url stringlengths 11 2.25k | text stringlengths 88 50k | ts timestamp[s]date 2026-01-13 08:47:33 2026-01-13 09:30:40 |
|---|---|---|
https://forem.com/t/programming/page/74 | Programming Page 74 - Forem Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account DEV Community Close Programming Follow Hide The magic behind computers. 💻 🪄 Create Post Older #programming posts 71 72 73 74 75 76 77 78 79 Posts Left menu 👋 Sign in for the ability to sort posts by relevant , latest , or top . Right menu Introducing temporal-contract: Type-Safe Temporal. io Workflows for TypeScript Benoit Travers Benoit Travers Benoit Travers Follow Dec 21 '25 Introducing temporal-contract: Type-Safe Temporal. io Workflows for TypeScript # typescript # node # programming # productivity 2 reactions Comments Add Comment 8 min read AWS CodeDeploy: A Beginner-Friendly Guide to Automated Deployments Ege Pakten Ege Pakten Ege Pakten Follow Dec 17 '25 AWS CodeDeploy: A Beginner-Friendly Guide to Automated Deployments # aws # codedeploy # programming # infrastructureascode Comments Add Comment 5 min read StableJSON: A Practical Workspace for Serious JSON Work Debjit Dey Debjit Dey Debjit Dey Follow Dec 31 '25 StableJSON: A Practical Workspace for Serious JSON Work # programming # webdev # devtool # json Comments 1 comment 2 min read I Built a Clean Age Calculator Because Most of Them Get the Details Wrong Momin Ali Momin Ali Momin Ali Follow Dec 18 '25 I Built a Clean Age Calculator Because Most of Them Get the Details Wrong # programming # webdev # javascript 1 reaction Comments 1 comment 2 min read The New Field Keyword Improves Properties in C# 14 Adrián Bailador Adrián Bailador Adrián Bailador Follow Dec 17 '25 The New Field Keyword Improves Properties in C# 14 # csharp # dotnet # programming # webdev Comments Add Comment 6 min read Atlassian Bamboo in the DevSecOps Periodic Table ABITHA N 24CB001 ABITHA N 24CB001 ABITHA N 24CB001 Follow Dec 18 '25 Atlassian Bamboo in the DevSecOps Periodic Table # devops # devsecops # programming # learning Comments Add Comment 1 min read How One Can Start Their Journey in Data Engineering Chetan Gupta Chetan Gupta Chetan Gupta Follow Jan 10 How One Can Start Their Journey in Data Engineering # programming # dataengineering # sql # beginners Comments 2 comments 4 min read AI-Powered Programming: Creating My Own Magical Flashcards Study App Daniel Daniel Daniel Follow for Datalaria Jan 10 AI-Powered Programming: Creating My Own Magical Flashcards Study App # showdev # ai # programming 5 reactions Comments 2 comments 5 min read YAML Formatter Pineapple Pineapple Pineapple Follow Dec 22 '25 YAML Formatter # webdev # programming # beginners # kubernetes Comments Add Comment 2 min read Beyond the Screen: Why LLMs Don't Need Browsers (And Why We Think They Do) Edward Burton Edward Burton Edward Burton Follow Dec 17 '25 Beyond the Screen: Why LLMs Don't Need Browsers (And Why We Think They Do) # webdev # programming # ai # browser 1 reaction Comments Add Comment 8 min read Day 73: Python Longest Palindromic Substring – Expand-Around-Center O(n^2) Technique for Max Palindrome (LeetCode #5 Guide) Shahrouz Nikseresht Shahrouz Nikseresht Shahrouz Nikseresht Follow Dec 23 '25 Day 73: Python Longest Palindromic Substring – Expand-Around-Center O(n^2) Technique for Max Palindrome (LeetCode #5 Guide) # challenge # python # algorithms # programming Comments Add Comment 2 min read The Time Our Pipeline Processed the Same Day’s Data 47 Times Pradeep Kalluri Pradeep Kalluri Pradeep Kalluri Follow Dec 17 '25 The Time Our Pipeline Processed the Same Day’s Data 47 Times # dataengineering # airflow # python # programming Comments Add Comment 5 min read How I Use AI to Build Full-Stack Apps (The Pipeline Nobody Talks About) Edjere Evelyn Oghenetejiri Edjere Evelyn Oghenetejiri Edjere Evelyn Oghenetejiri Follow Dec 17 '25 How I Use AI to Build Full-Stack Apps (The Pipeline Nobody Talks About) # webdev # ai # programming # nextjs 1 reaction Comments Add Comment 3 min read I Built a Deterministic Life Tool (and Intentionally Removed “AI” From the Loop) FlameAI Studio FlameAI Studio FlameAI Studio Follow Dec 17 '25 I Built a Deterministic Life Tool (and Intentionally Removed “AI” From the Loop) # webdev # programming # productivity # beginners Comments Add Comment 2 min read Effectively Managing AI Agents for Testing John Vester John Vester John Vester Follow Dec 18 '25 Effectively Managing AI Agents for Testing # ai # agentaichallenge # programming # testing 1 reaction Comments Add Comment 7 min read Perl 🐪 Weekly #753 - Happy New Year! Gabor Szabo Gabor Szabo Gabor Szabo Follow Dec 29 '25 Perl 🐪 Weekly #753 - Happy New Year! # news # perl # programming 1 reaction Comments Add Comment 6 min read Continuous Fluid Flow: How AI Is Compressing the Software Delivery Cycle Cleber de Lima Cleber de Lima Cleber de Lima Follow Dec 18 '25 Continuous Fluid Flow: How AI Is Compressing the Software Delivery Cycle # programming # ai # softwareengineering # softwaredevelopment Comments Add Comment 7 min read Apertre 3.0: A 30-Day Open-Source Journey for Developers 🚀 Soumyajit Mondal Soumyajit Mondal Soumyajit Mondal Follow for Apertre 3.0 Dec 17 '25 Apertre 3.0: A 30-Day Open-Source Journey for Developers 🚀 # webdev # programming # opensource # github 1 reaction Comments Add Comment 1 min read I Built an AI Studying Website as a Student — Meet Studex AI Studexaidev Studexaidev Studexaidev Follow Dec 17 '25 I Built an AI Studying Website as a Student — Meet Studex AI # webdev # ai # programming # beginners 1 reaction Comments 1 comment 2 min read Routing, Load Balancing, and Failover in LLM Systems Debby McKinney Debby McKinney Debby McKinney Follow Dec 23 '25 Routing, Load Balancing, and Failover in LLM Systems # mcp # programming # llm # rag 5 reactions Comments Add Comment 3 min read [AI 協作筆記] gRPC 傳輸優化：基於 Flattening 與 Bitset 的高效方案 Mesak Mesak Mesak Follow Dec 17 '25 [AI 協作筆記] gRPC 傳輸優化：基於 Flattening 與 Bitset 的高效方案 # programming # ai # php # grpc Comments Add Comment 2 min read gRPC Transmission Optimization: An Efficient Solution Based on Flattening and Bitset Mesak Mesak Mesak Follow Dec 17 '25 gRPC Transmission Optimization: An Efficient Solution Based on Flattening and Bitset # programming # ai # php # grpc Comments Add Comment 4 min read The Vibe Coding Hangover Is Real: What Nobody Tells You About AI-Generated Code in Production Paul Courage Labhani Paul Courage Labhani Paul Courage Labhani Follow Jan 8 The Vibe Coding Hangover Is Real: What Nobody Tells You About AI-Generated Code in Production # ai # webdev # programming # career 11 reactions Comments 6 comments 6 min read Understanding Python Data Structures: Lists, Tuples, Sets, and Dictionaries Made Simple Nomidl Official Nomidl Official Nomidl Official Follow Dec 18 '25 Understanding Python Data Structures: Lists, Tuples, Sets, and Dictionaries Made Simple # webdev # programming # ai # python Comments Add Comment 4 min read Fixing the Fatal Flaw in Your AI Pipeline Malik Abualzait Malik Abualzait Malik Abualzait Follow Dec 18 '25 Fixing the Fatal Flaw in Your AI Pipeline # ai # tech # programming # tutorial Comments Add Comment 3 min read loading... 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV DEV Community — Your community HQ Home About Contact Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . DEV Community © 2016 - 2026. We're a blogging-forward open source social network where we learn from one another Log in Create account | 2026-01-13T08:48:28 |
https://aws.amazon.com/es/app-mesh/ | Servicio de red de aplicaciones – AWS App Mesh – Amazon Web Services Saltar al contenido principal Filter: Todo English Contáctenos AWS Marketplace Soporte Mi cuenta Búsqueda Filter: Todo Iniciar sesión en la consola Crear cuenta AWS App Mesh Información general Características Precios Introducción Preguntas frecuentes Más Productos › Redes y entrega de contenido › AWS App Mesh Aviso de fin de soporte: el 30 de septiembre de 2026, AWS descontinuará el soporte para AWS AppMesh. Después del 30 de septiembre de 2026, ya no podrá acceder a la consola de AWS AppMesh ni a los recursos de AWS AppMesh. Para obtener más información, consulte la publicación del blog. AWS App Mesh Redes de nivel de aplicación para todos sus servicios ¿Por qué usar App Mesh? Reproducir Beneficios de App Mesh Optimización Optimice las operaciones, implemente reglas de enrutamiento del tráfico personalizadas y configure y estandarice el flujo del tráfico entre sus servicios. Optimice Capture métricas, registros y rastreos de sus aplicaciones para identificar y aislar errores con rapidez y así optimizar su aplicación. Mejore la seguridad Mejore la seguridad de red con controles de autenticación y solicitudes cifradas entre servicios, incluso dentro de su red privada. Cree una cuenta de AWS Aprender ¿Qué es AWS? ¿Qué es la computación en la nube? ¿Qué es la IA agéntica? Centro de conceptos de computación en la nube Seguridad en la nube de AWS Novedades Blogs Notas de prensa Recursos Introducción Formación Centro de confianza de AWS Biblioteca de soluciones de AWS Centro de arquitectura Preguntas frecuentes sobre cuestiones técnicas y productos Informes de analistas Socios de AWS Desarrolladores Centro de creadores SDK y herramientas .NET en AWS Python en AWS Java en AWS PHP en AWS JavaScript en AWS Ayuda Contacto Abra un ticket de soporte técnico AWS re:Post Centro de conocimientos Información general de AWS Support Reciba ayuda de expertos Accesibilidad de AWS Asuntos jurídicos English Volver arriba Amazon es un empleador que ofrece igualdad de oportunidades: minorías, mujeres, discapacitados, veteranos, identidad de género, orientación sexual y edad. x facebook linkedin instagram twitch youtube podcasts email Privacidad Términos del sitio Preferencias de cookies © 2026, Amazon Web Services, Inc. o sus empresas afiliadas. Todos los derechos reservados. | 2026-01-13T08:48:28 |
https://stackoverflow.blog/2026/01/12/now-everyone-can-chat-on-stack-overflow/ | Now everyone can chat on Stack Overflow - Stack Overflow Blog Loading… Everything Productivity AI/ML Open Source Business Hub Company Releases Podcast Newsletter Stack Overflow Business Stack Internal : the knowledge intelligence layer that powers enterprise AI. Stack Data Licensing : decades of verified, technical knowledge to boost AI performance and trust. Stack Ads : engage developers where it matters — in their daily workflow. January 12, 2026 Now everyone can chat on Stack Overflow Registered users can now join public chat rooms from day one, making it easier to connect, learn, and participate in the community Today we launched full access to Stack Overflow chat rooms for registered users. With an abundance of public chat rooms available across endless technical topics, Chat offers a real-time connection space with individuals in your communities. Allowing 1 reputation users to start chatting Chat access was previously a privilege reserved for users with 20 reputation points or more. As Stack Overflow continues to evolve to be a community-first platform, we realized that this created a barrier for newcomers. To provide an immediate, approachable entry point into the Stack Overflow experience and community networking, we began work to make chat accessible to everyone right from the start. In May 2025, we launched the Stack Overflow and Stack Exchange Lobbies . These spaces immediately give users with 1 reputation a place to discuss projects, ask support questions, and connect. The results from those spaces have been great to see. We verified that 60% of all Lobby room participants currently have fewer than 20 reputation points . This significant engagement from novice users motivates us to expand accessibility to all public chat rooms on Stack Overflow. This opens exciting possibilities for newly engaged users to grow their confidence, find their voice on the platform, and become even more active contributors across the entire platform in the right spaces for their topics. Updated chat room guidelines and onboarding As we move forward with opening chat to all registered users, we needed to clarify room guidelines and expectations. Chat Room Owners can now create onboarding cards to their public chat rooms to help the influx of new chat users to know what to expect from a chat room and guidance on how to successfully participate in the chat room. Stack Overflow Lobby chat room description and guidance page New moderation and protection tooling for a secure chat experience At Stack Overflow, user security, safety, and protection are paramount in the products we create and what the community wants. Chat, due to its instant public publishing and large audience, offers us another chance to continuously improve our tools for a safer online experience within the public platform. We have enhanced our moderation capabilities and implemented new security measures, including human identity validation, to prevent spam bots from entering chat rooms. Moderators and chat room owners also have additional tools available to them to assist with guarding against malicious behavior at a broader scale. Start chatting today Chat introduces a new level of ease and accessibility for both new and experienced users on Stack Overflow. As Stack Overflow continues to grow into the internet's most vital resource for technology, we recognize the critical need to enable real-time communication and connection among community members on topics essential to technologists' success. Explore the chat rooms landing page today to find your community and begin chatting. Author s Kate Smith Product Marketing Manager Staff Community Recent articles January 5, 2026 What’s new at Stack Overflow: January 2026 January 2, 2026 A new worst coder has entered the chat: vibe coding without code knowledge January 1, 2026 Documents: The architect’s programming language December 31, 2025 A look under the hood: How (and why) we built Question Assistant Latest Podcast January 13, 2026 Vibe code anything in a Hanselminute Add to the discussion Login with your stackoverflow.com account to take part in the discussion. Our Stack Stack Internal Features Customers Security Pricing Stack Data Licensing Stack Ads Partnerships Services Stack Overflow Company Leadership Press Careers Social Impact Support Contact Stack Overflow help Stack Internal help Terms Privacy policy Cookie policy Your Privacy Choices Elsewhere Blog Dev Newsletter Podcast Releases Dev Survey Site design / logo © 2026 Stack Exchange Inc. Light Dark Auto | 2026-01-13T08:48:28 |
https://github.com/codebunny20/HRT-Journey-Tracker-Suite#start-of-content | GitHub - codebunny20/HRT-Journey-Tracker-Suite Skip to content Navigation Menu Toggle navigation Sign in Appearance settings Platform AI CODE CREATION GitHub Copilot Write better code with AI GitHub Spark Build and deploy intelligent apps GitHub Models Manage and compare prompts MCP Registry New Integrate external tools DEVELOPER WORKFLOWS Actions Automate any workflow Codespaces Instant dev environments Issues Plan and track work Code Review Manage code changes APPLICATION SECURITY GitHub Advanced Security Find and fix vulnerabilities Code security Secure your code as you build Secret protection Stop leaks before they start EXPLORE Why GitHub Documentation Blog Changelog Marketplace View all features Solutions BY COMPANY SIZE Enterprises Small and medium teams Startups Nonprofits BY USE CASE App Modernization DevSecOps DevOps CI/CD View all use cases BY INDUSTRY Healthcare Financial services Manufacturing Government View all industries View all solutions Resources EXPLORE BY TOPIC AI Software Development DevOps Security View all topics EXPLORE BY TYPE Customer stories Events & webinars Ebooks & reports Business insights GitHub Skills SUPPORT & SERVICES Documentation Customer support Community forum Trust center Partners Open Source COMMUNITY GitHub Sponsors Fund open source developers PROGRAMS Security Lab Maintainer Community Accelerator Archive Program REPOSITORIES Topics Trending Collections Enterprise ENTERPRISE SOLUTIONS Enterprise platform AI-powered developer platform AVAILABLE ADD-ONS GitHub Advanced Security Enterprise-grade security features Copilot for Business Enterprise-grade AI features Premium Support Enterprise-grade 24/7 support Pricing Search or jump to... Search code, repositories, users, issues, pull requests... --> Search Clear Search syntax tips Provide feedback --> We read every piece of feedback, and take your input very seriously. Include my email address so I can be contacted Cancel Submit feedback Saved searches Use saved searches to filter your results more quickly --> Name Query To see all available qualifiers, see our documentation . Cancel Create saved search Sign in Sign up Appearance settings Resetting focus You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session. Dismiss alert {{ message }} codebunny20 / HRT-Journey-Tracker-Suite Public Notifications You must be signed in to change notification settings Fork 0 Star 2 2 stars 0 forks Branches Tags Activity Star Notifications You must be signed in to change notification settings Code Issues 0 Pull requests 0 Actions Projects 0 Security Uh oh! There was an error while loading. Please reload this page . Insights Additional navigation options Code Issues Pull requests Actions Projects Security Insights codebunny20/HRT-Journey-Tracker-Suite main Branches Tags Go to file Code Open more actions menu Folders and files Name Name Last commit message Last commit date Latest commit History 23 Commits Body Change map Body Change map Cycle Tracker Cycle Tracker Journey Journal Journey Journal Launcher Launcher Resource manager Resource manager TrackMyHRT TrackMyHRT Voice-Trainer Voice-Trainer .gitattributes .gitattributes .gitignore .gitignore README.md README.md requirements.txt requirements.txt View all files Repository files navigation README HRT Journey Tracker Ive made this small collection of PySide6 (Qt) desktop apps to help track different parts of an HRT journey (logging, journaling, cycle tracking, resources, and voice/pitch practice). Each app is self-contained, stores data locally, and includes a documented workflow. Once all apps are functional and cohesive I plan to bundle and biuld an all in one app including everything in this project. I also would like to make a secure web version. What’s included (at a glance) TrackMyHRT : medication + symptom tracking with exports Journey Journal : daily journaling with themes, table view, and exports Cycle Tracker : cycle/bleed logging with summary stats and an estimated next start date Resource Manager : save/search/open useful links (title + URL) Voice Trainer (prototype) : record/load audio and estimate pitch (Hz) Quick start (from source) Each app can be run on its own. py - m venv .venv .\.venv\Scripts\Activate.ps1 py - m pip install - U pip py - m pip install PySide6 Then run an app (examples): py .\HRT.py py .\JJ.py py .\C - T.py Some apps have extra dependencies (see the app’s .md doc, especially Voice Trainer). Apps included TrackMyHRT ( HRT.py ) Log HRT entries with date/time , one or more medications (name/dose/unit/route/time), optional mood/energy/symptoms/libido (multi-select), and notes . Notable behavior/features: Saving requires at least one medication name Built-in viewer: View / Details (raw JSON) / Delete / Export Export formats: .jsonl , .json , .txt , .md Supports migrating older JSONL → JSON storage if detected Data storage: storage/entries.json (next to HRT.py or bundled .exe ) Run: py .\HRT.py Details: TrackMyHRT/TrackMyHRT.md Journey Journal ( JJ.py ) Create a daily journal entry (date, mood, symptoms, a few dropdown fields, notes), browse entries in a table, delete single/multiple, export ( .json/.md/.txt ), and toggle Dark/Light theme (persisted via QSettings ). Notable behavior/features: Enforces one entry per date (prompts to replace) Refuses to save fully empty entries (prevents blank rows) Exports to: .json , .md (formatted), .txt (plain blocks) Includes a “view entries” dialog with Refresh / View / Details / Delete Theme menu: View → Theme → Dark/Light Data storage: storage/j_j.json Run: py .\JJ.py Details: Journey Journal/Journal Journy.md Cycle Tracker ( C-T.py ) Log cycle/bleed entries, view/edit/delete them in a sortable table, and see summary stats: average cycle length , average bleed length , and an estimated next start . Includes Dark/Light theme via QSettings , plus hover tooltips for tags/notes. Notable behavior/features: Add/Edit validates that end date >= start date Tags are comma-separated and are trimmed + de-duplicated Sorting-safe row selection (stores an index in Qt.UserRole ) Summary shows “not enough entries” until there are at least 2 cycles Data storage: data/cycle_entries.json (next to the script) Run: py .\C-T.py Details: Cycle Tracker/Cycle Tracker.md Resource Manager ( main.py ) — Link Manager Save and manage useful Title + URL resources with fast search/filtering and quick actions: open in browser, copy URL, remove, clear all. Notable behavior/features: Instant filtering matches title or URL (case-insensitive) Normalizes URLs (e.g. example.com → https://example.com ) Accepts only http:// and https:// Context menu + double-click open Data storage: handled by data.storage.LinkStorage (see app docs) Run (from Resource manager folder): py .\main.py Details: Resource manager/Resource manager.md Voice Trainer — Prototype ( V-T.py ) Record a short mono clip (or load an audio file), estimate pitch using aubio YIN , and display an average pitch (median) in Hz . Uses a worker thread for recording so the UI stays responsive. Notable behavior/features: Can analyze either last_recording.wav or any chosen file Filters pitch values to a human-voice range (~50–500 Hz) and ignores silence Designed as a prototype for future integration Data storage: uses a working file last_recording.wav next to the script (no entries DB) Run: py .\V-T.py Details: Voice-Trainer/Voice Trainer.md Project direction (planned) Combine these tools into one cohesive “all-in-one” desktop app once the individual apps stabilize Explore a secure web version later (after the desktop workflow and data model are solid) Notes These are desktop GUI apps built with PySide6 ; each app’s markdown file documents behavior, storage, and UI flows. If you bundle into an .exe (PyInstaller), storage paths are described per-app in the linked docs. About No description, website, or topics provided. Resources Readme Uh oh! There was an error while loading. Please reload this page . Activity Stars 2 stars Watchers 1 watching Forks 0 forks Report repository Releases No releases published Packages 0 No packages published Languages Python 100.0% Footer © 2026 GitHub, Inc. Footer navigation Terms Privacy Security Status Community Docs Contact Manage cookies Do not share my personal information You can’t perform that action at this time. | 2026-01-13T08:48:28 |
https://www.linkedin.com/posts/devcyclehq_why-a-homegrown-feature-flag-system-is-a-activity-7406383191910993920-ANWK | Why a Homegrown Feature Flag System is a Trap | DevCycle Agree & Join LinkedIn By clicking Continue to join or sign in, you agree to LinkedIn’s User Agreement , Privacy Policy , and Cookie Policy . Skip to main content LinkedIn Top Content People Learning Jobs Games Sign in Join for free DevCycle’s Post DevCycle 1,008 followers 4w Report this post The real data is brutal: • 30% of engineering time lost to DIY flag maintenance 🚧 • 73% of flags never removed 🔒 • Thousands of hours per year navigating flag technical debt and bloat 🫃 Homegrown feature flags aren’t “lightweight.” They’re a slow bleed. 🩸 🩸 🩸 https://lnkd.in/eqWXpDfE #FeatureFlags #SoftwareEng #EngManager by Mark Allen Why a Homegrown Feature Flag System is a Trap blog.devcycle.com 2 1 Comment Like Comment Share Copy LinkedIn Facebook X Mohamad Shahkhajeh 4w Report this comment 30% engineering time lost to DIY flag maintenance highlights a serious operational efficiency bottleneck. Like Reply 1 Reaction To view or add a comment, sign in 1,008 followers View Profile Follow Explore content categories Career Productivity Finance Soft Skills & Emotional Intelligence Project Management Education Technology Leadership Ecommerce User Experience Show more Show less LinkedIn © 2026 About Accessibility User Agreement Privacy Policy Cookie Policy Copyright Policy Brand Policy Guest Controls Community Guidelines العربية (Arabic) বাংলা (Bangla) Čeština (Czech) Dansk (Danish) Deutsch (German) Ελληνικά (Greek) English (English) Español (Spanish) فارسی (Persian) Suomi (Finnish) Français (French) हिंदी (Hindi) Magyar (Hungarian) Bahasa Indonesia (Indonesian) Italiano (Italian) עברית (Hebrew) 日本語 (Japanese) 한국어 (Korean) मराठी (Marathi) Bahasa Malaysia (Malay) Nederlands (Dutch) Norsk (Norwegian) ਪੰਜਾਬੀ (Punjabi) Polski (Polish) Português (Portuguese) Română (Romanian) Русский (Russian) Svenska (Swedish) తెలుగు (Telugu) ภาษาไทย (Thai) Tagalog (Tagalog) Türkçe (Turkish) Українська (Ukrainian) Tiếng Việt (Vietnamese) 简体中文 (Chinese (Simplified)) 正體中文 (Chinese (Traditional)) Language Sign in to view more content Create your free account or sign in to continue your search Sign in Welcome back Email or phone Password Show Forgot password? Sign in or By clicking Continue to join or sign in, you agree to LinkedIn’s User Agreement , Privacy Policy , and Cookie Policy . New to LinkedIn? Join now or New to LinkedIn? Join now By clicking Continue to join or sign in, you agree to LinkedIn’s User Agreement , Privacy Policy , and Cookie Policy . | 2026-01-13T08:48:28 |
https://dev.to/hamzaansariask#main-content | Hamza Ansari - DEV Community Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account DEV Community Close Follow User actions Hamza Ansari Website Developer at in Scotland at tech company in scotland. Location scotland Joined Joined on May 31, 2025 More info about @hamzaansariask Badges Writing Debut Awarded for writing and sharing your first DEV post! Continue sharing your work to earn the 4 Week Writing Streak Badge. Got it Close 1 Week Community Wellness Streak For actively engaging with the community by posting at least 2 comments in a single week. Got it Close Post 0 posts published Comment 2 comments written Tag 0 tags followed Want to connect with Hamza Ansari? Create an account to connect with Hamza Ansari. You can also sign in below to proceed if you already have an account. Create Account Already have an account? Sign in loading... 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV DEV Community — A space to discuss and keep up software development and manage your software career Home DEV++ Podcasts Videos DEV Education Tracks DEV Challenges DEV Help Advertise on DEV DEV Showcase About Contact Free Postgres Database Software comparisons Forem Shop Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . DEV Community © 2016 - 2026. We're a place where coders share, stay up-to-date and grow their careers. Log in Create account | 2026-01-13T08:48:28 |
https://aws.amazon.com/de/app-mesh/ | Service für Anwendungsnetzwerke – AWS App Mesh – Amazon Webservices Überspringen zum Hauptinhalt Filter: Alle English Kontaktieren Sie uns AWS Marketplace Support Mein Konto Suche Filter: Alle Bei der Konsole anmelden Konto erstellen AWS App Mesh Übersicht Features Preise Erste Schritte Häufig gestellte Fragen Mehr Produkte › Netzwerke und Inhaltsbereitstellung › AWS App Mesh Hinweis zum Ende des Supports: Am 30. September 2026 wird AWS den Support für AWS AppMesh einstellen. Nach dem 30. September 2026 können Sie nicht mehr auf die AWS-AppMesh-Konsole oder die AWS-AppMesh-Ressourcen zugreifen. Weitere Informationen finden Sie in diesem Blog-Beitrag. AWS App Mesh Netzwerk auf Anwendungsebene für alle Ihre Services Warum App Mesh? Abspielen Vorteile von App Mesh Straffen Optimieren Sie die Abläufe, implementieren Sie benutzerdefinierte Regeln für die Weiterleitung des Datenverkehrs und konfigurieren und standardisieren Sie den Ablauf des Datenverkehrs zwischen Ihren Services. Optimieren Erfassen Sie Metriken, Protokolle und Ablaufverfolgungen von Ihren Anwendungen, um Probleme schnell zu identifizieren und zu isolieren und Ihre Anwendung zu optimieren. Verbessern der Sicherheit Erhöhen Sie die Netzwerksicherheit mit Authentifizierungskontrollen und verschlüsselten Anfragen zwischen Services – sogar innerhalb Ihres privaten Netzwerks. AWS-Konto erstellen Lernen Was ist AWS? Was ist „Cloud Computing“? Was ist „Agentenbasierte KI“? Hub für Cloud-Computing-Konzepte AWS Cloud Sicherheit Neuerungen Blogs Pressemitteilungen Ressourcen Erste Schritte Training AWS Trust Center AWS-Lösungsportfolio Architekturzentrum Häufig gestellte Fragen zu Produkt und Technik Berichte von Analysten AWS-Partner Entwickler Builder Center SDKs und Tools .NET auf AWS Python in AWS Java in AWS PHP in AWS JavaScript in AWS Hilfe Kontaktieren Sie uns Support-Ticket aufgeben AWS re:Post Wissenscenter AWS Support – Überblick Erhalten Sie Hilfe von Experten Barrierefreiheit bei AWS Rechtlicher Hinweis English Zurück zum Seitenanfang Amazon.com setzt als Arbeitgeber auf Gleichberechtigung: Minderheiten/Frauen/Menschen mit Behinderungen/Veteranen/Geschlechtsidentität/sexuelle Orientierung/Alter. x facebook linkedin instagram twitch youtube podcasts email Datenschutz Allgemeine Geschäftsbedingungen Cookie-Einstellungen © 2026, Amazon Web Services, Inc. bzw. Tochtergesellschaften des Unternehmens. Alle Rechte vorbehalten. | 2026-01-13T08:48:28 |
https://stackoverflow.blog/2026/01/12/now-everyone-can-chat-on-stack-overflow/#comments | Now everyone can chat on Stack Overflow - Stack Overflow Blog Loading… Everything Productivity AI/ML Open Source Business Hub Company Releases Podcast Newsletter Stack Overflow Business Stack Internal : the knowledge intelligence layer that powers enterprise AI. Stack Data Licensing : decades of verified, technical knowledge to boost AI performance and trust. Stack Ads : engage developers where it matters — in their daily workflow. January 12, 2026 Now everyone can chat on Stack Overflow Registered users can now join public chat rooms from day one, making it easier to connect, learn, and participate in the community Today we launched full access to Stack Overflow chat rooms for registered users. With an abundance of public chat rooms available across endless technical topics, Chat offers a real-time connection space with individuals in your communities. Allowing 1 reputation users to start chatting Chat access was previously a privilege reserved for users with 20 reputation points or more. As Stack Overflow continues to evolve to be a community-first platform, we realized that this created a barrier for newcomers. To provide an immediate, approachable entry point into the Stack Overflow experience and community networking, we began work to make chat accessible to everyone right from the start. In May 2025, we launched the Stack Overflow and Stack Exchange Lobbies . These spaces immediately give users with 1 reputation a place to discuss projects, ask support questions, and connect. The results from those spaces have been great to see. We verified that 60% of all Lobby room participants currently have fewer than 20 reputation points . This significant engagement from novice users motivates us to expand accessibility to all public chat rooms on Stack Overflow. This opens exciting possibilities for newly engaged users to grow their confidence, find their voice on the platform, and become even more active contributors across the entire platform in the right spaces for their topics. Updated chat room guidelines and onboarding As we move forward with opening chat to all registered users, we needed to clarify room guidelines and expectations. Chat Room Owners can now create onboarding cards to their public chat rooms to help the influx of new chat users to know what to expect from a chat room and guidance on how to successfully participate in the chat room. Stack Overflow Lobby chat room description and guidance page New moderation and protection tooling for a secure chat experience At Stack Overflow, user security, safety, and protection are paramount in the products we create and what the community wants. Chat, due to its instant public publishing and large audience, offers us another chance to continuously improve our tools for a safer online experience within the public platform. We have enhanced our moderation capabilities and implemented new security measures, including human identity validation, to prevent spam bots from entering chat rooms. Moderators and chat room owners also have additional tools available to them to assist with guarding against malicious behavior at a broader scale. Start chatting today Chat introduces a new level of ease and accessibility for both new and experienced users on Stack Overflow. As Stack Overflow continues to grow into the internet's most vital resource for technology, we recognize the critical need to enable real-time communication and connection among community members on topics essential to technologists' success. Explore the chat rooms landing page today to find your community and begin chatting. Author s Kate Smith Product Marketing Manager Staff Community Recent articles January 5, 2026 What’s new at Stack Overflow: January 2026 January 2, 2026 A new worst coder has entered the chat: vibe coding without code knowledge January 1, 2026 Documents: The architect’s programming language December 31, 2025 A look under the hood: How (and why) we built Question Assistant Latest Podcast January 13, 2026 Vibe code anything in a Hanselminute Add to the discussion Login with your stackoverflow.com account to take part in the discussion. Our Stack Stack Internal Features Customers Security Pricing Stack Data Licensing Stack Ads Partnerships Services Stack Overflow Company Leadership Press Careers Social Impact Support Contact Stack Overflow help Stack Internal help Terms Privacy policy Cookie policy Your Privacy Choices Elsewhere Blog Dev Newsletter Podcast Releases Dev Survey Site design / logo © 2026 Stack Exchange Inc. Light Dark Auto | 2026-01-13T08:48:28 |
https://dev.to/ajtiti/ajtiti-35-o-roli-team-leada-1-2#main-content | AjTiTi #35 - O roli Team Leada (1/2) - DEV Community Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account Forem Close AjTiTi [PL] Follow AjTiTi #35 - O roli Team Leada (1/2) Feb 18 '22 play Kim jest Team Lead? Jaka jest jego rola w zespole? Czy każdy może nim zostać? Czy każdy powinien? Na te i kilka innych pytań postaramy się odpowiedzieć w dzisiejszym odcinku! :) Episode source Personal Trusted User Create template Templates let you quickly answer FAQs or store snippets for re-use. Submit Preview Dismiss Your browser does not support the audio element. 1x initializing... × 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV Forem — A space to discuss and keep up software development and manage your software career Home DEV++ Podcasts Videos DEV Education Tracks DEV Challenges DEV Help Advertise on DEV DEV Showcase About Contact Free Postgres Database Software comparisons Forem Shop Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . Forem © 2016 - 2026. We're a place where coders share, stay up-to-date and grow their careers. Log in Create account | 2026-01-13T08:48:28 |
https://dev.to/aaronmccollum | Aaron McCollum - DEV Community Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account DEV Community Close Follow User actions Aaron McCollum Aaron is a Software Developer experienced in web development and business-process management applications. He also enjoys soccer, craft beer, and cheering for "next season" as a Cleveland Browns fan. Joined Joined on Apr 22, 2020 Personal website https://medium.com/@amccollum.dev github website Five Year Club This badge celebrates the longevity of those who have been a registered member of the DEV Community for at least five years. Got it Close Four Year Club This badge celebrates the longevity of those who have been a registered member of the DEV Community for at least four years. Got it Close 2 Week Community Wellness Streak Keep the community conversation going! Post at least 2 comments for 2 straight weeks and unlock the 4 Week Badge. Got it Close Top 7 Awarded for having a post featured in the weekly "must-reads" list. 🙌 Got it Close Writing Debut Awarded for writing and sharing your first DEV post! Continue sharing your work to earn the 4 Week Writing Streak Badge. Got it Close 1 Week Community Wellness Streak For actively engaging with the community by posting at least 2 comments in a single week. Got it Close Three Year Club This badge celebrates the longevity of those who have been a registered member of the DEV Community for at least three years. Got it Close Two Year Club This badge celebrates the longevity of those who have been a registered member of the DEV Community for at least two years. Got it Close 4 Week Writing Streak You've posted at least one post per week for 4 consecutive weeks! Got it Close One Year Club This badge celebrates the longevity of those who have been a registered member of the DEV Community for at least one year. Got it Close Codeland:Distributed 2020 Awarded for attending CodeLand:Distributed 2020! Got it Close More info about @aaronmccollum Skills/Languages HTML, CSS, JavaScript, React, Python Currently learning 100Devs Cohort 2 Available for Feel free to talk about projects you're building, ask for career advice (I've had a few different "careers" so happy to give you my opinions), or video games and sports! Post 32 posts published Comment 102 comments written Tag 10 tags followed 2026 Hopes and Goals Aaron McCollum Aaron McCollum Aaron McCollum Follow Jan 7 2026 Hopes and Goals # 100dev # webdev # career Comments Add Comment 2 min read Want to connect with Aaron McCollum? Create an account to connect with Aaron McCollum. You can also sign in below to proceed if you already have an account. Create Account Already have an account? Sign in Creating a functional Contact form on your website Aaron McCollum Aaron McCollum Aaron McCollum Follow Dec 26 '25 Creating a functional Contact form on your website # webdev # learning # programming # netlify Comments Add Comment 5 min read Start, Stop, and Continue for 2026 Aaron McCollum Aaron McCollum Aaron McCollum Follow Dec 19 '25 Start, Stop, and Continue for 2026 # webdev # programming # learning Comments Add Comment 3 min read Podcasts I listened to in 2025 Aaron McCollum Aaron McCollum Aaron McCollum Follow Dec 15 '25 Podcasts I listened to in 2025 # podcast # software # yearinreview # programming Comments Add Comment 3 min read Things learned from making several HTML/CSS layouts Aaron McCollum Aaron McCollum Aaron McCollum Follow Dec 5 '25 Things learned from making several HTML/CSS layouts # html # css # webdev # ui 1 reaction Comments Add Comment 3 min read Branch development with git Aaron McCollum Aaron McCollum Aaron McCollum Follow Dec 2 '25 Branch development with git # git # github # software # webdev Comments Add Comment 3 min read Creating an application using Vite Aaron McCollum Aaron McCollum Aaron McCollum Follow Feb 26 '25 Creating an application using Vite # webdev # javascript # beginners # react Comments Add Comment 2 min read Watching Claude play Pokemon Aaron McCollum Aaron McCollum Aaron McCollum Follow Feb 26 '25 Watching Claude play Pokemon # machinelearning # llm Comments Add Comment 2 min read Tips for remote work Aaron McCollum Aaron McCollum Aaron McCollum Follow Mar 23 '24 Tips for remote work # career # remote # workplace 93 reactions Comments 31 comments 5 min read My software development journey Aaron McCollum Aaron McCollum Aaron McCollum Follow Mar 13 '24 My software development journey # career # coding # learning # workplace Comments Add Comment 7 min read Semantic HTML Aaron McCollum Aaron McCollum Aaron McCollum Follow Jun 11 '23 Semantic HTML # html # webdev 1 reaction Comments Add Comment 2 min read A Short History on the C Programming Language Aaron McCollum Aaron McCollum Aaron McCollum Follow Jan 27 '22 A Short History on the C Programming Language 2 reactions Comments 3 comments 2 min read Reviewing "Androids" by Chet Haase Aaron McCollum Aaron McCollum Aaron McCollum Follow Jan 23 '22 Reviewing "Androids" by Chet Haase 2 reactions Comments Add Comment 3 min read First Coding Meetup of 2022 Aaron McCollum Aaron McCollum Aaron McCollum Follow Jan 20 '22 First Coding Meetup of 2022 2 reactions Comments Add Comment 1 min read Working with the DOM Part 1 Aaron McCollum Aaron McCollum Aaron McCollum Follow Oct 6 '21 Working with the DOM Part 1 6 reactions Comments Add Comment 4 min read Finishing my Landing Page project Aaron McCollum Aaron McCollum Aaron McCollum Follow Sep 28 '21 Finishing my Landing Page project 3 reactions Comments 2 comments 3 min read Contributing to Open Source for the first time Aaron McCollum Aaron McCollum Aaron McCollum Follow Sep 23 '21 Contributing to Open Source for the first time 2 reactions Comments Add Comment 4 min read The Odin Project – 2 weeks in Aaron McCollum Aaron McCollum Aaron McCollum Follow Sep 19 '21 The Odin Project – 2 weeks in 3 reactions Comments Add Comment 2 min read Introduction to Git: Part 2 Aaron McCollum Aaron McCollum Aaron McCollum Follow Sep 17 '21 Introduction to Git: Part 2 12 reactions Comments Add Comment 3 min read An Introduction to Git, Part 1 Aaron McCollum Aaron McCollum Aaron McCollum Follow Sep 16 '21 An Introduction to Git, Part 1 6 reactions Comments 3 comments 3 min read Three nifty shortcuts on the Command Line Aaron McCollum Aaron McCollum Aaron McCollum Follow Sep 12 '21 Three nifty shortcuts on the Command Line 5 reactions Comments Add Comment 2 min read Common JavaScript errors to watch out for (what what gets me everyday) Aaron McCollum Aaron McCollum Aaron McCollum Follow Jan 8 '21 Common JavaScript errors to watch out for (what what gets me everyday) 1 reaction Comments 3 comments 3 min read Making my own code documentation Aaron McCollum Aaron McCollum Aaron McCollum Follow Jan 5 '21 Making my own code documentation 3 reactions Comments 2 comments 2 min read A Programmer's Thanksgiving Aaron McCollum Aaron McCollum Aaron McCollum Follow Nov 27 '20 A Programmer's Thanksgiving 4 reactions Comments Add Comment 2 min read My 2-week reaction post about App Academy Open Aaron McCollum Aaron McCollum Aaron McCollum Follow Nov 14 '20 My 2-week reaction post about App Academy Open 4 reactions Comments 3 comments 2 min read October Updates - Functional Programming! Aaron McCollum Aaron McCollum Aaron McCollum Follow Oct 14 '20 October Updates - Functional Programming! 2 reactions Comments Add Comment 2 min read First time with a Virtual Machine Aaron McCollum Aaron McCollum Aaron McCollum Follow Aug 23 '20 First time with a Virtual Machine 2 reactions Comments Add Comment 2 min read What have I been doing this week? 8/3-7 Aaron McCollum Aaron McCollum Aaron McCollum Follow Aug 7 '20 What have I been doing this week? 8/3-7 1 reaction Comments Add Comment 2 min read Dice Rolling Program Aaron McCollum Aaron McCollum Aaron McCollum Follow Jul 24 '20 Dice Rolling Program 5 reactions Comments 13 comments 1 min read My First JavaScript Page Aaron McCollum Aaron McCollum Aaron McCollum Follow May 7 '20 My First JavaScript Page 6 reactions Comments Add Comment 1 min read First Profile Site Aaron McCollum Aaron McCollum Aaron McCollum Follow Apr 27 '20 First Profile Site 3 reactions Comments 5 comments 1 min read Hello World! Aaron McCollum Aaron McCollum Aaron McCollum Follow Apr 22 '20 Hello World! 3 reactions Comments Add Comment 1 min read loading... 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV DEV Community — A space to discuss and keep up software development and manage your software career Home DEV++ Podcasts Videos DEV Education Tracks DEV Challenges DEV Help Advertise on DEV DEV Showcase About Contact Free Postgres Database Software comparisons Forem Shop Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . DEV Community © 2016 - 2026. We're a place where coders share, stay up-to-date and grow their careers. Log in Create account | 2026-01-13T08:48:28 |
https://techcrunch.com/2021/12/14/the-irrational-exuberance-of-web3/ | The irrational exuberance of web3 | TechCrunch TechCrunch Desktop Logo TechCrunch Mobile Logo Latest Startups Venture Apple Security AI Apps Events Podcasts Newsletters Search Submit Site Search Toggle Mega Menu Toggle Topics Latest AI Amazon Apps Biotech & Health Climate Cloud Computing Commerce Crypto Enterprise EVs Fintech Fundraising Gadgets Gaming Google Government & Policy Hardware Instagram Layoffs Media & Entertainment Meta Microsoft Privacy Robotics Security Social Space Startups TikTok Transportation Venture More from TechCrunch Staff Events Startup Battlefield StrictlyVC Newsletters Podcasts Videos Partner Content TechCrunch Brand Studio Crunchboard Contact Us Image Credits: Tolga_TEZCAN / Getty Images The irrational exuberance of web3 Ron Miller 11:11 AM PST · December 14, 2021 This year’s hottest new tech terms are definitely “web3” and “metaverse .” The former refers to a decentralized web, based on the blockchain, while the latter is a combination of the internet and augmented and virtual reality. It is possible that we will see a merging of the concepts at some point. That is, if the concepts ever turn into anything. Suddenly, out of nowhere in 2021, we began using these terms like they were a given and we were all privy to the change. Like a giant game of social telephone, the blockchain became “web3” and AR and VR morphed into “the metaverse” — and we all went along for the ride. Yet the blockchain idea has existed for years as a concept , long before bitcoin decided to use it as a ledger for its digital currency idea in 2008. I began covering the notion of blockchain in the enterprise in 2017 when a colleague pointed out it could be the next big thing, a way to establish trust through an irrefutable record. It was interesting at first, but was often referred to as a solution looking for a problem, and I eventually lost interest. Here’s what I wrote in a 2018 article about the blockchain in the enterprise: The blockchain is in the middle of a major hype cycle at the moment, and that makes it hard for many people to take it seriously, but if you look at the core digital ledger technology, there is tremendous potential to change the way we think about trust in business. Yet these are still extremely early days and there are a number of missing pieces that need to be in place for the blockchain to really take off in the enterprise. At the time, I wrote about a number of promising startups. I talked to people in charge of blockchain at larger companies like IBM and SAP as they dabbled in the idea of bringing blockchain-based solutions for the enterprise. I was actually pretty pumped about it, too, until I realized it was more hype than reality and moved on. Three years later, it’s back, and once again, it’s the next big thing — and it’s got a new name to go with it. Techcrunch event Join the Disrupt 2026 Waitlist Add yourself to the Disrupt 2026 waitlist to be first in line when Early Bird tickets drop. Past Disrupts have brought Google Cloud, Netflix, Microsoft, Box, Phia, a16z, ElevenLabs, Wayve, Hugging Face, Elad Gil, and Vinod Khosla to the stages — part of 250+ industry leaders driving 200+ sessions built to fuel your growth and sharpen your edge. Plus, meet the hundreds of startups innovating across every sector. Join the Disrupt 2026 Waitlist Add yourself to the Disrupt 2026 waitlist to be first in line when Early Bird tickets drop. Past Disrupts have brought Google Cloud, Netflix, Microsoft, Box, Phia, a16z, ElevenLabs, Wayve, Hugging Face, Elad Gil, and Vinod Khosla to the stages — part of 250+ industry leaders driving 200+ sessions built to fuel your growth and sharpen your edge. Plus, meet the hundreds of startups innovating across every sector. San Francisco | October 13-15, 2026 W AITLIST NOW Stephen Diehl, an engineer and blogger from the U.K., sees the web3 moniker as pure repackaging of the same technology with the same issues. “At its core, web3 is a vapid marketing campaign that attempts to reframe the public’s negative associations of crypto assets into a false narrative about disruption of legacy tech company hegemony,” Diehl wrote in a December 4 blog post that pulled no punches. 7 investors discuss web3’s present and peer into its future What he means is that web3 advocates say that decentralization could reduce the power of the biggest internet companies — Amazon, Google, Microsoft and Facebook — and give it back to the users. But will it? Kevin Werbach, a Wharton professor and author of “ The Blockchain and the New Architecture of Trust ,” said that the technology might not be as far along as the hype, and the current popularity of digital assets doesn’t yet equate to a threat to Big Tech. “Web3 is, to some extent, a meme or marketing brand around a variety of blockchain and cryptocurrency activity, which was already happening. Like the enterprise blockchain wave of a few years ago, web3 is being hyped as much farther along in adoption than it truly is. Lots of people are trading crypto and buying NFTs, but that doesn’t necessarily mean they are adopting distributed alternatives to major tech platforms,” he said. But Hilary Carter, VP of research at the Linux Foundation who spent three years at The Blockchain Research Institute in Toronto, sees a promising set of technologies that could be ready to scale to take on web3 hype. “Web3 simply could not even exist without the innovation that is blockchain. The road has not been easy, as the technology has been too often dismissed for some early failures. But those failures drove innovation to address issues like scale,” Carter told me. She said that the problems around scale and sustainability that I saw in my blockchain coverage several years ago have been solved in the ensuing years. “I think today, with those issues having been addressed, we’re seeing the maturity of the blockchain ecosystem, so much so that nation-states are building ‘central bank digital currency,’ which is probably the use case that will demand the most throughput,” she said. Certainly, financial institutions are embracing the technology. In its annual blockchain survey , Deloitte reported that nearly 80% of the respondents believed that digital assets would be important or somewhat important to their industries within the next two years. There is also a persistent belief that the speeding of digital transformation amid the pandemic is driving a corresponding shift to more widespread acceptance of digital currencies. While the idea of digital currency in an increasingly digital world certainly makes sense, it’s a bigger leap to say that the blockchain can support a broad set of use cases, including replacing current internet infrastructure, as supporters suggest. Diehl certainly doesn’t believe so. “On a compute basis, blockchain networks don’t scale except by becoming the very same plutocratic and centralized systems they allegedly were designed to replace,” he wrote. But Carter sees room for both digital currency and other use cases. “Sure. I do see both digital currency and blockchain implementations advancing significantly,” she said. Werbach adds that there are some promising examples, but there is reason to be skeptical about web3 as an overall concept. “New systems built from scratch, such as in DeFi (decentralized finance), don’t have the problem of legacy firms, but they face the challenge of scaling and mass adoption. Many so-called ‘web3’ solutions are not as decentralized as they seem, while others have yet to show they are scalable, secure and accessible enough for the mass market. That may change, but it’s not a given that all these limitations will be overcome,” he said. And there’s the rub. Whether web3 is a marketing slogan or a true technological trend, there is certainly a lot of money and tech behind it. Yet there are clearly still substantial obstacles and challenges ahead, and only time will tell if web3 can overcome them and live up to the latest hype cycle. The blockchain begins finding its way in the enterprise Topics Crypto , digital currency , digital transformation , web3 Ron Miller Enterprise Reporter Ron Miller was an enterprise reporter at TechCrunch. Previously, he was a long-time Contributing Editor at EContent Magazine. Past regular gigs included CITEworld, DaniWeb, TechTarget, Internet Evolution and FierceContentManagement. Disclosures: Ron was formerly corporate blogger for Intronis where he wrote once weekly on IT issues. He has contributed to various corporate blogs in the past including Ness, Novell and the IBM Mid-market Blogger Program. View Bio Dates TBD Locations TBA Plan ahead for the 2026 StrictlyVC events. Hear straight-from-the-source candid insights in on-stage fireside sessions and meet the builders and backers shaping the industry. Join the waitlist to get first access to the lowest-priced tickets and important updates. Waitlist Now Most Popular Google announces a new protocol to facilitate commerce using AI agents Ivan Mehta The most bizarre tech announced so far at CES 2026 Lauren Forristal Yes, LinkedIn banned AI agent startup Artisan, but now it’s back Julie Bort OpenAI unveils ChatGPT Health, says 230 million users ask about health each week Amanda Silberling Techcrunch event Join the Disrupt 2026 Waitlist Add yourself to the Disrupt 2026 waitlist to be first in line when Early Bird tickets drop. Past Disrupts have brought Google Cloud, Netflix, Microsoft, Box, Phia, a16z, ElevenLabs, Wayve, Hugging Face, Elad Gil, and Vinod Khosla to the stages — part of 250+ industry leaders driving 200+ sessions built to fuel your growth and sharpen your edge. Plus, meet the hundreds of startups innovating across every sector. Join the Disrupt 2026 Waitlist Add yourself to the Disrupt 2026 waitlist to be first in line when Early Bird tickets drop. Past Disrupts have brought Google Cloud, Netflix, Microsoft, Box, Phia, a16z, ElevenLabs, Wayve, Hugging Face, Elad Gil, and Vinod Khosla to the stages — part of 250+ industry leaders driving 200+ sessions built to fuel your growth and sharpen your edge. Plus, meet the hundreds of startups innovating across every sector. San Francisco | October 13-15, 2026 W AITLIST NOW How Quilt solved the heat pump’s biggest challenge Tim De Chant A viral Reddit post alleging fraud from a food delivery app turned out to be AI-generated Amanda Silberling Founder of spyware maker pcTattletale pleads guilty to hacking and advertising surveillance software Zack Whittaker Loading the next article Error loading the next article X LinkedIn Facebook Instagram youTube Mastodon Threads Bluesky TechCrunch Staff Contact Us Advertise Crunchboard Jobs Site Map Terms of Service Privacy Policy RSS Terms of Use Code of Conduct CES 2026 Elon Musk v OpenAI Clicks Communicator Gmail Larry Page Tech Layoffs ChatGPT © 2025 TechCrunch Media LLC. | 2026-01-13T08:48:28 |
https://support.apple.com/en-az/105082 | Delete your Safari history, cache, and cookies on iPhone - Apple Support (AZ) Products, services, and OS functions may not be available in this country. Apple Mac iPad iPhone Watch AirPods TV & Home Entertainment Support Where to Buy Delete your Safari history, cache, and cookies on iPhone In your iPhone settings, you can choose to delete your Safari history, cookies, cache, or a specific website from your history. You can also turn on content blockers. Delete history, cache, and cookies Clear cookies and cache, but keep your history Delete a website from your history Block cookies Use content blockers Delete history, cache, and cookies Go to Settings > Apps > Safari. Scroll down and tap Clear History and Website Data. Confirm the timeframe that you want to clear, then tap Clear History. This doesn't change your AutoFill information. If this button is gray, there is either no data to clear, or you might need to check your web content restrictions in Screen Time . Clear cookies and cache, but keep your history Go to Settings > Apps > Safari > Advanced > Website Data. Tap Remove All Website Data. If this button is gray, there is either no data to clear, or you might need to check your web content restrictions in Screen Time . Tap Remove Now. This clears data that's used for tracking, and by websites to save login information for faster browsing. Delete a website from your history Open the Safari app, then tap the More button . Tap Bookmarks. Tap the History button , then tap the More button again. Tap Select Websites, then select one or more websites to delete from your history. Tap the Trash button . Block cookies If you want to block cookies (data a site places on your device to remember you), go to Settings > Apps > Safari > Advanced. Turn on Block All Cookies. Tap Block All. This removes all existing cookies and website data. Safari quits, and your tabs are reloaded. If you block cookies, some webpages might not work. Here are some examples: You will likely not be able to sign in to a site, even when using your correct username and password. You might see a message that cookies are required or that your browser's cookies are off. Some features on a site might not work. Use content blockers Go to the App Store and download a content blocking app (third-party apps and extensions that let Safari block cookies, images, resources, pop-ups, and other content). Then tap Settings > Apps > Safari > Extensions. Tap to turn on a listed content blocker. You can use more than one content blocker. If you need help, contact the app developer . Information about products not manufactured by Apple, or independent websites not controlled or tested by Apple, is provided without recommendation or endorsement. Apple assumes no responsibility with regard to the selection, performance, or use of third-party websites or products. Apple makes no representations regarding third-party website accuracy or reliability. Contact the vendor for additional information. Published Date: September 17, 2025 Helpful? Yes No Character limit: 250 Maximum character limit is 250. Please don’t include any personal information in your comment. Submit Thanks for your feedback. Related topics Apple Footer Apple Support Delete your Safari history, cache, and cookies on iPhone Azerbaijan Copyright © 2025 Apple Inc. All rights reserved. Terms of Use Privacy Policy | 2026-01-13T08:48:28 |
https://aws.amazon.com/terms/?nc1=f_pr | AWS Site Terms Skip to main content Filter: All English Contact us AWS Marketplace Support My account Search Filter: All Sign in to console Create account AWS Site Terms Last Updated: June 4, 2025 Welcome to the Amazon Web Services site (the “AWS Site”). Amazon Web Services, Inc. and/or its affiliates (“AWS”) provides the AWS Site to you subject to the following terms of use (“Site Terms”). By visiting the AWS Site, you accept the Site Terms. Please read them carefully. In addition, when you use any current or future AWS services, content or other materials, you also will be subject to the AWS Customer Agreement or other agreement governing your use of our services (the “Agreement”). PRIVACY Please review our Privacy Notice , which also governs your visit to the AWS Site, to understand our practices. ELECTRONIC COMMUNICATIONS When you visit the AWS Site or send e-mails to us, you are communicating with us electronically. You consent to receive communications from us electronically. We will communicate with you by e-mail or by posting notices on the AWS Site. You agree that all agreements, notices, disclosures and other communications that we provide to you electronically satisfy any legal requirement that such communications be in writing. COPYRIGHT All content included on the AWS Site, such as text, graphics, logos, button icons, images, audio clips, digital downloads, data compilations, and software, is the property of AWS or its content suppliers and protected by United States and international copyright laws. The compilation of all content on the AWS Site is the exclusive property of AWS and protected by U.S. and international copyright laws. All software used on the AWS Site is the property of AWS or its software suppliers and protected by United States and international copyright laws. TRADEMARKS “Amazon Web Services” and all related marks, including logos, graphic designs, and service names, are trademarks or trade dress of AWS in the U.S. and other countries. AWS’s trademarks and trade dress may not be used in connection with any product or service that is not AWS’s, in any manner that is likely to cause confusion among customers, or in any manner that disparages or discredits AWS. All other trademarks not owned by AWS that appear on this Site are the property of their respective owners, who may or may not be affiliated with, connected to, or sponsored by AWS. LICENSE AND SITE ACCESS AWS grants you a limited license to access and make personal use of the AWS Site and not to download (other than page caching) or modify it, or any portion of it, except with express written consent of AWS. This license does not include any resale or commercial use of the AWS Site or its contents; any derivative use of the AWS Site or its contents; any downloading or copying of any other users’ account information; or any use of data mining, robots, or similar data gathering and extraction tools. Unless otherwise specified by AWS in a separate license, your right to use any software, data, documentation or other materials that you access or download through the AWS Site is subject to these Site Terms or, if you have an AWS account, the Agreement. The materials hosted on docs.aws.amazon.com are licensed as follows: documentation (e.g., user guides, developer guides, other publications) is licensed under CC-BY-SA-4.0, while any code therein is licensed under MIT-0. The AWS Site or any portion of the AWS Site may not be reproduced, duplicated, copied, sold, resold, visited, or otherwise exploited for any commercial purpose without express written consent or license of AWS. You may not frame or utilize framing techniques to enclose any trademark, logo, or other proprietary information (including images, text, page layout, or form) of AWS without express written consent. You may not use any meta tags or any other “hidden text” utilizing AWS’s name or trademarks without the express written consent of AWS. Any unauthorized use terminates the permission or license granted by AWS. You are granted a limited, revocable, and nonexclusive right to create a hyperlink to the home page of the AWS Site, so long as the link does not portray AWS, or its products or services in a false, misleading, derogatory, or otherwise offensive matter. You may not use any AWS logo or other proprietary graphic or trademark as part of the link without express written permission. YOUR ACCOUNT If you use the AWS Site, you are responsible for maintaining the confidentiality of your AWS account and password and for restricting access to your computer, and you agree to accept responsibility for all activities that occur under your account or password. AWS reserves the right to refuse service, terminate accounts, remove or edit content in its sole discretion. REVIEWS, COMMENTS, COMMUNICATIONS, AND OTHER CONTENT You may post reviews, comments and other content; and submit suggestions, ideas, comments, questions, or other information, so long as the content is not illegal, obscene, threatening, defamatory, invasive of privacy, infringing of intellectual property rights, or otherwise injurious to third parties or objectionable and does not consist of or contain software viruses, political campaigning, commercial solicitation, chain letters, mass mailings, or any form of “spam.” You may not use a false e-mail address, impersonate any person or entity, or otherwise mislead as to the origin of a card or other content. AWS reserves the right (but not the obligation) to remove or edit such content, but does not regularly review posted content. If you do post content or submit material, and unless we indicate otherwise, you grant AWS a nonexclusive, royalty-free, perpetual, irrevocable, and fully sublicensable right to use, reproduce, modify, adapt, publish, translate, create derivative works from, distribute, and display such content throughout the world in any media. You grant AWS and sublicensees the right to use the name that you submit in connection with such content, if they choose. You and third parties may be permitted to upload certain software (including machine images), data, text, audio, video, images or other content (“Third Party Content”) to community areas of the AWS Site. You acknowledge that (a) AWS has not tested or screened Third Party Content, (b) you use any Third Party Content is at your sole risk, and (c) Third Party Content may be subject to separate license terms as determined by the person posting such content. You represent and warrant that you own or otherwise control all of the rights to the content, including any Third Party Content, that you post; that the content is accurate; that use of the content you supply does not violate this policy and will not cause injury to any person or entity; and that you will indemnify AWS for all claims resulting from content you supply. AWS has the right but not the obligation to monitor and edit or remove any activity or content. AWS takes no responsibility and assumes no liability for any content posted by you or any third party. COPYRIGHT COMPLAINTS AWS respects the intellectual property of others. If you believe that your work has been copied in a way that constitutes copyright infringement, please follow our Notice and Procedure for Making Claims of Copyright Infringement . DISCLAIMER OF WARRANTIES AND LIMITATION OF LIABILITY THE AWS SITE AND ALL INFORMATION, CONTENT, MATERIALS, PRODUCTS (INCLUDING ANY SOFTWARE) AND SERVICES INCLUDED ON OR OTHERWISE MADE AVAILABLE TO YOU THROUGH THIS SITE ARE PROVIDED BY AWS ON AN “AS IS” AND “AS AVAILABLE” BASIS, UNLESS OTHERWISE SPECIFIED IN THE AGREEMENT. EXCEPT TO THE EXTENT PROHIBITED BY LAW, OR TO THE EXTENT ANY LEGAL RIGHTS APPLY THAT CANNOT BE EXCLUDED, LIMITED OR WAIVED, AWS MAKES NO REPRESENTATIONS OR WARRANTIES OF ANY KIND, EXPRESS OR IMPLIED, AS TO THE OPERATION OF THIS SITE OR THE INFORMATION, CONTENT, MATERIALS, PRODUCTS (INCLUDING ANY SOFTWARE) OR SERVICES INCLUDED ON OR OTHERWISE MADE AVAILABLE TO YOU THROUGH THE AWS SITE, UNLESS OTHERWISE SPECIFIED IN WRITING. YOU EXPRESSLY AGREE THAT YOUR USE OF THIS SITE IS AT YOUR SOLE RISK. TO THE FULL EXTENT PERMISSIBLE BY APPLICABLE LAW, AWS DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. AWS DOES NOT WARRANT THAT THIS SITE; INFORMATION, CONTENT, MATERIALS, PRODUCTS (INCLUDING ANY SOFTWARE) OR SERVICES INCLUDED ON OR OTHERWISE MADE AVAILABLE TO YOU THROUGH THE AWS SITE; ITS SERVERS; OR E-MAIL SENT FROM AWS ARE FREE OF VIRUSES OR OTHER HARMFUL COMPONENTS. AWS WILL NOT BE LIABLE FOR ANY DAMAGES OF ANY KIND ARISING FROM THE USE OF THE AWS SITE OR FROM ANY INFORMATION, CONTENT, MATERIALS, PRODUCTS (INCLUDING SOFTWARE) OR SERVICES INCLUDED ON OR OTHERWISE MADE AVAILABLE TO YOU THROUGH THE AWS SITE, INCLUDING, BUT NOT LIMITED TO DIRECT, INDIRECT, INCIDENTAL, PUNITIVE, AND CONSEQUENTIAL DAMAGES, UNLESS OTHERWISE SPECIFIED IN THE AGREEMENT. CERTAIN STATE LAWS DO NOT ALLOW LIMITATIONS ON IMPLIED WARRANTIES OR THE EXCLUSION OR LIMITATION OF CERTAIN DAMAGES. IF THESE LAWS APPLY TO YOU, SOME OR ALL OF THE ABOVE DISCLAIMERS, EXCLUSIONS, OR LIMITATIONS MAY NOT APPLY TO YOU, AND YOU MIGHT HAVE ADDITIONAL RIGHTS. APPLICABLE LAW By visiting the AWS Site, you agree that the laws of the state of Washington, without regard to principles of conflict of laws, will govern these Site Terms and any dispute of any sort that might arise between you and AWS. DISPUTES Any dispute relating in any way to your visit to the AWS Site or to services provided by AWS or through the AWS Site in which the aggregate total claim for relief sought on behalf of one or more parties exceeds $7,500 shall be adjudicated in any state or federal court in King County, Washington, and you consent to exclusive jurisdiction and venue in such courts. SITE POLICIES, MODIFICATION, AND SEVERABILITY Please review our other policies on the AWS Site. These policies also govern your visit to the AWS Site. We reserve the right to make changes to the AWS Site, policies, and these Site Terms at any time. If any of these conditions shall be deemed invalid, void, or for any reason unenforceable, that condition shall be deemed severable and shall not affect the validity and enforceability of any remaining condition. OUR ADDRESS Amazon Web Services, Inc. P.O. Box 81226 Seattle, WA 98108-1226 http://aws.amazon.com NOTICE AND PROCEDURE FOR MAKING CLAIMS OF COPYRIGHT INFRINGEMENT If you believe that your work has been copied in a way that constitutes copyright infringement, please provide our copyright agent the written information specified below. Please note that this procedure is exclusively for notifying AWS that your copyrighted material has been infringed. An electronic or physical signature of the person authorized to act on behalf of the owner of the copyright interest; A description of the copyrighted work that you claim has been infringed upon; A description of where the material that you claim is infringing is located on the Site; Your address, telephone number, and e-mail address; A statement by you that you have a good-faith belief that the disputed use is not authorized by the copyright owner, its agent, or the law; A statement by you, made under penalty of perjury, that the above information in your notice is accurate and that you are the copyright owner or authorized to act on the copyright owner’s behalf. AWS’s Copyright Agent for notice of claims of copyright infringement can be reached as follows: Copyright Agent/Amazon Web Services Amazon.com Legal Department P.O. Box 81226 Seattle, WA 98108 phone: (206) 266-4064 fax: (206) 266-7010 e-mail: trustandsafety@support.aws.com Courier address: Copyright Agent/Amazon Web Services Amazon.com Legal Department 410 Terry Avenue North Seattle, WA 98109-5210 USA Create an AWS account Learn What Is AWS? What Is Cloud Computing? What Is Agentic AI? Cloud Computing Concepts Hub AWS Cloud Security What's New Blogs Press Releases Resources Getting Started Training AWS Trust Center AWS Solutions Library Architecture Center Product and Technical FAQs Analyst Reports AWS Partners Developers Builder Center SDKs & Tools .NET on AWS Python on AWS Java on AWS PHP on AWS JavaScript on AWS Help Contact Us File a Support Ticket AWS re:Post Knowledge Center AWS Support Overview Get Expert Help AWS Accessibility Legal English Back to top Amazon is an Equal Opportunity Employer: Minority / Women / Disability / Veteran / Gender Identity / Sexual Orientation / Age. x facebook linkedin instagram twitch youtube podcasts email Privacy Site terms Cookie Preferences © 2026, Amazon Web Services, Inc. or its affiliates. All rights reserved. | 2026-01-13T08:48:28 |
https://stackoverflow.blog/2025/11/12/2025-8-release-introduces-stack-overflow-internal-the-next-generation-of-enterprise-knowledge-intelligence/ | 2025.8 release introduces Stack Overflow Internal: The next generation of enterprise knowledge intelligence - Stack Overflow Blog Loading… Everything Productivity AI/ML Open Source Business Hub Company Releases Podcast Newsletter Stack Overflow Business Stack Internal : the knowledge intelligence layer that powers enterprise AI. Stack Data Licensing : decades of verified, technical knowledge to boost AI performance and trust. Stack Ads : engage developers where it matters — in their daily workflow. November 12, 2025 2025.8 release introduces Stack Overflow Internal: The next generation of enterprise knowledge intelligence Today, we’re excited to introduce Stack Overflow Internal—the next evolution of our enterprise platform and the future of Stack Overflow for Teams. More than a rebrand, Stack Internal is a strategic leap forward. It represents our continued mission to be the most trusted source of knowledge for technologists—and our growing role in powering the intelligence layer of enterprise AI. Built for an AI-first era Stack Overflow for Teams has always connected people with knowledge. Stack Internal takes this even further by transforming our platform into an enterprise knowledge intelligence layer that captures, validates, and delivers trusted information into the systems and workflows your teams rely on every day. Whether you’re a developer working in an IDE, a product manager in Microsoft Teams, or a data scientist using AI copilots, Stack Internal ensures that the knowledge you need is accurate, current, and available—wherever work happens. What’s new in the Stack Internal 2025.8 release This release introduces powerful features that help organizations consolidate scattered knowledge, connect your AI agents with real-time answers, and accelerate onboarding, delivery, and decision-making. MCP Server–Free Trial Extended The Model Context Protocol (MCP) Server connects agentic AI developer tools—like GitHub Copilot, ChatGPT, and Cursor—directly to your enterprise’s verified knowledge in Stack Internal. The MCP server enables: Grounded, attributed AI responses based on real organizational knowledge Bi-directional flows, so agents can also suggest updates and keep your knowledge fresh Full privacy and control, with server deployments running inside your infrastructure The Stack Internal MCP Server is available for all enterprise customers, and the free trial period has been extended. With it, you can power AI across your org while maintaining governance, accuracy, and trust. Try the Stack Internal MCP Server for free today. Knowledge Ingestion Pilot One of the biggest challenges in enterprise knowledge management is fragmentation. Knowledge Ingestion solves this by transforming existing content from tools like Confluence, MS Teams, Slack, and ServiceNow into trusted, structured knowledge inside Stack Internal. Using AI-powered ingestion, confidence scoring, and a scalable human-in-the-loop validation workflow, this feature ensures that only high-quality, relevant knowledge is published. With Knowledge Ingestion, your teams can: Seed and validate historical content with Stack Internal Reduce time-to-value and onboarding effort Create a strong foundation for AI-native workflows like search, copilots, and autonomous agents The pilot is currently open to select enterprise customers. Contact your Success Manager to learn more about use cases for Knowledge Ingestion and how it may help your organization. Moving forward with Stack Internal As organizations race to adopt AI, one truth remains: AI is only as powerful as the knowledge it’s built on. Stack Internal delivers the foundation for enterprise AI—accurate, validated, and grounded in real work. It captures trusted knowledge, keeps it fresh, and delivers it directly into the tools where teams operate: Microsoft 365, Slack, IDEs, and AI copilots. This turns knowledge into action—and action into competitive advantage. Here’s what sets Stack Internal apart: Knowledge starts where work happens It’s strengthened through AI + human validation And it flows into the tools and agents that drive modern work This release marks more than a name change—it’s the beginning of a new chapter for enterprise knowledge. One that helps your organization scale expertise, accelerate development, and adopt AI responsibly. Let’s build that future—together. Author s Carrie Koos Staff Releases Stack Internal Stack Overflow Internal Where developers & technologists share private knowledge with coworkers. Learn more Latest releases January 5, 2026 What’s new at Stack Overflow: January 2026 December 16, 2025 Your 2025 Stacked: A year of knowledge, community, and impact December 1, 2025 What’s new at Stack Overflow: December 2025 November 12, 2025 2025.8 release introduces Stack Overflow Internal: The next generation of enterprise knowledge intelligence Add to the discussion Login with your stackoverflow.com account to take part in the discussion. Our Stack Stack Internal Features Customers Security Pricing Stack Data Licensing Stack Ads Partnerships Services Stack Overflow Company Leadership Press Careers Social Impact Support Contact Stack Overflow help Stack Internal help Terms Privacy policy Cookie policy Your Privacy Choices Elsewhere Blog Dev Newsletter Podcast Releases Dev Survey Site design / logo © 2026 Stack Exchange Inc. Light Dark Auto | 2026-01-13T08:48:28 |
https://stackoverflow.blog/2025/06/18/smarter-teams-brighter-insights-stack-overflow-for-teams-business-summer-bundle/ | Smarter teams, brighter insights: Stack Overflow for Teams Business summer bundle - Stack Overflow Blog Loading… Everything Productivity AI/ML Open Source Business Hub Company Releases Podcast Newsletter Stack Overflow Business Stack Internal : the knowledge intelligence layer that powers enterprise AI. Stack Data Licensing : decades of verified, technical knowledge to boost AI performance and trust. Stack Ads : engage developers where it matters — in their daily workflow. June 18, 2025 Smarter teams, brighter insights: Stack Overflow for Teams Business summer bundle Read on to see the latest features coming to Stack Overflow for Teams Business users! When summer hits, it’s time to clear out clutter, double down on what works, and set yourself up for smoother days ahead. That’s exactly what the latest Stack Overflow for Teams release is all about: powerful updates that help you deliver insights where they matter, boost engagement across your team, and manage content access with more flexibility than ever. Whether you're using Teams in Slack, Microsoft 365, or our web app, this summer bundle makes it easier to keep your knowledge flowing—and your team thriving. Read on to see the latest features coming to Stack Overflow for Teams Business users! Executive Report Let your work speak for itself. The new Executive Report is a reimagined take on the Weekly Dashboard Report. It's built to help teams tell a bigger story—one about how your knowledge community fuels the business. You’ll get a ready-to-share overview that includes: Trending topics across your org Resource coverage for emerging themes Engagement breakdowns and content interaction Top contributors and SMEs Best of all? You can share the report with executive stakeholders—even if they’re not Stack Overflow for Teams users. Weekly digests in Microsoft Teams and Slack Wherever your team works, your knowledge can now follow. New team digests deliver a weekly summary to Slack or Microsoft Teams channels, highlighting: Top contributors by user and department Usage metrics Most pressing unanswered questions Prefer a one-on-one update? Personal digests send a tailored DM with: Your activity highlights Relevant unanswered questions A quick look at your impact Personal digests are off by default. You can turn them on anytime in Slack or Teams app settings. Flexible user group permissions You asked, we delivered: moderators now have the power to manage user groups. That means they can: Create, update, and delete user groups Ensure the right people see the right content Help organize and scale knowledge delivery—without admin access Admins still control system-level settings, but moderators now have more tools to help keep the knowledge base clear, clean, and targeted. Voting enhancements Sometimes the best ideas just need a little nudge. We’ve added two simple UX updates to encourage more participation: Unanswered posts now display a “Vote” prompt instead of a lonely zero Users who haven’t voted recently (30+ days) get a tooltip reminder More feedback → better answers → stronger knowledge. Recently viewed content in search Save time and backtrack faster. Now when you use the search bar, you’ll see a list of your recently viewed content—so you can revisit answers you trust without digging through tabs. Dive deeper Check out the Help Center for more details, or head to your Teams instance now to explore what’s new. Whether you’re sharing insights with leadership, nudging teammates to vote, or just trying to get your day started faster, this release is designed to make every moment on Stack Overflow for Teams more impactful. ☀️ Here’s to a smarter, stronger summer—together. Author s Carrie Koos Staff stack overflow for business Releases Stack Overflow Internal Where developers & technologists share private knowledge with coworkers. Learn more Latest releases January 5, 2026 What’s new at Stack Overflow: January 2026 December 16, 2025 Your 2025 Stacked: A year of knowledge, community, and impact December 1, 2025 What’s new at Stack Overflow: December 2025 November 12, 2025 2025.8 release introduces Stack Overflow Internal: The next generation of enterprise knowledge intelligence Add to the discussion Login with your stackoverflow.com account to take part in the discussion. Our Stack Stack Internal Features Customers Security Pricing Stack Data Licensing Stack Ads Partnerships Services Stack Overflow Company Leadership Press Careers Social Impact Support Contact Stack Overflow help Stack Internal help Terms Privacy policy Cookie policy Your Privacy Choices Elsewhere Blog Dev Newsletter Podcast Releases Dev Survey Site design / logo © 2026 Stack Exchange Inc. Light Dark Auto | 2026-01-13T08:48:28 |
https://dev.to/coder_bhagya_laxmi#main-content | Bhagya Laxmi - DEV Community Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account DEV Community Close Follow User actions Bhagya Laxmi "I am Bhagya Laxmi Yadav, a BCA student passionate about coding, web development, and learning new skills. Joined Joined on Aug 24, 2025 Personal website https://www.linkedin.com/in/bhagya-laxmi-yadav-69052b333 github website Education Techno Institute of Higher Studies, Lucknow — Bachelor of Computer Applications (BCA) Pronouns She/ her More info about @coder_bhagya_laxmi Badges 1 Week Community Wellness Streak For actively engaging with the community by posting at least 2 comments in a single week. Got it Close Writing Debut Awarded for writing and sharing your first DEV post! Continue sharing your work to earn the 4 Week Writing Streak Badge. Got it Close Skills/Languages Frontend: HTML, CSS, Bootstrap, JavaScript, React | Backend: PHP, Node.js, MySQL | Tools: Git/GitHub | Interests: Hackathons & Open Source. Currently learning Frontend with HTML, CSS, Bootstrap, JavaScript & React, and backend with PHP, Node.js & MySQL. Also exploring Git/GitHub, APIs, and cloud deployment for practical development. Post 1 post published Comment 3 comments written Tag 0 tags followed 👉 "My First Step into DEV.to Community" Bhagya Laxmi Bhagya Laxmi Bhagya Laxmi Follow Aug 24 '25 👉 "My First Step into DEV.to Community" # beginners # community # learning # devto Comments 1 comment 1 min read Want to connect with Bhagya Laxmi? Create an account to connect with Bhagya Laxmi. You can also sign in below to proceed if you already have an account. Create Account Already have an account? Sign in loading... 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV DEV Community — A space to discuss and keep up software development and manage your software career Home DEV++ Podcasts Videos DEV Education Tracks DEV Challenges DEV Help Advertise on DEV DEV Showcase About Contact Free Postgres Database Software comparisons Forem Shop Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . DEV Community © 2016 - 2026. We're a place where coders share, stay up-to-date and grow their careers. Log in Create account | 2026-01-13T08:48:28 |
https://www.linkedin.com/legal/user-agreement?session_redirect=&trk=registration-frontend_join-form-user-agreement | User Agreement | LinkedIn Skip to main content User Agreement Summary of User Agreement Privacy Policy Professional Community Policies Cookie Policy Copyright Policy Regional Info EU Notice California Privacy Disclosure U.S. State Privacy Laws User Agreement Summary of User Agreement Privacy Policy Professional Community Policies Cookie Policy Copyright Policy Regional Info EU Notice California Privacy Disclosure U.S. State Privacy Laws User Agreement Effective on November 3, 2025 Our mission is to connect the world’s professionals to allow them to be more productive and successful. Our services are designed to promote economic opportunity for our members by enabling you and millions of other professionals to meet, exchange ideas, learn, and find opportunities or employees, work, and make decisions in a network of trusted relationships. Table of Contents: Introduction Obligations Rights and Limits Disclaimer and Limit of Liability Termination Governing Law and Dispute Resolution General Terms LinkedIn “Dos and Don’ts” Complaints Regarding Content How To Contact Us Introduction 1.1 Contract When you use our Services you agree to all of these terms. Your use of our Services is also subject to our Cookie Policy and our Privacy Policy, which covers how we collect, use, share, and store your personal information. By creating a LinkedIn account or accessing or using our Services (described below), you are agreeing to enter into a legally binding contract with LinkedIn (even if you are using third party credentials or using our Services on behalf of a company). If you do not agree to this contract (“Contract” or “User Agreement”), do not create an account or access or otherwise use any of our Services. If you wish to terminate this Contract at any time, you can do so by closing your account and no longer accessing or using our Services. As a Visitor or Member of our Services, the collection, use, and sharing of your personal data is subject to our Privacy Policy , our Cookie Policy and other documents referenced in our Privacy Policy , and updates. You acknowledge and have read our Privacy Policy . Services This Contract applies to LinkedIn.com, LinkedIn-branded apps, and other LinkedIn-related sites, apps, communications, and other services that state that they are offered under this Contract (“Services”), including the offsite collection of data for those Services, such as via our ads and the “Apply with LinkedIn” and “Share with LinkedIn” plugins. LinkedIn and other Key Terms You are entering into this Contract with LinkedIn (also referred to as “we” and “us”). Designated Countries . We use the term “Designated Countries” to refer to countries in the European Union (EU), European Economic Area (EEA), and Switzerland. If you reside in the “Designated Countries”, you are entering into this Contract with LinkedIn Ireland Unlimited Company (“LinkedIn Ireland”) and LinkedIn Ireland will be the controller of your personal data provided to, or collected by or for, or processed in connection with our Services. If you reside outside of the “Designated Countries”, you are entering into this Contract with LinkedIn Corporation (“LinkedIn Corp.”) and LinkedIn Corp. will be the controller of (or business responsible for) your personal data provided to, or collected by or for, or processed in connection with our Services. Affiliates . Affiliates are companies controlling, controlled by or under common control with us, including, for example, LinkedIn Ireland, LinkedIn Corporation, LinkedIn Singapore and Microsoft Corporation or any of its subsidiaries (e.g., Github, Inc.). Social Action . Actions that members take on our services such as likes, comments, follows, sharing content. Content . Content includes, for example, feed posts, feedback, comments, profiles, articles (and contributions), group posts, job postings, messages (including InMails), videos, photos, audio, and/or PDFs. 1.2 Members and Visitors This Contract applies to Members and Visitors. When you register and join the LinkedIn Services, you become a “Member”. If you have chosen not to register for our Services, you may access certain features as a “Visitor.” 1.3 Changes We may make changes to this Contract. We may modify this Contract, our Privacy Policy and our Cookie Policy from time to time. If we materially change these terms or if we are legally required to provide notice, we will provide you notice through our Services, or by other means, to provide you the opportunity to review the changes before they become effective. However, we may not always provide prior notice of changes to these terms (1) when those changes are legally required to be implemented with immediate effect, or (2) when those changes relate to a newly launched service or feature. We agree that changes cannot be retroactive. If you object to any of these changes, you may close your account . Your continued use of our Services after we publish or send a notice about our changes to these terms means that you are consenting to the updated terms as of their effective date. 2. Obligations 2.1 Service Eligibility Here are some promises that you make to us in this Contract: You’re eligible to enter into this Contract and you are at least our “Minimum Age.” The Services are not for use by anyone under the age of 16. To use the Services, you agree that: (1) you must be the "Minimum Age" (described below) or older; (2) you will only have one LinkedIn account, which must be in your real name; and (3) you are not already restricted by LinkedIn from using the Services. Creating an account with false information is a violation of our terms, including accounts registered on behalf of others or persons under the age of 16. “Minimum Age” means 16 years old. However, if law requires that you must be older in order for LinkedIn to lawfully provide the Services to you without parental consent (including using your personal data) then the Minimum Age is such older age. Learn More 2.2 Your Account You will keep your password a secret You will not share your account with anyone else and will follow our policies and the law. Members are account holders. You agree to: (1) protect against wrongful access to your account (e.g., use a strong password and keep it confidential); (2) not share or transfer your account or any part of it (e.g., sell or transfer the personal data of others by transferring your connections); and (3) follow the law, our list of Dos and Don’ts (below), and our Professional Community Policies . Learn More You are responsible for anything that happens through your account unless you close it or report misuse. As between you and others (including your employer), your account belongs to you. However, if the Services were purchased by another party for you to use in connection with your work for them (e.g., Recruiter seat or LinkedIn Learning subscription bought by your employer), the party paying for such Service has the right to control access to and get reports on your use of such paid Service; however, they do not have rights to your personal account. 2.3 Payment You’ll honor your payment obligations and you are okay with us storing your payment information. You understand that there may be fees and taxes that are added to our prices. Refunds are subject to our policy, and we may modify our prices and those modified prices will apply prospectively. If you buy any of our paid Services, you agree to pay us the applicable fees and taxes and you agree to the additional terms specific to the paid Services. Failure to pay these fees will result in the termination of your paid Services. Also, you agree that: Your purchase may be subject to foreign exchange fees or differences in prices based on location (e.g., exchange rates). We may store and continue billing your payment method (e.g., credit card), even after it has expired, to avoid interruptions in your paid Services and to use it to pay for other Services you may buy. If your primary payment method fails, we may automatically charge a secondary payment method, if you have provided one. You may update or change your payment method. Learn more If you purchase a subscription, your payment method automatically will be charged at the start of each subscription period for the fees and taxes applicable to that period. To avoid future charges, cancel before the renewal date. Learn how to cancel or suspend your paid subscription Services. We may modify our prices effective prospectively upon reasonable notice to the extent allowed under the law. All of your paid Services are subject to LinkedIn’s refund policy . We may calculate taxes payable by you based on the billing information that you provide us. You can get a copy of your invoice through your LinkedIn account settings under “ Purchase History ”. 2.4 Notices and Messages You’re okay with us providing notices and messages to you through our websites, apps, and contact information. If your contact information is out of date, you may miss out on important notices. You agree that we will provide notices and messages to you in the following ways: (1) within the Services or (2) sent to the contact information you provided us (e.g., email, mobile number, physical address). You agree to keep your contact information up to date. Please review your settings to control and limit the types of messages you receive from us. 2.5 Sharing When you share information on our Services, others can see, copy and use that information. Our Services allow sharing of information (including content) in many ways, such as through your profile, posts, articles, group posts, links to news articles, job postings, messages, and InMails. Depending on the feature and choices you make, information that you share may be seen by other Members, Visitors, or others (on or off of the Services). Where we have made settings available, we will honor the choices you make about who can see content or other information (e.g., message content to your addressees, sharing content only to LinkedIn connections, restricting your profile visibility from search tools, or opting not to notify others of your LinkedIn profile update). For job searching activities, we default to not notifying your connections or the public. So, if you apply for a job through our Services or opt to signal that you are interested in a job, our default is to share it only with the job poster. To the extent that laws allow this, we are not obligated to publish any content or other information on our Services and can remove it with or without notice. 3. Rights and Limits 3.1. Your License to LinkedIn You own all of your original content that you provide to us, but you also grant us a non-exclusive license to it. We’ll honor the choices you make about who gets to see your content, including how it can be used for ads. As between you and LinkedIn, you own your original content that you submit or post to the Services. You grant LinkedIn and our Affiliates the following non-exclusive license to the content and other information you provide (e.g., share, post, upload, and/or otherwise submit) to our Services: A worldwide, transferable and sublicensable right to use, copy, modify, distribute, publicly perform and display, host, and process your content and other information without any further consent, notice and/or compensation to you or others. These rights are limited in the following ways: You can end this license for specific content by deleting such content from the Services, or generally by closing your account, except (a) to the extent you (1) shared it with others as part of the Services and they copied, re-shared it or stored it, (2) we had already sublicensed others prior to your content removal or closing of your account, or (3) we are required by law to retain or share it with others, and (b) for the reasonable time it takes to remove the content you delete from backup and other systems. We will not include your content in advertisements for the products and services of third parties to others without your separate consent (including sponsored content). However, without compensation to you or others, ads may be served near your content and other information, and your social actions may be visible and included with ads, as noted in the Privacy Policy. If you use a Service feature, we may mention that with your name or photo to promote that feature within our Services, subject to your settings. We will honor the audience choices for shared content (e.g., “Connections only”). For example, if you choose to share your post to "Anyone on or off LinkedIn” (or similar): (a) we may make it available off LinkedIn; (b) we may enable others to publicly share onto third-party services (e.g., a Member embedding your post on a third party service); and/or (c) we may enable search tools to make that public content findable though their services. Learn More While we may edit and make format changes to your content (such as translating or transcribing it, modifying the size, layout or file type, and removing or adding labels or metadata), we will take steps to avoid materially modifying the meaning of your expression in content you share with others. Because you own your original content and we only have non-exclusive rights to it, you may choose to make it available to others, including under the terms of a Creative Commons license . You and LinkedIn agree that if content includes personal data, it is subject to our Privacy Policy. You and LinkedIn agree that we may access, store, process, and use any information (including content and/or personal data) that you provide in accordance with the terms of the Privacy Policy and your choices (including settings). By submitting suggestions or other feedback regarding our Services to LinkedIn, you agree that LinkedIn can use and share (but does not have to) such feedback for any purpose without compensation to you. You promise to only provide content and other information that you have the right to share and that your LinkedIn profile will be truthful. You agree to only provide content and other information that does not violate the law or anyone’s rights (including intellectual property rights). You have choices about how much information to provide on your profile but also agree that the profile information you provide will be truthful. LinkedIn may be required by law to remove certain content and other information in certain countries. 3.2 Service Availability We may change or limit the availability of some features, or end any Service. We may change, suspend or discontinue any of our Services. We may also limit the availability of features, content and other information so that they are not available to all Visitors or Members (e.g., by country or by subscription access). We don’t promise to store or show (or keep showing) any information (including content) that you’ve shared. LinkedIn is not a storage service. You agree that we have no obligation to store, maintain or provide you a copy of any content or other information that you or others provide, except to the extent required by applicable law and as noted in our Privacy Policy. 3.3 Other Content, Sites and Apps Your use of others’ content and information posted on our Services, is at your own risk. Others may offer their own products and services through our Services, and we aren’t responsible for those third-party activities. Others’ Content: By using the Services, you may encounter content or other information that might be inaccurate, incomplete, delayed, misleading, illegal, offensive, or otherwise harmful. You agree that we are not responsible for content or other information made available through or within the Services by others, including Members. While we apply automated tools to review much of the content and other information presented in the Services, we cannot always prevent misuse of our Services, and you agree that we are not responsible for any such misuse. You also acknowledge the risk that others may share inaccurate or misleading information about you or your organization, and that you or your organization may be mistakenly associated with content about others, for example, when we let connections and followers know you or your organization were mentioned in the news. Members have choices about this feature . Others’ Products and Services: LinkedIn may help connect you to other Members (e.g., Members using Services Marketplace or our enterprise recruiting, jobs, sales, or marketing products) who offer you opportunities (on behalf of themselves, their organizations, or others) such as offers to become a candidate for employment or other work or offers to purchase products or services. You acknowledge that LinkedIn does not perform these offered services, employ those who perform these services, or provide these offered products. You further acknowledge that LinkedIn does not supervise, direct, control, or monitor Members in the making of these offers, or in their providing you with work, delivering products or performing services, and you agree that (1) LinkedIn is not responsible for these offers, or performance or procurement of them, (2) LinkedIn does not endorse any particular Member’s offers, and (3) LinkedIn is not an agent or employment agency on behalf of any Member offering employment or other work, products or services. With respect to employment or other work, LinkedIn does not make employment or hiring decisions on behalf of Members offering opportunities and does not have such authority from Members or organizations using our products. For Services Marketplace , (a) you must be at least 18 years of age to procure, offer, or perform services, and (b) you represent and warrant that you have all the required licenses and will provide services consistent with the relevant industry standards and our Professional Community Policies . Others’ Events: Similarly, LinkedIn may help you register for and/or attend events organized by Members and connect with other Members who are attendees at such events. You agree that (1) LinkedIn is not responsible for the conduct of any of the Members or other attendees at such events, (2) LinkedIn does not endorse any particular event listed on our Services, (3) LinkedIn does not review and/or vet any of these events or speakers, and (4) you will adhere to the terms and conditions that apply to such events. 3.4 Limits We have the right to limit how you connect and interact on our Services. LinkedIn reserves the right to limit your use of the Services, including the number of your connections and your ability to contact other Members. LinkedIn reserves the right to restrict, suspend, or terminate your account if you breach this Contract or the law or are misusing the Services (e.g., violating any of the Dos and Don’ts or Professional Community Policies ). We can also remove any content or other information you shared if we believe it violates our Professional Community Policies or Dos and Don’ts or otherwise violates this Contract. Learn more about how we moderate content. 3.5 Intellectual Property Rights We’re providing you notice about our intellectual property rights. LinkedIn reserves all of its intellectual property rights in the Services. Trademarks and logos used in connection with the Services are the trademarks of their respective owners. LinkedIn, and “in” logos and other LinkedIn trademarks, service marks, graphics and logos used for our Services are trademarks or registered trademarks of LinkedIn. 3.6 Recommendations and Automated Processing We use data and other information about you to make and order relevant suggestions and to generate content for you and others. Recommendations: We use the data and other information that you provide and that we have about Members and content on the Services to make recommendations for connections, content, ads, and features that may be useful to you. We use that data and other information to recommend and to present information to you in an order that may be more relevant for you. For example, that data and information may be used to recommend jobs to you and you to recruiters and to organize content in your feed in order to optimize your experience and use of the Services. Keeping your profile accurate and up to date helps us to make these recommendations more accurate and relevant. Learn More Generative AI Features: By using the Services, you may interact with features we offer that automate content generation for you. The content that is generated might be inaccurate, incomplete, delayed, misleading or not suitable for your purposes. Please review and edit such content before sharing with others. Like all content you share on our Services, you are responsible for ensuring it complies with our Professional Community Policies , including not sharing misleading information. The Services may include content automatically generated and shared using tools offered by LinkedIn or others off LinkedIn. Like all content and other information on our Services, regardless of whether it's labeled as created by “AI”, be sure to carefully review before relying on it. 4. Disclaimer and Limit of Liability 4.1 No Warranty This is our disclaimer of legal liability for the quality, safety, or reliability of our Services. LINKEDIN AND ITS AFFILIATES MAKE NO REPRESENTATION OR WARRANTY ABOUT THE SERVICES, INCLUDING ANY REPRESENTATION THAT THE SERVICES WILL BE UNINTERRUPTED OR ERROR-FREE, AND PROVIDE THE SERVICES (INCLUDING CONTENT, OUTPUT AND INFORMATION) ON AN “AS IS” AND “AS AVAILABLE” BASIS. TO THE FULLEST EXTENT PERMITTED UNDER APPLICABLE LAW, LINKEDIN AND ITS AFFILIATES DISCLAIM ANY IMPLIED OR STATUTORY WARRANTY, INCLUDING ANY IMPLIED WARRANTY OF TITLE, ACCURACY, NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. If you plan to use content, output and information for any reason, it is your responsibility to verify its accuracy and fitness for your purposes, because any content, output and information on the service may not reflect accurate, complete, or current information. 4.2 Exclusion of Liability These are the limits of legal liability we may have to you. TO THE FULLEST EXTENT PERMITTED BY LAW (AND UNLESS LINKEDIN HAS ENTERED INTO A SEPARATE WRITTEN AGREEMENT THAT OVERRIDES THIS CONTRACT), LINKEDIN AND ITS AFFILIATES, WILL NOT BE LIABLE IN CONNECTION WITH THIS CONTRACT FOR LOST PROFITS OR LOST BUSINESS OPPORTUNITIES, REPUTATION (E.G., OFFENSIVE OR DEFAMATORY STATEMENTS), LOSS OF DATA (E.G., DOWN TIME OR LOSS, USE OF, OR CHANGES TO, YOUR INFORMATION OR CONTENT) OR ANY INDIRECT, INCIDENTAL, CONSEQUENTIAL, SPECIAL OR PUNITIVE DAMAGES. LINKEDIN AND ITS AFFILIATES WILL NOT BE LIABLE TO YOU IN CONNECTION WITH THIS CONTRACT FOR ANY AMOUNT THAT EXCEEDS (A) THE TOTAL FEES PAID OR PAYABLE BY YOU TO LINKEDIN FOR THE SERVICES DURING THE TERM OF THIS CONTRACT, IF ANY, OR (B) US $1000. 4.3 Basis of the Bargain; Exclusions The limitations of liability in this Section 4 are part of the basis of the bargain between you and LinkedIn and shall apply to all claims of liability (e.g., warranty, tort, negligence, contract and law) even if LinkedIn or its affiliates has been told of the possibility of any such damage, and even if these remedies fail their essential purpose. THESE LIMITATIONS OF LIABILITY DO NOT APPLY TO LIABILITY FOR DEATH OR PERSONAL INJURY OR FOR FRAUD, GROSS NEGLIGENCE OR INTENTIONAL MISCONDUCT, OR IN CASES OF NEGLIGENCE, WHERE A MATERIAL OBLIGATION HAS BEEN BREACHED. A MATERIAL OBLIGATION BEING AN OBLIGATION WHICH FORMS A PREREQUISITE TO OUR DELIVERY OF SERVICES AND ON WHICH YOU MAY REASONABLY RELY, BUT ONLY TO THE EXTENT THAT THE DAMAGES WERE DIRECTLY CAUSED BY THE BREACH AND WERE FORESEEABLE UPON CONCLUSION OF THIS CONTRACT AND TO THE EXTENT THAT THEY ARE TYPICAL IN THE CONTEXT OF THIS CONTRACT. 5. Termination We can each end this Contract, but some rights and obligations survive. Both you and LinkedIn may terminate this Contract at any time with notice to the other. On termination, you lose the right to access or use the Services. The following shall survive termination: Our rights to use and disclose your feedback; Section 3 (subject to 3.1.1); Sections 4, 6, 7, and 8.2 of this Contract; and Any amounts owed by either party prior to termination remain owed after termination. You can visit our Help Center to learn about how to close your account 6. Governing Law and Dispute Resolution In the unlikely event we end up in a legal dispute, depending on where you live, you and LinkedIn agree to resolve it in California courts using California law, Dublin, Ireland courts using Irish law, or as otherwise provided in this section. If you live in the Designated Countries, the laws of Ireland govern all claims related to LinkedIn's provision of the Services, but this shall not deprive you of the mandatory consumer protections under the law of the country to which we direct your Services where you have habitual residence. With respect to jurisdiction, you and LinkedIn agree to choose the courts of the country to which we direct your Services where you have habitual residence for all disputes arising out of or relating to this User Agreement, or in the alternative, you may choose the responsible court in Ireland. If you are a business user within the scope of Article 6(12) of the EU Digital Markets Act (“DMA”) and have a dispute arising out of or in connection with Article 6(12) of the DMA, you may also utilize the alternative dispute resolution mechanism available in the Help Center . For others outside of Designated Countries, including those who live outside of the United States: You and LinkedIn agree that the laws of the State of California, U.S.A., excluding its conflict of laws rules, shall exclusively govern any dispute relating to this Contract and/or the Services. You and LinkedIn both agree that all claims and disputes can be litigated only in the federal or state courts in Santa Clara County, California, USA, and you and LinkedIn each agree to personal jurisdiction in those courts. You may have additional rights of redress and appeal for some decisions made by LinkedIn that impact you. 7. General Terms Here are some important details about the Contract. If a court with authority over this Contract finds any part of it unenforceable, you and we agree that the court should modify the terms to make that part enforceable while still achieving its intent. If the court cannot do that, you and we agree to ask the court to remove that unenforceable part and still enforce the rest of this Contract. This Contract (including additional terms that may be provided by us when you engage with a feature of the Services) is the only agreement between us regarding the Services and supersedes all prior agreements for the Services. If we don't act to enforce a breach of this Contract, that does not mean that LinkedIn has waived its right to enforce this Contract. You may not assign or transfer this Contract (or your membership or use of Services) to anyone without our consent. However, you agree that LinkedIn may assign this Contract to its affiliates or a party that buys it without your consent. There are no third-party beneficiaries to this Contract. You agree that the only way to provide us legal notice is at the addresses provided in Section 10. 8. LinkedIn “Dos and Don’ts” LinkedIn is a community of professionals. This list of “Dos and Don’ts” along with our Professional Community Policies limits what you can and cannot do on our Services, unless otherwise explicitly permitted by LinkedIn in a separate writing (e.g., through a research agreement). 8.1. Dos You agree that you will: Comply with all applicable laws, including, without limitation, privacy laws, intellectual property laws, anti-spam laws, export control laws, laws governing the content shared, and other applicable laws and regulatory requirements; Provide accurate contact and identity information to us and keep it updated; Use your real name on your profile; and Use the Services in a professional manner. 8.2. Don’ts You agree that you will not : Create a false identity on LinkedIn, misrepresent your identity, create a Member profile for anyone other than yourself (a real person), or use or attempt to use another’s account (such as sharing log-in credentials or copying cookies); Develop, support or use software, devices, scripts, robots or any other means or processes (such as crawlers, browser plugins and add-ons or any other technology) to scrape or copy the Services, including profiles and other data from the Services; Override any security feature or bypass or circumvent any access controls or use limits of the Services (such as search results, profiles, or videos); Copy, use, display or distribute any information (including content) obtained from the Services, whether directly or through third parties (such as search tools or data aggregators or brokers), without the consent of the content owner (such as LinkedIn for content it owns); Disclose information that you do not have the consent to disclose (such as confidential information of others (including your employer); Violate the intellectual property rights of others, including copyrights, patents, trademarks, trade secrets or other proprietary rights. For example, do not copy or distribute (except through the available sharing functionality) the posts or other content of others without their permission, which they may give by posting under a Creative Commons license; Violate the intellectual property or other rights of LinkedIn, including, without limitation, (i) copying or distributing our learning videos or other materials, (ii) copying or distributing our technology, unless it is released under open source licenses; or (iii) using the word “LinkedIn” or our logos in any business name, email, or URL except as provided in the Brand Guidelines ; Post (or otherwise share) anything that contains software viruses, worms, or any other harmful code; Reverse engineer, decompile, disassemble, decipher or otherwise attempt to derive the source code for the Services or any related technology that is not open source; Imply or state that you are affiliated with or endorsed by LinkedIn without our express consent (e.g., representing yourself as an accredited LinkedIn trainer); Rent, lease, loan, trade, sell/re-sell or otherwise monetize the Services or related data or access to the same, without LinkedIn’s consent; Deep-link to our Services for any purpose other than to promote your profile or a Group on our Services, without LinkedIn’s consent; Use bots or other unauthorized automated methods to access the Services, add or download contacts, send or redirect messages, create, comment on, like, share, or re-share posts, or otherwise drive inauthentic engagement; Engage in “framing”, “mirroring”, or otherwise simulating the appearance or function of the Services; Overlay or otherwise modify the Services or their appearance (such as by inserting elements into the Services or removing, covering, or obscuring an advertisement included on the Services); Interfere with the operation of, or place an unreasonable load on, the Services (e.g., spam, denial of service attack, viruses, manipulating algorithms); Violate the Professional Community Policies , certain third party terms where applicable, or any additional terms concerning a specific Service that are provided when you sign up for or start using such Service; Use our Services to do anything that is unlawful, misleading, discriminatory, fraudulent or deceitful (e.g. manipulated media that wrongfully depicts a person saying or doing something they did not say or do); and/or Misuse our reporting or appeals process, including by submitting duplicative, fraudulent or unfounded reports, complaints or appeals. 9. Complaints Regarding Content Contact information for complaints about content provided by our Members. We ask that you report content and other information that you believe violates your rights (including intellectual property rights), our Professional Community Policies or otherwise violates this Contract or the law. To the extent we can under law, we may remove or restrict access to content, features, services, or information, including if we believe that it’s reasonably necessary to avoid harm to LinkedIn or others, violates the law or is reasonably necessary to prevent misuse of our Services. We reserve the right to take action against serious violations of this Contract, including by implementing account restrictions for significant violations. We respect the intellectual property rights of others. We require that information shared by Members be accurate and not in violation of the intellectual property rights or other rights of third parties. We provide a policy and process for complaints concerning content shared, and/or trademarks used, by our Members. 10. How To Contact Us Our Contact information. Our Help Center also provides information about our Services. For general inquiries, you may contact us online . For legal notices or service of process, you may write us at these addresses . LinkedIn © 2026 About Accessibility User Agreement Privacy Policy Cookie Policy Copyright Policy Brand Policy Guest Controls Community Guidelines العربية (Arabic) বাংলা (Bangla) Čeština (Czech) Dansk (Danish) Deutsch (German) Ελληνικά (Greek) English (English) Español (Spanish) فارسی (Persian) Suomi (Finnish) Français (French) हिंदी (Hindi) Magyar (Hungarian) Bahasa Indonesia (Indonesian) Italiano (Italian) עברית (Hebrew) 日本語 (Japanese) 한국어 (Korean) मराठी (Marathi) Bahasa Malaysia (Malay) Nederlands (Dutch) Norsk (Norwegian) ਪੰਜਾਬੀ (Punjabi) Polski (Polish) Português (Portuguese) Română (Romanian) Русский (Russian) Svenska (Swedish) తెలుగు (Telugu) ภาษาไทย (Thai) Tagalog (Tagalog) Türkçe (Turkish) Українська (Ukrainian) Tiếng Việt (Vietnamese) 简体中文 (Chinese (Simplified)) 正體中文 (Chinese (Traditional)) Language | 2026-01-13T08:48:28 |
https://stackoverflow.blog/2025/12/16/your-2025-stacked-a-year-of-knowledge-community-and-impact/ | Your 2025 Stacked: A year of knowledge, community, and impact - Stack Overflow Blog Loading… Everything Productivity AI/ML Open Source Business Hub Company Releases Podcast Newsletter Stack Overflow Business Stack Internal : the knowledge intelligence layer that powers enterprise AI. Stack Data Licensing : decades of verified, technical knowledge to boost AI performance and trust. Stack Ads : engage developers where it matters — in their daily workflow. December 16, 2025 Your 2025 Stacked: A year of knowledge, community, and impact From tough questions to standout answers, your team built a lot in 2025. Your 2025 Stacked brings those contributions together in one shareable snapshot—celebrating the people, posts, and topics that defined your year in Stack Internal. Celebrate your year in Stack Internal What did your team build this year? If you used Stack Internal in 2025, the answer is: a lot. You asked tough questions, shared expert answers, reviewed content, and helped your organization move faster through knowledge. Now, you can see that impact come to life in one place: Your 2025 Stacked—a year-in-review experience available to eligible Stack Internal communities starting today. This shareable summary highlights your people, your contributions, and the knowledge-sharing wins that shaped your year. Top contributors The names behind your strongest contributors—across categories like: Most helpful : Assisted the most team members Most knowledgeable : Contributed the most answers and articles Most supportive : Most upvotes, reactions, bookmarks, and follows given Most connected : Contributed answers across the most tags Most dependable : Most days visited during the year Most curious: Asked the most questions Most attentive : Reviewed the most posts in Content Health Popular contributions Your 2025 Stacked doesn’t just show who contributed—it highlights what resonated most across your community, including: Post of the year : The question or article that received the most votes and follows Most popular posts : High-impact questions and articles based on a mix of views, votes, bookmarks, and follows Most popular tags : The topics your team turned to again and again Most popular user groups: Groups that drove engagement through participation and mentions Most popular communities : Your most active and impactful Communities, as measured by contributions and interaction These callouts help surface the content that brought your team together—and the topics that moved your organization forward. You brought the activity. We brought the receipts. Your 2025 Stacked is live for sites that meet the minimum eligibility requirements for community age and activity. It’s packed with the highlights, habits, and heroics that made this year one to remember. No setup. Just real impact. What we shipped in 2025: Stack Internal highlights 2025 was a standout year for Stack Internal. It powered knowledge sharing across 1,000+ instances, used by 100K+ users every month at more than 100 Business and Enterprise organizations. Each month, those users generated more than one million meaningful interactions—asking, answering, upvoting, and curating knowledge that moves work forward. To support that momentum, we shipped dozens of platform enhancements designed to make sharing easier, insights more discoverable, and collaboration more scalable. Here are just a few of the features that helped communities grow smarter in 2025: Slack + Microsoft Teams digests: Channel and personal digests brought weekly insights—top contributors, unanswered questions, and key metrics—directly into team workflows. Executive report: A reimagined dashboard for leadership, with trend snapshots, SME highlights, and engagement breakdowns. Backstage.io integration: SO-enhanced search, in-context question submission, and a dedicated Stack Internal hub—all embedded in your developer portal. Voting enhancements: "Vote" prompts on unanswered questions and tooltip nudges helped boost engagement across the board. Threaded comments: A cleaner, more connected conversation experience—built on top of a redesigned interface with @ mentions and reply tracking. LangChain loader + Stack Internal SDK: Support for AI-native integrations and custom apps through our v3 API, SDK, and plug-and-play document loader. MCP server: Bi-directional, secure connections between generative AI tools (like GitHub Copilot, ChatGPT, and more) and your trusted internal knowledge—enabling grounded responses and continuous knowledge improvement. Last, but certainly not least, we ushered in a new, AI-first era, rebranding Stack Overflow for Teams as Stack Internal with both a new name and refreshed look that better represents our mission to fuel AI, accelerate delivery, and preserve your org’s trusted knowledge. What’s coming in 2026: A smarter, more connected Stack Internal If 2025 was about strengthening the foundation of Stack Internal, 2026 is about transforming how knowledge flows across your organization. At the center of that evolution is one of our most ambitious initiatives yet: Knowledge Ingestion. Knowledge Ingestion will give teams a powerful new way to bring high-value content from the systems they already use—Confluence, Slack, Microsoft Teams, and more—directly into Stack Internal. The goal is simple: eliminate silos, centralize trusted information, and help every team get to the “Stack solved my problem” moment faster. This work is already underway through a multi-month pilot with a select group of highly engaged customers, who are partnering with us to test early workflows and shape the final experience. If you want a deeper look at what Knowledge Ingestion unlocks, be sure to check out our on-demand webinar . 2026 will bring even more ways to make your knowledge discoverable, durable, and ready for the AI-powered workflows your teams rely on. And we’re just getting started. Here’s to more curiosity, collaboration, and contribution in 2026. 🚀 Author s Carrie Koos Staff Releases Stack Overflow Internal Where developers & technologists share private knowledge with coworkers. Learn more Latest releases January 5, 2026 What’s new at Stack Overflow: January 2026 December 16, 2025 Your 2025 Stacked: A year of knowledge, community, and impact December 1, 2025 What’s new at Stack Overflow: December 2025 November 12, 2025 2025.8 release introduces Stack Overflow Internal: The next generation of enterprise knowledge intelligence Add to the discussion Login with your stackoverflow.com account to take part in the discussion. Our Stack Stack Internal Features Customers Security Pricing Stack Data Licensing Stack Ads Partnerships Services Stack Overflow Company Leadership Press Careers Social Impact Support Contact Stack Overflow help Stack Internal help Terms Privacy policy Cookie policy Your Privacy Choices Elsewhere Blog Dev Newsletter Podcast Releases Dev Survey Site design / logo © 2026 Stack Exchange Inc. Light Dark Auto | 2026-01-13T08:48:28 |
https://stackoverflow.blog/ml/ | ML - Stack Overflow Blog Loading… Everything Productivity AI/ML Open Source Business Hub Company Releases Podcast Newsletter Stack Overflow Business Stack Internal : the knowledge intelligence layer that powers enterprise AI. Stack Data Licensing : decades of verified, technical knowledge to boost AI performance and trust. Stack Ads : engage developers where it matters — in their daily workflow. ML Subscribe to the podcast Get The Stack Overflow Podcast at your favorite listening service. Apple Podcasts Overcast Overcast Pocket Casts Spotify RSS feed December 31, 2025 A look under the hood: How (and why) we built Question Assistant Evaluating question quality and determining the appropriate feedback required some classic ML techniques in addition to our GenAI solution. Derek Cheng , Caroline Thomas , Ryan Donovan 3 comment s questions staging ground Question Assistant AI ML Engineering March 18, 2025 Improving error monitoring with AI Tillman Elser, AI/ML lead at Sentry, joins Ryan for a conversation about improving error monitoring with AI and ML. They talk through the challenges of analyzing stack traces, the innovative use of embeddings to improve error grouping, the trial-and-error process of developing algorithms, and where Sentry’s AI capabilities are headed next. Eira May 0 comment s The Stack Overflow Podcast generative AI AI ML error tracking monitoring software development programming language June 6, 2023 MosaicML: Deep learning models for sale, all shapes and sizes (Ep. 577) Ben and Ryan talk with Jonathan Frankle and Abhinav Venigalla of MosaicML, a startup trying to make deep learning and generative AI efficient and accessible for everyone. Eira May 0 comment s AI machine learning ML the stack overflow podcast The Stack Overflow Podcast February 24, 2023 ML and AI consulting-as-a-service (Ep. 542) The home team talks with Jaclyn Rice Nelson, cofounder and CEO of Tribe AI, about the explosion of hype surrounding generative AI, what it’s like to work at a startup after working at Google, and how Tribe is leveraging the power of a specialist network. Eira May 0 comment s AI data science Engineering machine learning ML the stack overflow podcast The Stack Overflow Podcast tribe ai September 9, 2022 Plug-and-play AI for your own projects (Ep. 482) Ben talks with Dylan Fox, founder and CEO of rapid-growth startup AssemblyAI, about how he became interested in AI and machine learning, why he left a steady job at a tech giant to create something new, and what AI can offer creators like writers and visual artists. Eira May 1 comment AI ai-as-a-service ML The Stack Overflow Podcast the stack overflow podcast August 23, 2022 Why AI is having an on-prem moment (Ep. 476) The home team discusses how Instagram’s evolving platform has alienated some creators, why AI and machine learning are moving on-premises, and why Amazon’s acquisition of the company behind the Roomba is striking from a privacy perspective. Eira May 3 comment s AI instagram ML the stack overflow podcast The Stack Overflow Podcast Show more Our Stack Stack Internal Features Customers Security Pricing Stack Data Licensing Stack Ads Partnerships Services Stack Overflow Company Leadership Press Careers Social Impact Support Contact Stack Overflow help Stack Internal help Terms Privacy policy Cookie policy Your Privacy Choices Elsewhere Blog Dev Newsletter Podcast Releases Dev Survey Site design / logo © 2026 Stack Exchange Inc. Light Dark Auto | 2026-01-13T08:48:28 |
https://dev.to/himanshu_bhatt/networking-101-1-networking-introduction-4ip0 | Networking 101 #1. Networking Introduction - DEV Community Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account DEV Community Close Add reaction Like Unicorn Exploding Head Raised Hands Fire Jump to Comments Save Boost More... Copy link Copy link Copied to Clipboard Share to X Share to LinkedIn Share to Facebook Share to Mastodon Share Post via... Report Abuse Himanshu Bhatt Posted on Jan 13 Networking 101 #1. Networking Introduction # devops # networking # cloud # beginners 👋 Short Intro (Why I’m Writing This) I’m currently learning Networking for DevOps and decided to learn in public by documenting my journey. This blog is part of my Networking 101 series, where I’m learning DevOps step by step from scratch. This series is not written by an expert — it’s a beginner learning out loud, sharing: what I understand, what confuses me, and what I learn along the way. The goal is to build consistency, clarity, and invite discussion. 📌 What This Blog Covers In this post, I’ll cover: 📂 GitHub Repository All my notes, diagrams, and learning resources for this series live here: 👉 GitHub Repo: https://github.com/dmz-v-x/networking-for-devops-101 This repo is updated as I continue learning. 📚 Learning Notes Why should DevOps engineers even care about networking? Let’s start from basics. Most DevOps failures are not code bugs . They look like this: ❌ “The app works locally but not in production” ❌ “The service is running but not reachable” ❌ “502 Bad Gateway” ❌ “Connection refused” ❌ “Request timed out” All of these comes down to one problem that is networking problems . If you don’t understand networking: You won’t know where the problem is You’ll randomly try fixes You’ll depend on someone else to debug This blog series exists to change that — from zero . Goal of this series By the end of this series, you should be able to: Understand how traffic flows from browser → cloud → server Debug basic production networking issues Understand Docker & Kubernetes networking at a high level Read cloud architecture diagrams without fear And i hope you and i we both be able to answer networking related questions in your interview The ONE mental model we must remember Everything in networking can be explained using three boxes : Client (Browser / App) ↓ Network (DNS, Internet, Load Balancer) ↓ Server (VM / Container / App) Enter fullscreen mode Exit fullscreen mode Rule: When something breaks, the problem is always in one of these boxes or the connection between them. We’ll keep coming back to this model in every blog. Before we go further: 3 tiny building blocks You must understand these three things first. Don’t worry — we’ll go slow. 1. DNS — turning names into addresses When you type any url into our browser: For Example: https://example.com Enter fullscreen mode Exit fullscreen mode Your computer does not understand example.com . Computers only understand numbers (IP addresses). 👉 DNS exists to solve this problem. DNS = Name → IP address Means resolving Name(address/url) to IP Address. Example: example.com → 93.184.216.34 Enter fullscreen mode Exit fullscreen mode 📌 Think of DNS like a phone book : You search by name You get a number If DNS breaks, nothing works — even if your server is perfectly fine. 2. IP addresses & Ports — where and what to connect to 2.1 IP Address An IP address identifies a machine on a network . Examples: 192.168.1.10 (private IP) 13.234.56.78 (public IP) Public IP → reachable from the internet Private IP → only reachable inside a private network (like cloud VPCs - Virtual Private Cloud) 2.2 Port A port identifies which application on that machine you want to talk to. Okay, so when we connect to an application, we are actually connecting to an IP address where that application is running. However, this does not mean that only one application can run on a single IP address. But in reality, mulitple application can run on the same IP address , and they are distinguished from each other using different port numbers. Example: Let say we have a server that has an IP: 192.168.1.10 Now on this same IP, we might have: Web app running on port 80 Backend API running on port 3000 Database running on port 5432 So: 192.168.1.10:80 → Web application 192.168.1.10:3000 → Backend service 192.168.1.10:5432 → Database Examples: 22 → SSH 80 → HTTP 443 → HTTPS 5432 → PostgreSQL 📌 IP = which computer 📌 Port = which app on that computer 3. TCP vs UDP — how data is sent This is about rules of communication . 3.1 TCP (most important for DevOps) Reliable Ordered Connection-based Used by: HTTP / HTTPS SSH Databases Think of TCP like a phone call : You connect You talk You hang up 3.2 UDP (less common, but important) Fast No guarantee of delivery No connection Used by: DNS (often) Streaming Some internal systems Think of UDP like shouting messages — fast, but no confirmation. 🛠️ Tiny hands-on demo (run these now) These commands make networking real . 🔍 Check DNS resolution dig google.com +short Enter fullscreen mode Exit fullscreen mode Computers cannot understand domain names. Computers only understand IP addresses like: 93.184.216.34 . So in the above command we are asking a tool called dig (Domain Information Groper) to provide us the IP address of domain: google.com . So finding IP address of a domain name is called as DNS resolution. We run: dig google.com +short We ask the dig tool: Hey DNS, what is the IP address of google.com? The DNS system looks it up and replies with something like: 74.125.68.101 The +short flag means: Don't show technical details, just give me the final answer i.e IP Address. or nslookup example.com Enter fullscreen mode Exit fullscreen mode nslookup means (Name Server Lookup) nslookup does the same job as dig, but with different output style. By different style what i meant is it does provides the IP address of the domain name, but it also provides the DNS server that answered the query. We run: nslookup google.com Our computer contacts a DNS server The DNS server responds with the IP address & The DNS server that answered the query Example output: Server: 8.8.8.8 Address: 8.8.8.8#53 Non-authoritative answer: Name: example.com Address: 93.184.216.34 Enter fullscreen mode Exit fullscreen mode If DNS fails → nothing else matters. 📡 Check basic connectivity ping google.com OR ping 93.184.216.34 Enter fullscreen mode Exit fullscreen mode Before anything else, we always ask what is the IP address of google.com, like we did it using above two tools (dig & nslookup). So internally this happens: example.com → DNS → 93.184.216.34 So if DNS fails everything fails. Once IP is known, we do ping to that IP address, ping sends a special network message called ICMP Echo request . It like asking to that server, hey server, are you alive? Now there could two things happens, either the server responds or it doesn't. If server is reachable and allows ping. It replies with ICMP Echo Reply . Our terminal prints something like: 64 bytes from 93.184.216.34: time=12ms This means: the server is reachable, the network path work & the round trip time is 12 milliseconds. By default ping keeps sending packets every second: ping → reply ping → reply ping → reply Until you stop it with: Ctrl + C If ping fails: Network issue Firewall issue Host down What ping google.com actually verifies: The IP is reachable over the network Basic connectivity exists What Pings does not verify Application is running Website is working Port is open Server is healthy A server can reply to ping still have a down website. Sometimes ping may fail but website might be working fine. That's because many servers block (ICMP) ping for security reasons. So this can happen: ping google.com - may fail curl https://google.com - may work This does not mean site is down. A Basic Debugging Order: DNS: dig example.com Network reachability: ping example.com Application check: curl example.com Does ping do DNS resolution? Yes ping does the DNS resolution. But it only does the DNS resolution when we provide it a domain to find the IP of that particular domain it does the DNS resolution, If we provide it IP it won't do the DNS resolution. Example: Let's say we have a domain example.com, and we want to ping it. ping example.com Internally: ping sees the domain. It asks the DNS to resolve this domain The DNS server responds back with the IP: ping IP vs ping domain CASE A: ping google.com In this case we type the domain name which we want to ping ping google.com The computer doesn't understand names, it needs an IP, so DNS lookup happens means finding the IP address for the domain name. (Yes ping does the DNS if we provide it domain (bare minimum DNS just to find IP Address)) google.com → 93.184.216.34 Now ping sends packets to the IP address. DNS is involved only once at the beginning CASE B: ping 93.184.216.34 In this case we type the IP Address which we want to ping ping 93.184.216.34 The computer doesn't need to do DNS resolution as it already have the IP address. So DNS is skipped completely Ping sends packets directly to the IP. Difference in one sentence | Command | DNS involved? | What is pinged | | ------------- | ------------- | --------------------- | | ping domain | ✅ Yes | Application server IP | | ping IP | ❌ No | Application server IP | Why Cloud servers block ping Ping uses ICMP protocol, when we do ping we ask server (ICMP echo request) are you alive? This is a low-level network check, not an application request. Security Reasons: If ping were to allowed Attackers could easily find live servers Map infrastructure Launch attacks (DDoS Scanning) So cloud providers decide not to respond to ping at all. Ping ≠ Real Usage: User don't use ICMP, Ping. Users use HTTPS, HTTP, APIs, TCP Connection. So blocking ping does not affect real users. Common real-world situation: ping myserver.com → fails curl https://myserver.com → works This means: Server is running, application is working, ICMP is blocked intentionally. ICMP vs TCP ICMP ICMP = Internet Control Message Protocol Used only to check reachability, report network errors what it does: Can i reach this machine/server at all? TCP TCP = Transmission Control Protocol Used to open reliable connections, talk to applications on ports TCP → Port 80 / 443 → Web server HTTP/HTTPS Application-level protocols Build on top of TCP They answers questions like: Give me this web page, process this api request. Comparison: Thing ICMP (Ping) TCP / HTTP Purpose Reachability Real communication Uses ports? ❌ No ✅ Yes Talks to app? ❌ No ✅ Yes Blocked often? ✅ Yes ❌ Rarely Used by users? ❌ No ✅ Yes 🔌 Check if a port is open nc -vz example.com 443 Enter fullscreen mode Exit fullscreen mode If you see: ❌ connection refused → service or firewall issue ❌ timeout → routing or security group issue 🌍 Test HTTP directly curl -I https://example.com Enter fullscreen mode Exit fullscreen mode If this works → TCP + HTTP + DNS are all working. 🔧 Real DevOps debugging example Problem: Your app is deployed but users can’t access it. Debug like this (always in order): ❓ Does DNS resolve? ❓ Is the IP reachable? ❓ Is the port open? ❓ Is the application responding? 📌 Never jump steps. 📌 Networking debugging is layered , not random. 🚫 What we intentionally skipped (for now) We will explain these later — slowly and clearly: Subnets & CIDR NAT Firewalls & security groups Load balancers Docker networking Kubernetes services Each deserves its own beginner-friendly post. ✅ Key takeaways DevOps problems are often network problems Use the Client → Network → Server mental model Learn DNS, IPs, ports, and TCP first — everything builds on them Debug step by step, not by guessing ⏭️ Coming next Part 2: How the Internet Actually Works (Step by Step) We’ll trace what happens when you type a URL into your browser: DNS resolution Packets Servers Responses No jargon. No assumptions. If this helped you, consider bookmarking or sharing — the next parts build directly on this foundation. Top comments (0) Subscribe Personal Trusted User Create template Templates let you quickly answer FAQs or store snippets for re-use. Submit Preview Dismiss Code of Conduct • Report abuse Are you sure you want to hide this comment? It will become hidden in your post, but will still be visible via the comment's permalink . Hide child comments as well Confirm For further actions, you may consider blocking this person and/or reporting abuse Himanshu Bhatt Follow Aspiring DevOps professional passionate about cloud technologies. Sharing my learning journey to help others and grow. Looking to connect and explore new career opportunities! Location Nainital, Uttarakhand Education Bipin Tripathi Kuamon Institute of Technology Pronouns He/Him Work Seeking opportunities in DevOps & Cloud Engineering. Building skills through projects & blogging. Joined Jan 24, 2025 More from Himanshu Bhatt Introduction to DevOps #5. DevOps Tooling Landscape # devops # cloud # beginners # discuss [Boost] # devops # cloud # beginners # discuss Introduction to DevOps #4. What Problems DevOps Solves # devops # cloud # beginners # discuss 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV DEV Community — A space to discuss and keep up software development and manage your software career Home DEV++ Podcasts Videos DEV Education Tracks DEV Challenges DEV Help Advertise on DEV DEV Showcase About Contact Free Postgres Database Software comparisons Forem Shop Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . DEV Community © 2016 - 2026. We're a place where coders share, stay up-to-date and grow their careers. Log in Create account | 2026-01-13T08:48:28 |
https://stackoverflow.blog/2024/02/08/discussions-now-taking-place-across-all-tags-on-stack-overflow/ | Discussions now taking place across all tags on Stack Overflow - Stack Overflow Blog Loading… Everything Productivity AI/ML Open Source Business Hub Company Releases Podcast Newsletter Stack Overflow Business Stack Internal : the knowledge intelligence layer that powers enterprise AI. Stack Data Licensing : decades of verified, technical knowledge to boost AI performance and trust. Stack Ads : engage developers where it matters — in their daily workflow. February 8, 2024 Discussions now taking place across all tags on Stack Overflow Expanding the experiment to create the space for developers to have meaningful conversations about their favorite technologies. In August 2023, Prashanth Chandrasekar, CEO of Stack Overflow, announced Discussions at the WeAreDevelopers event. Discussions is a dedicated space for the developer community to dive into meaningful dialogue and exchange perspectives on specific technical subjects. Discussions lets developers of all skill levels have opinion-based conversations and share their own insights. Discussions is different than the conversation traditionally suited for the Stack Overflow Q&A platform and creates a new venue and opportunity for subjective conversations. Discussions has now expanded beyond Collectives™ on Stack Overflow to all technical topics on Stack Overflow. Why do this? We know that when developers learn something new or formalize a direction for a project, they often turn to other developers and the technical community to seek their advice and guidance. This expanded experiment creates space for a new type of conversation on Stack Overflow so developers can learn or share a new perspective outside of the traditional question-and-answer space. Discussions provides a way for developers to tap into the collective knowledge of the Stack Overflow community. Here, developers can explore technical approaches, share different perspectives, and make more informed technical decisions. How to get started? To get started with Discussions, simply select the Discussions tab under Labs on the left sidebar: From here, you’ll be able to access existing Discussions, create new ones, and filter through Stack Overflow tags. Let us know what you think! Discussions is an experiment that we’re expanding, and we want to hear from you and the community to help us guide the future of these conversations. Let us know your thoughts and provide your feedback about Discussions on Meta . Author s Janice Manningham Senior Product Manager Staff Releases new features discussion Community experiment Latest releases January 5, 2026 What’s new at Stack Overflow: January 2026 December 16, 2025 Your 2025 Stacked: A year of knowledge, community, and impact December 1, 2025 What’s new at Stack Overflow: December 2025 November 12, 2025 2025.8 release introduces Stack Overflow Internal: The next generation of enterprise knowledge intelligence Add to the discussion Login with your stackoverflow.com account to take part in the discussion. Our Stack Stack Internal Features Customers Security Pricing Stack Data Licensing Stack Ads Partnerships Services Stack Overflow Company Leadership Press Careers Social Impact Support Contact Stack Overflow help Stack Internal help Terms Privacy policy Cookie policy Your Privacy Choices Elsewhere Blog Dev Newsletter Podcast Releases Dev Survey Site design / logo © 2026 Stack Exchange Inc. Light Dark Auto | 2026-01-13T08:48:28 |
https://dev.to/ajtiti/ajtiti-49-wakacje-programisty#main-content | AjTiTi #49 - Wakacje programisty - DEV Community Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account DEV Community Close AjTiTi [PL] Follow AjTiTi #49 - Wakacje programisty Sep 2 '22 play Rok szkolny się rozpoczął, więc podejmujemy sentymentalną podróż w stronę wakacji. W jaki sposób programista powinien przygotować się do wakacji? Co zrobić przed? Co robić w trakcie? Jak przeżyć powrót do pracy? Czy w ogóle warto robić sobie wakacyjne przerwy? (SPOILER: zdecydowanie warto!). Piosenka Janet Jackson niszczy komputery: https://devblogs.microsoft.com/oldnewthing/20220816-00/?p=106994 Episode source Personal Trusted User Create template Templates let you quickly answer FAQs or store snippets for re-use. Submit Preview Dismiss Your browser does not support the audio element. 1x initializing... × 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV DEV Community — A space to discuss and keep up software development and manage your software career Home DEV++ Podcasts Videos DEV Education Tracks DEV Challenges DEV Help Advertise on DEV DEV Showcase About Contact Free Postgres Database Software comparisons Forem Shop Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . DEV Community © 2016 - 2026. We're a place where coders share, stay up-to-date and grow their careers. Log in Create account | 2026-01-13T08:48:28 |
https://www.linkedin.com/legal/user-agreement?trk=content_footer-user-agreement | User Agreement | LinkedIn Skip to main content User Agreement Summary of User Agreement Privacy Policy Professional Community Policies Cookie Policy Copyright Policy Regional Info EU Notice California Privacy Disclosure U.S. State Privacy Laws User Agreement Summary of User Agreement Privacy Policy Professional Community Policies Cookie Policy Copyright Policy Regional Info EU Notice California Privacy Disclosure U.S. State Privacy Laws User Agreement Effective on November 3, 2025 Our mission is to connect the world’s professionals to allow them to be more productive and successful. Our services are designed to promote economic opportunity for our members by enabling you and millions of other professionals to meet, exchange ideas, learn, and find opportunities or employees, work, and make decisions in a network of trusted relationships. Table of Contents: Introduction Obligations Rights and Limits Disclaimer and Limit of Liability Termination Governing Law and Dispute Resolution General Terms LinkedIn “Dos and Don’ts” Complaints Regarding Content How To Contact Us Introduction 1.1 Contract When you use our Services you agree to all of these terms. Your use of our Services is also subject to our Cookie Policy and our Privacy Policy, which covers how we collect, use, share, and store your personal information. By creating a LinkedIn account or accessing or using our Services (described below), you are agreeing to enter into a legally binding contract with LinkedIn (even if you are using third party credentials or using our Services on behalf of a company). If you do not agree to this contract (“Contract” or “User Agreement”), do not create an account or access or otherwise use any of our Services. If you wish to terminate this Contract at any time, you can do so by closing your account and no longer accessing or using our Services. As a Visitor or Member of our Services, the collection, use, and sharing of your personal data is subject to our Privacy Policy , our Cookie Policy and other documents referenced in our Privacy Policy , and updates. You acknowledge and have read our Privacy Policy . Services This Contract applies to LinkedIn.com, LinkedIn-branded apps, and other LinkedIn-related sites, apps, communications, and other services that state that they are offered under this Contract (“Services”), including the offsite collection of data for those Services, such as via our ads and the “Apply with LinkedIn” and “Share with LinkedIn” plugins. LinkedIn and other Key Terms You are entering into this Contract with LinkedIn (also referred to as “we” and “us”). Designated Countries . We use the term “Designated Countries” to refer to countries in the European Union (EU), European Economic Area (EEA), and Switzerland. If you reside in the “Designated Countries”, you are entering into this Contract with LinkedIn Ireland Unlimited Company (“LinkedIn Ireland”) and LinkedIn Ireland will be the controller of your personal data provided to, or collected by or for, or processed in connection with our Services. If you reside outside of the “Designated Countries”, you are entering into this Contract with LinkedIn Corporation (“LinkedIn Corp.”) and LinkedIn Corp. will be the controller of (or business responsible for) your personal data provided to, or collected by or for, or processed in connection with our Services. Affiliates . Affiliates are companies controlling, controlled by or under common control with us, including, for example, LinkedIn Ireland, LinkedIn Corporation, LinkedIn Singapore and Microsoft Corporation or any of its subsidiaries (e.g., Github, Inc.). Social Action . Actions that members take on our services such as likes, comments, follows, sharing content. Content . Content includes, for example, feed posts, feedback, comments, profiles, articles (and contributions), group posts, job postings, messages (including InMails), videos, photos, audio, and/or PDFs. 1.2 Members and Visitors This Contract applies to Members and Visitors. When you register and join the LinkedIn Services, you become a “Member”. If you have chosen not to register for our Services, you may access certain features as a “Visitor.” 1.3 Changes We may make changes to this Contract. We may modify this Contract, our Privacy Policy and our Cookie Policy from time to time. If we materially change these terms or if we are legally required to provide notice, we will provide you notice through our Services, or by other means, to provide you the opportunity to review the changes before they become effective. However, we may not always provide prior notice of changes to these terms (1) when those changes are legally required to be implemented with immediate effect, or (2) when those changes relate to a newly launched service or feature. We agree that changes cannot be retroactive. If you object to any of these changes, you may close your account . Your continued use of our Services after we publish or send a notice about our changes to these terms means that you are consenting to the updated terms as of their effective date. 2. Obligations 2.1 Service Eligibility Here are some promises that you make to us in this Contract: You’re eligible to enter into this Contract and you are at least our “Minimum Age.” The Services are not for use by anyone under the age of 16. To use the Services, you agree that: (1) you must be the "Minimum Age" (described below) or older; (2) you will only have one LinkedIn account, which must be in your real name; and (3) you are not already restricted by LinkedIn from using the Services. Creating an account with false information is a violation of our terms, including accounts registered on behalf of others or persons under the age of 16. “Minimum Age” means 16 years old. However, if law requires that you must be older in order for LinkedIn to lawfully provide the Services to you without parental consent (including using your personal data) then the Minimum Age is such older age. Learn More 2.2 Your Account You will keep your password a secret You will not share your account with anyone else and will follow our policies and the law. Members are account holders. You agree to: (1) protect against wrongful access to your account (e.g., use a strong password and keep it confidential); (2) not share or transfer your account or any part of it (e.g., sell or transfer the personal data of others by transferring your connections); and (3) follow the law, our list of Dos and Don’ts (below), and our Professional Community Policies . Learn More You are responsible for anything that happens through your account unless you close it or report misuse. As between you and others (including your employer), your account belongs to you. However, if the Services were purchased by another party for you to use in connection with your work for them (e.g., Recruiter seat or LinkedIn Learning subscription bought by your employer), the party paying for such Service has the right to control access to and get reports on your use of such paid Service; however, they do not have rights to your personal account. 2.3 Payment You’ll honor your payment obligations and you are okay with us storing your payment information. You understand that there may be fees and taxes that are added to our prices. Refunds are subject to our policy, and we may modify our prices and those modified prices will apply prospectively. If you buy any of our paid Services, you agree to pay us the applicable fees and taxes and you agree to the additional terms specific to the paid Services. Failure to pay these fees will result in the termination of your paid Services. Also, you agree that: Your purchase may be subject to foreign exchange fees or differences in prices based on location (e.g., exchange rates). We may store and continue billing your payment method (e.g., credit card), even after it has expired, to avoid interruptions in your paid Services and to use it to pay for other Services you may buy. If your primary payment method fails, we may automatically charge a secondary payment method, if you have provided one. You may update or change your payment method. Learn more If you purchase a subscription, your payment method automatically will be charged at the start of each subscription period for the fees and taxes applicable to that period. To avoid future charges, cancel before the renewal date. Learn how to cancel or suspend your paid subscription Services. We may modify our prices effective prospectively upon reasonable notice to the extent allowed under the law. All of your paid Services are subject to LinkedIn’s refund policy . We may calculate taxes payable by you based on the billing information that you provide us. You can get a copy of your invoice through your LinkedIn account settings under “ Purchase History ”. 2.4 Notices and Messages You’re okay with us providing notices and messages to you through our websites, apps, and contact information. If your contact information is out of date, you may miss out on important notices. You agree that we will provide notices and messages to you in the following ways: (1) within the Services or (2) sent to the contact information you provided us (e.g., email, mobile number, physical address). You agree to keep your contact information up to date. Please review your settings to control and limit the types of messages you receive from us. 2.5 Sharing When you share information on our Services, others can see, copy and use that information. Our Services allow sharing of information (including content) in many ways, such as through your profile, posts, articles, group posts, links to news articles, job postings, messages, and InMails. Depending on the feature and choices you make, information that you share may be seen by other Members, Visitors, or others (on or off of the Services). Where we have made settings available, we will honor the choices you make about who can see content or other information (e.g., message content to your addressees, sharing content only to LinkedIn connections, restricting your profile visibility from search tools, or opting not to notify others of your LinkedIn profile update). For job searching activities, we default to not notifying your connections or the public. So, if you apply for a job through our Services or opt to signal that you are interested in a job, our default is to share it only with the job poster. To the extent that laws allow this, we are not obligated to publish any content or other information on our Services and can remove it with or without notice. 3. Rights and Limits 3.1. Your License to LinkedIn You own all of your original content that you provide to us, but you also grant us a non-exclusive license to it. We’ll honor the choices you make about who gets to see your content, including how it can be used for ads. As between you and LinkedIn, you own your original content that you submit or post to the Services. You grant LinkedIn and our Affiliates the following non-exclusive license to the content and other information you provide (e.g., share, post, upload, and/or otherwise submit) to our Services: A worldwide, transferable and sublicensable right to use, copy, modify, distribute, publicly perform and display, host, and process your content and other information without any further consent, notice and/or compensation to you or others. These rights are limited in the following ways: You can end this license for specific content by deleting such content from the Services, or generally by closing your account, except (a) to the extent you (1) shared it with others as part of the Services and they copied, re-shared it or stored it, (2) we had already sublicensed others prior to your content removal or closing of your account, or (3) we are required by law to retain or share it with others, and (b) for the reasonable time it takes to remove the content you delete from backup and other systems. We will not include your content in advertisements for the products and services of third parties to others without your separate consent (including sponsored content). However, without compensation to you or others, ads may be served near your content and other information, and your social actions may be visible and included with ads, as noted in the Privacy Policy. If you use a Service feature, we may mention that with your name or photo to promote that feature within our Services, subject to your settings. We will honor the audience choices for shared content (e.g., “Connections only”). For example, if you choose to share your post to "Anyone on or off LinkedIn” (or similar): (a) we may make it available off LinkedIn; (b) we may enable others to publicly share onto third-party services (e.g., a Member embedding your post on a third party service); and/or (c) we may enable search tools to make that public content findable though their services. Learn More While we may edit and make format changes to your content (such as translating or transcribing it, modifying the size, layout or file type, and removing or adding labels or metadata), we will take steps to avoid materially modifying the meaning of your expression in content you share with others. Because you own your original content and we only have non-exclusive rights to it, you may choose to make it available to others, including under the terms of a Creative Commons license . You and LinkedIn agree that if content includes personal data, it is subject to our Privacy Policy. You and LinkedIn agree that we may access, store, process, and use any information (including content and/or personal data) that you provide in accordance with the terms of the Privacy Policy and your choices (including settings). By submitting suggestions or other feedback regarding our Services to LinkedIn, you agree that LinkedIn can use and share (but does not have to) such feedback for any purpose without compensation to you. You promise to only provide content and other information that you have the right to share and that your LinkedIn profile will be truthful. You agree to only provide content and other information that does not violate the law or anyone’s rights (including intellectual property rights). You have choices about how much information to provide on your profile but also agree that the profile information you provide will be truthful. LinkedIn may be required by law to remove certain content and other information in certain countries. 3.2 Service Availability We may change or limit the availability of some features, or end any Service. We may change, suspend or discontinue any of our Services. We may also limit the availability of features, content and other information so that they are not available to all Visitors or Members (e.g., by country or by subscription access). We don’t promise to store or show (or keep showing) any information (including content) that you’ve shared. LinkedIn is not a storage service. You agree that we have no obligation to store, maintain or provide you a copy of any content or other information that you or others provide, except to the extent required by applicable law and as noted in our Privacy Policy. 3.3 Other Content, Sites and Apps Your use of others’ content and information posted on our Services, is at your own risk. Others may offer their own products and services through our Services, and we aren’t responsible for those third-party activities. Others’ Content: By using the Services, you may encounter content or other information that might be inaccurate, incomplete, delayed, misleading, illegal, offensive, or otherwise harmful. You agree that we are not responsible for content or other information made available through or within the Services by others, including Members. While we apply automated tools to review much of the content and other information presented in the Services, we cannot always prevent misuse of our Services, and you agree that we are not responsible for any such misuse. You also acknowledge the risk that others may share inaccurate or misleading information about you or your organization, and that you or your organization may be mistakenly associated with content about others, for example, when we let connections and followers know you or your organization were mentioned in the news. Members have choices about this feature . Others’ Products and Services: LinkedIn may help connect you to other Members (e.g., Members using Services Marketplace or our enterprise recruiting, jobs, sales, or marketing products) who offer you opportunities (on behalf of themselves, their organizations, or others) such as offers to become a candidate for employment or other work or offers to purchase products or services. You acknowledge that LinkedIn does not perform these offered services, employ those who perform these services, or provide these offered products. You further acknowledge that LinkedIn does not supervise, direct, control, or monitor Members in the making of these offers, or in their providing you with work, delivering products or performing services, and you agree that (1) LinkedIn is not responsible for these offers, or performance or procurement of them, (2) LinkedIn does not endorse any particular Member’s offers, and (3) LinkedIn is not an agent or employment agency on behalf of any Member offering employment or other work, products or services. With respect to employment or other work, LinkedIn does not make employment or hiring decisions on behalf of Members offering opportunities and does not have such authority from Members or organizations using our products. For Services Marketplace , (a) you must be at least 18 years of age to procure, offer, or perform services, and (b) you represent and warrant that you have all the required licenses and will provide services consistent with the relevant industry standards and our Professional Community Policies . Others’ Events: Similarly, LinkedIn may help you register for and/or attend events organized by Members and connect with other Members who are attendees at such events. You agree that (1) LinkedIn is not responsible for the conduct of any of the Members or other attendees at such events, (2) LinkedIn does not endorse any particular event listed on our Services, (3) LinkedIn does not review and/or vet any of these events or speakers, and (4) you will adhere to the terms and conditions that apply to such events. 3.4 Limits We have the right to limit how you connect and interact on our Services. LinkedIn reserves the right to limit your use of the Services, including the number of your connections and your ability to contact other Members. LinkedIn reserves the right to restrict, suspend, or terminate your account if you breach this Contract or the law or are misusing the Services (e.g., violating any of the Dos and Don’ts or Professional Community Policies ). We can also remove any content or other information you shared if we believe it violates our Professional Community Policies or Dos and Don’ts or otherwise violates this Contract. Learn more about how we moderate content. 3.5 Intellectual Property Rights We’re providing you notice about our intellectual property rights. LinkedIn reserves all of its intellectual property rights in the Services. Trademarks and logos used in connection with the Services are the trademarks of their respective owners. LinkedIn, and “in” logos and other LinkedIn trademarks, service marks, graphics and logos used for our Services are trademarks or registered trademarks of LinkedIn. 3.6 Recommendations and Automated Processing We use data and other information about you to make and order relevant suggestions and to generate content for you and others. Recommendations: We use the data and other information that you provide and that we have about Members and content on the Services to make recommendations for connections, content, ads, and features that may be useful to you. We use that data and other information to recommend and to present information to you in an order that may be more relevant for you. For example, that data and information may be used to recommend jobs to you and you to recruiters and to organize content in your feed in order to optimize your experience and use of the Services. Keeping your profile accurate and up to date helps us to make these recommendations more accurate and relevant. Learn More Generative AI Features: By using the Services, you may interact with features we offer that automate content generation for you. The content that is generated might be inaccurate, incomplete, delayed, misleading or not suitable for your purposes. Please review and edit such content before sharing with others. Like all content you share on our Services, you are responsible for ensuring it complies with our Professional Community Policies , including not sharing misleading information. The Services may include content automatically generated and shared using tools offered by LinkedIn or others off LinkedIn. Like all content and other information on our Services, regardless of whether it's labeled as created by “AI”, be sure to carefully review before relying on it. 4. Disclaimer and Limit of Liability 4.1 No Warranty This is our disclaimer of legal liability for the quality, safety, or reliability of our Services. LINKEDIN AND ITS AFFILIATES MAKE NO REPRESENTATION OR WARRANTY ABOUT THE SERVICES, INCLUDING ANY REPRESENTATION THAT THE SERVICES WILL BE UNINTERRUPTED OR ERROR-FREE, AND PROVIDE THE SERVICES (INCLUDING CONTENT, OUTPUT AND INFORMATION) ON AN “AS IS” AND “AS AVAILABLE” BASIS. TO THE FULLEST EXTENT PERMITTED UNDER APPLICABLE LAW, LINKEDIN AND ITS AFFILIATES DISCLAIM ANY IMPLIED OR STATUTORY WARRANTY, INCLUDING ANY IMPLIED WARRANTY OF TITLE, ACCURACY, NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. If you plan to use content, output and information for any reason, it is your responsibility to verify its accuracy and fitness for your purposes, because any content, output and information on the service may not reflect accurate, complete, or current information. 4.2 Exclusion of Liability These are the limits of legal liability we may have to you. TO THE FULLEST EXTENT PERMITTED BY LAW (AND UNLESS LINKEDIN HAS ENTERED INTO A SEPARATE WRITTEN AGREEMENT THAT OVERRIDES THIS CONTRACT), LINKEDIN AND ITS AFFILIATES, WILL NOT BE LIABLE IN CONNECTION WITH THIS CONTRACT FOR LOST PROFITS OR LOST BUSINESS OPPORTUNITIES, REPUTATION (E.G., OFFENSIVE OR DEFAMATORY STATEMENTS), LOSS OF DATA (E.G., DOWN TIME OR LOSS, USE OF, OR CHANGES TO, YOUR INFORMATION OR CONTENT) OR ANY INDIRECT, INCIDENTAL, CONSEQUENTIAL, SPECIAL OR PUNITIVE DAMAGES. LINKEDIN AND ITS AFFILIATES WILL NOT BE LIABLE TO YOU IN CONNECTION WITH THIS CONTRACT FOR ANY AMOUNT THAT EXCEEDS (A) THE TOTAL FEES PAID OR PAYABLE BY YOU TO LINKEDIN FOR THE SERVICES DURING THE TERM OF THIS CONTRACT, IF ANY, OR (B) US $1000. 4.3 Basis of the Bargain; Exclusions The limitations of liability in this Section 4 are part of the basis of the bargain between you and LinkedIn and shall apply to all claims of liability (e.g., warranty, tort, negligence, contract and law) even if LinkedIn or its affiliates has been told of the possibility of any such damage, and even if these remedies fail their essential purpose. THESE LIMITATIONS OF LIABILITY DO NOT APPLY TO LIABILITY FOR DEATH OR PERSONAL INJURY OR FOR FRAUD, GROSS NEGLIGENCE OR INTENTIONAL MISCONDUCT, OR IN CASES OF NEGLIGENCE, WHERE A MATERIAL OBLIGATION HAS BEEN BREACHED. A MATERIAL OBLIGATION BEING AN OBLIGATION WHICH FORMS A PREREQUISITE TO OUR DELIVERY OF SERVICES AND ON WHICH YOU MAY REASONABLY RELY, BUT ONLY TO THE EXTENT THAT THE DAMAGES WERE DIRECTLY CAUSED BY THE BREACH AND WERE FORESEEABLE UPON CONCLUSION OF THIS CONTRACT AND TO THE EXTENT THAT THEY ARE TYPICAL IN THE CONTEXT OF THIS CONTRACT. 5. Termination We can each end this Contract, but some rights and obligations survive. Both you and LinkedIn may terminate this Contract at any time with notice to the other. On termination, you lose the right to access or use the Services. The following shall survive termination: Our rights to use and disclose your feedback; Section 3 (subject to 3.1.1); Sections 4, 6, 7, and 8.2 of this Contract; and Any amounts owed by either party prior to termination remain owed after termination. You can visit our Help Center to learn about how to close your account 6. Governing Law and Dispute Resolution In the unlikely event we end up in a legal dispute, depending on where you live, you and LinkedIn agree to resolve it in California courts using California law, Dublin, Ireland courts using Irish law, or as otherwise provided in this section. If you live in the Designated Countries, the laws of Ireland govern all claims related to LinkedIn's provision of the Services, but this shall not deprive you of the mandatory consumer protections under the law of the country to which we direct your Services where you have habitual residence. With respect to jurisdiction, you and LinkedIn agree to choose the courts of the country to which we direct your Services where you have habitual residence for all disputes arising out of or relating to this User Agreement, or in the alternative, you may choose the responsible court in Ireland. If you are a business user within the scope of Article 6(12) of the EU Digital Markets Act (“DMA”) and have a dispute arising out of or in connection with Article 6(12) of the DMA, you may also utilize the alternative dispute resolution mechanism available in the Help Center . For others outside of Designated Countries, including those who live outside of the United States: You and LinkedIn agree that the laws of the State of California, U.S.A., excluding its conflict of laws rules, shall exclusively govern any dispute relating to this Contract and/or the Services. You and LinkedIn both agree that all claims and disputes can be litigated only in the federal or state courts in Santa Clara County, California, USA, and you and LinkedIn each agree to personal jurisdiction in those courts. You may have additional rights of redress and appeal for some decisions made by LinkedIn that impact you. 7. General Terms Here are some important details about the Contract. If a court with authority over this Contract finds any part of it unenforceable, you and we agree that the court should modify the terms to make that part enforceable while still achieving its intent. If the court cannot do that, you and we agree to ask the court to remove that unenforceable part and still enforce the rest of this Contract. This Contract (including additional terms that may be provided by us when you engage with a feature of the Services) is the only agreement between us regarding the Services and supersedes all prior agreements for the Services. If we don't act to enforce a breach of this Contract, that does not mean that LinkedIn has waived its right to enforce this Contract. You may not assign or transfer this Contract (or your membership or use of Services) to anyone without our consent. However, you agree that LinkedIn may assign this Contract to its affiliates or a party that buys it without your consent. There are no third-party beneficiaries to this Contract. You agree that the only way to provide us legal notice is at the addresses provided in Section 10. 8. LinkedIn “Dos and Don’ts” LinkedIn is a community of professionals. This list of “Dos and Don’ts” along with our Professional Community Policies limits what you can and cannot do on our Services, unless otherwise explicitly permitted by LinkedIn in a separate writing (e.g., through a research agreement). 8.1. Dos You agree that you will: Comply with all applicable laws, including, without limitation, privacy laws, intellectual property laws, anti-spam laws, export control laws, laws governing the content shared, and other applicable laws and regulatory requirements; Provide accurate contact and identity information to us and keep it updated; Use your real name on your profile; and Use the Services in a professional manner. 8.2. Don’ts You agree that you will not : Create a false identity on LinkedIn, misrepresent your identity, create a Member profile for anyone other than yourself (a real person), or use or attempt to use another’s account (such as sharing log-in credentials or copying cookies); Develop, support or use software, devices, scripts, robots or any other means or processes (such as crawlers, browser plugins and add-ons or any other technology) to scrape or copy the Services, including profiles and other data from the Services; Override any security feature or bypass or circumvent any access controls or use limits of the Services (such as search results, profiles, or videos); Copy, use, display or distribute any information (including content) obtained from the Services, whether directly or through third parties (such as search tools or data aggregators or brokers), without the consent of the content owner (such as LinkedIn for content it owns); Disclose information that you do not have the consent to disclose (such as confidential information of others (including your employer); Violate the intellectual property rights of others, including copyrights, patents, trademarks, trade secrets or other proprietary rights. For example, do not copy or distribute (except through the available sharing functionality) the posts or other content of others without their permission, which they may give by posting under a Creative Commons license; Violate the intellectual property or other rights of LinkedIn, including, without limitation, (i) copying or distributing our learning videos or other materials, (ii) copying or distributing our technology, unless it is released under open source licenses; or (iii) using the word “LinkedIn” or our logos in any business name, email, or URL except as provided in the Brand Guidelines ; Post (or otherwise share) anything that contains software viruses, worms, or any other harmful code; Reverse engineer, decompile, disassemble, decipher or otherwise attempt to derive the source code for the Services or any related technology that is not open source; Imply or state that you are affiliated with or endorsed by LinkedIn without our express consent (e.g., representing yourself as an accredited LinkedIn trainer); Rent, lease, loan, trade, sell/re-sell or otherwise monetize the Services or related data or access to the same, without LinkedIn’s consent; Deep-link to our Services for any purpose other than to promote your profile or a Group on our Services, without LinkedIn’s consent; Use bots or other unauthorized automated methods to access the Services, add or download contacts, send or redirect messages, create, comment on, like, share, or re-share posts, or otherwise drive inauthentic engagement; Engage in “framing”, “mirroring”, or otherwise simulating the appearance or function of the Services; Overlay or otherwise modify the Services or their appearance (such as by inserting elements into the Services or removing, covering, or obscuring an advertisement included on the Services); Interfere with the operation of, or place an unreasonable load on, the Services (e.g., spam, denial of service attack, viruses, manipulating algorithms); Violate the Professional Community Policies , certain third party terms where applicable, or any additional terms concerning a specific Service that are provided when you sign up for or start using such Service; Use our Services to do anything that is unlawful, misleading, discriminatory, fraudulent or deceitful (e.g. manipulated media that wrongfully depicts a person saying or doing something they did not say or do); and/or Misuse our reporting or appeals process, including by submitting duplicative, fraudulent or unfounded reports, complaints or appeals. 9. Complaints Regarding Content Contact information for complaints about content provided by our Members. We ask that you report content and other information that you believe violates your rights (including intellectual property rights), our Professional Community Policies or otherwise violates this Contract or the law. To the extent we can under law, we may remove or restrict access to content, features, services, or information, including if we believe that it’s reasonably necessary to avoid harm to LinkedIn or others, violates the law or is reasonably necessary to prevent misuse of our Services. We reserve the right to take action against serious violations of this Contract, including by implementing account restrictions for significant violations. We respect the intellectual property rights of others. We require that information shared by Members be accurate and not in violation of the intellectual property rights or other rights of third parties. We provide a policy and process for complaints concerning content shared, and/or trademarks used, by our Members. 10. How To Contact Us Our Contact information. Our Help Center also provides information about our Services. For general inquiries, you may contact us online . For legal notices or service of process, you may write us at these addresses . LinkedIn © 2026 About Accessibility User Agreement Privacy Policy Cookie Policy Copyright Policy Brand Policy Guest Controls Community Guidelines العربية (Arabic) বাংলা (Bangla) Čeština (Czech) Dansk (Danish) Deutsch (German) Ελληνικά (Greek) English (English) Español (Spanish) فارسی (Persian) Suomi (Finnish) Français (French) हिंदी (Hindi) Magyar (Hungarian) Bahasa Indonesia (Indonesian) Italiano (Italian) עברית (Hebrew) 日本語 (Japanese) 한국어 (Korean) मराठी (Marathi) Bahasa Malaysia (Malay) Nederlands (Dutch) Norsk (Norwegian) ਪੰਜਾਬੀ (Punjabi) Polski (Polish) Português (Portuguese) Română (Romanian) Русский (Russian) Svenska (Swedish) తెలుగు (Telugu) ภาษาไทย (Thai) Tagalog (Tagalog) Türkçe (Turkish) Українська (Ukrainian) Tiếng Việt (Vietnamese) 简体中文 (Chinese (Simplified)) 正體中文 (Chinese (Traditional)) Language | 2026-01-13T08:48:28 |
https://dev.to/ngxp/s2e15-igor-minar-on-empathy-in-software-development#main-content | S2E15 - Igor Minar on Empathy in Software Development - DEV Community Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account DEV Community Close Angular Experience Follow S2E15 - Igor Minar on Empathy in Software Development May 9 '22 play SHOW SUMMARY: In today’s episode we welcome back Igor Minar for a discussion about empathy and what it means to practice empathy for self, for others, and as a software engineer. How can empathy help you live a better life, improve relationships, and help you improve your performance on the job? Igor answers all this and more! LINKS: https://blog.angular.io/thank-you-angular-d90d70f2e9d8 https://igor.dev/posts/experiences-web-frameworks-future-me/ http://blog.igorminar.com/ https://www.audible.com/pd/Tribes-Audiobook/B002V59XXW?action_code=ASSGB149080119000H&share_location=pdp&shareTest=TestShare https://www.headspace.com/ CONNECT WITH US: Igor Minar @IgorMinar Brooke Avery @JediBravery Erik Slack @Erikslack Episode source Personal Trusted User Create template Templates let you quickly answer FAQs or store snippets for re-use. Submit Preview Dismiss Your browser does not support the audio element. 1x initializing... × 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV DEV Community — A space to discuss and keep up software development and manage your software career Home DEV++ Podcasts Videos DEV Education Tracks DEV Challenges DEV Help Advertise on DEV DEV Showcase About Contact Free Postgres Database Software comparisons Forem Shop Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . DEV Community © 2016 - 2026. We're a place where coders share, stay up-to-date and grow their careers. Log in Create account | 2026-01-13T08:48:28 |
https://forem.com/t/programming/page/76 | Programming Page 76 - Security Forem Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account Security Forem Close Programming Follow Hide The magic behind computers. 💻 🪄 Create Post Older #programming posts 73 74 75 76 77 78 79 80 81 Posts Left menu 👋 Sign in for the ability to sort posts by relevant , latest , or top . Right menu The Modern Scrapy Developer's Guide (Part 3): Auto-Generating Page Objects with Web Scraping Co-pilot John Rooney John Rooney John Rooney Follow for Zyte Dec 16 '25 The Modern Scrapy Developer's Guide (Part 3): Auto-Generating Page Objects with Web Scraping Co-pilot # tutorial # scrapy # programming # webscraping Comments Add Comment 5 min read Creating Engaging Tableau Dashboards Using GIFs Perceptive Analytics Perceptive Analytics Perceptive Analytics Follow Dec 18 '25 Creating Engaging Tableau Dashboards Using GIFs # webdev # programming # ai # javascript 1 reaction Comments Add Comment 5 min read The Modern Scrapy Developer's Guide (Part 2): Page Objects with scrapy-poet John Rooney John Rooney John Rooney Follow for Zyte Dec 16 '25 The Modern Scrapy Developer's Guide (Part 2): Page Objects with scrapy-poet # programming # tutorial # scrapy # webscraping Comments Add Comment 6 min read The Modern Scrapy Developer's Guide (Part 1): Building Your First Spider John Rooney John Rooney John Rooney Follow for Zyte Dec 16 '25 The Modern Scrapy Developer's Guide (Part 1): Building Your First Spider # programming # webscraping # scrapy # tutorial Comments Add Comment 6 min read AI Tools for Software Development: What Agencies Are Using to Bring Projects to Life Rootstack Rootstack Rootstack Follow Dec 18 '25 AI Tools for Software Development: What Agencies Are Using to Bring Projects to Life # ai # webdev # programming Comments Add Comment 4 min read Token Box Model rokoss21 rokoss21 rokoss21 Follow Dec 16 '25 Token Box Model # webdev # ai # programming # opensource Comments Add Comment 2 min read Adapter Requirements rokoss21 rokoss21 rokoss21 Follow Dec 16 '25 Adapter Requirements # webdev # programming # ai # architecture Comments Add Comment 3 min read Designing Terminal UX for AI is really about DX (and a few classic UX principles) Vyacheslav Mayorskiy Vyacheslav Mayorskiy Vyacheslav Mayorskiy Follow Dec 16 '25 Designing Terminal UX for AI is really about DX (and a few classic UX principles) # ai # cli # programming # ux Comments Add Comment 3 min read Loading TXT, CSV, and Other Delimited Files Dipti Moryani Dipti Moryani Dipti Moryani Follow Dec 17 '25 Loading TXT, CSV, and Other Delimited Files # webdev # programming # ai # beginners Comments Add Comment 5 min read SkyHetu: Designing a Causality-First Programming Language in Rust kargathara Aakash kargathara Aakash kargathara Aakash Follow Jan 7 SkyHetu: Designing a Causality-First Programming Language in Rust # rust # causality # skyhetu # programming Comments Add Comment 3 min read 7 Essential Libraries for Modern Node.js Backend Development James Miller James Miller James Miller Follow Dec 17 '25 7 Essential Libraries for Modern Node.js Backend Development # node # webdev # programming # ai 1 reaction Comments Add Comment 5 min read The Contract Layer rokoss21 rokoss21 rokoss21 Follow Dec 16 '25 The Contract Layer # webdev # programming # ai # architecture Comments Add Comment 3 min read The Secret Life of Go: Packages and Structure Aaron Rose Aaron Rose Aaron Rose Follow Dec 28 '25 The Secret Life of Go: Packages and Structure # go # coding # programming # softwaredevelopment 6 reactions Comments Add Comment 5 min read The AI Agent Automation Process: From Idea to Reliable Production IanaNickos IanaNickos IanaNickos Follow Dec 16 '25 The AI Agent Automation Process: From Idea to Reliable Production # ai # webdev # programming # javascript Comments Add Comment 5 min read Linux Kernel Architecture: From Ring 0 to Network Stack & eBPF kt kt kt Follow Jan 10 Linux Kernel Architecture: From Ring 0 to Network Stack & eBPF # linux # kernel # ebpf # programming Comments Add Comment 9 min read Building vtracer: Day 1 – My First Java Agent Adventure with Java 21 Abhi Abhi Abhi Follow Dec 16 '25 Building vtracer: Day 1 – My First Java Agent Adventure with Java 21 # webdev # programming # java # tutorial Comments Add Comment 2 min read Introducing Supabase ETL Yuri Yuri Yuri Follow for Supabase Dec 22 '25 Introducing Supabase ETL # vectordatabase # ai # programming # database 6 reactions Comments Add Comment 4 min read Dompurify : Prevent XSS Attack remove all the script tag. Anupam Pandey Anupam Pandey Anupam Pandey Follow Dec 17 '25 Dompurify : Prevent XSS Attack remove all the script tag. # webdev # javascript # dompurify # programming Comments Add Comment 1 min read How to Choose the Right Tech Stack for Your Software Project Priya dharshini Priya dharshini Priya dharshini Follow Dec 17 '25 How to Choose the Right Tech Stack for Your Software Project # webdev # programming # ai # opensource Comments Add Comment 3 min read Breaking data for fun Dmitriy Dmitriy Dmitriy Follow Dec 16 '25 Breaking data for fun # data # database # programming # tutorial Comments Add Comment 9 min read FACET Manifesto rokoss21 rokoss21 rokoss21 Follow Dec 16 '25 FACET Manifesto # webdev # programming # ai # architecture Comments Add Comment 2 min read Read live data from Google Sheets in Mini Micro JoeStrout JoeStrout JoeStrout Follow Dec 17 '25 Read live data from Google Sheets in Mini Micro # miniscript # minimicro # programming # networking 1 reaction Comments Add Comment 4 min read Day 10 of My Web Dev Journey — Mastering CSS Positions: Absolute, Relative, Fixed & Sticky bblackwind bblackwind bblackwind Follow Dec 17 '25 Day 10 of My Web Dev Journey — Mastering CSS Positions: Absolute, Relative, Fixed & Sticky # webdev # programming # css # frontend Comments Add Comment 3 min read Supercharge Your Web Dev Game with MCP - Part 2: Chrome DevTools MCP + AI-Driven Web Performance Susanna Wong Susanna Wong Susanna Wong Follow Dec 30 '25 Supercharge Your Web Dev Game with MCP - Part 2: Chrome DevTools MCP + AI-Driven Web Performance # webdev # ai # programming # productivity 1 reaction Comments Add Comment 7 min read MindsEye & MindScript: A Ledger-First Cognitive Architecture Technical Whitepaper v4.0 PEACEBINFLOW PEACEBINFLOW PEACEBINFLOW Follow Dec 17 '25 MindsEye & MindScript: A Ledger-First Cognitive Architecture Technical Whitepaper v4.0 # programming # ai # mindseye # opensource 9 reactions Comments 1 comment 18 min read loading... 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV Security Forem — Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Home About Contact Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . Security Forem © 2016 - 2026. Share. Secure. Succeed Log in Create account | 2026-01-13T08:48:28 |
https://dev.to/all-the-code/sara-williams-newcastle-university#main-content | Sara Williams Newcastle University - DEV Community Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account DEV Community Close All the Code Follow Sara Williams Newcastle University Oct 16 '21 play This episode I have a fabulous conversation with Sara Williams from Newcastle University careers service about the changing landscape of tech hiring, what you can do to stand out from the crowd and how universities are staying relevant in the age of YouTube and Bootcamps. Episode source Personal Trusted User Create template Templates let you quickly answer FAQs or store snippets for re-use. Submit Preview Dismiss Your browser does not support the audio element. 1x initializing... × 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV DEV Community — A space to discuss and keep up software development and manage your software career Home DEV++ Podcasts Videos DEV Education Tracks DEV Challenges DEV Help Advertise on DEV DEV Showcase About Contact Free Postgres Database Software comparisons Forem Shop Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . DEV Community © 2016 - 2026. We're a place where coders share, stay up-to-date and grow their careers. Log in Create account | 2026-01-13T08:48:28 |
https://stackoverflow.blog/releases/stack-overflow/ | Stack Overflow - Stack Overflow Blog Loading… Everything Productivity AI/ML Open Source Business Hub Company Releases Podcast Newsletter Stack Overflow Business Stack Internal : the knowledge intelligence layer that powers enterprise AI. Stack Data Licensing : decades of verified, technical knowledge to boost AI performance and trust. Stack Ads : engage developers where it matters — in their daily workflow. Stack Overflow January 5, 2026 What’s new at Stack Overflow: January 2026 For this first edition of the new year, we’re taking a step back to highlight some of the most impactful features shipped over the last year and how they can help you start 2026 strong. Zach Rutta 0 comment s December 1, 2025 What’s new at Stack Overflow: December 2025 Including a new MCP server, expanded access to a new question type, a long requested community ask to make copying code easier, and more! Zach Rutta 0 comment s November 3, 2025 What’s new at Stack Overflow: November 2025 From a new kind of vote to a preview of the upcoming redesign, check out what’s been happening at Stack Overflow over the past month. Zach Rutta 1 comment October 8, 2025 A new look for comments Learn about what’s new with comments on Stack Overflow. Kate Smith 1 comment June 4, 2024 Introducing Staging Ground: The private space to get feedback on questions before they’re posted Learn about the workflow designed to help new askers improve their questions on Stack Overflow. Jeff Tan 5 comment s February 8, 2024 Discussions now taking place across all tags on Stack Overflow Expanding the experiment to create the space for developers to have meaningful conversations about their favorite technologies. Janice Manningham 4 comment s October 4, 2022 Meet Saves: the tool to help you organize your favorite content on Stack Overflow Learn about our newly designed tool to help make your favorite questions and answers easier to find. Jeff T 7 comment s Show more Our Stack Stack Internal Features Customers Security Pricing Stack Data Licensing Stack Ads Partnerships Services Stack Overflow Company Leadership Press Careers Social Impact Support Contact Stack Overflow help Stack Internal help Terms Privacy policy Cookie policy Your Privacy Choices Elsewhere Blog Dev Newsletter Podcast Releases Dev Survey Site design / logo © 2026 Stack Exchange Inc. Light Dark Auto | 2026-01-13T08:48:28 |
https://stackoverflow.blog/2025/12/31/a-look-under-the-hood-how-and-why-we-built-question-assistant/ | A look under the hood: How (and why) we built Question Assistant - Stack Overflow Blog Loading… Everything Productivity AI/ML Open Source Business Hub Company Releases Podcast Newsletter Stack Overflow Business Stack Internal : the knowledge intelligence layer that powers enterprise AI. Stack Data Licensing : decades of verified, technical knowledge to boost AI performance and trust. Stack Ads : engage developers where it matters — in their daily workflow. December 31, 2025 A look under the hood: How (and why) we built Question Assistant Evaluating question quality and determining the appropriate feedback required some classic ML techniques in addition to our GenAI solution. Credit: Alexandra Francis [Ed. note: While we take some time to rest up over the holidays and prepare for next year, we are re-publishing our top ten posts for the year. Please enjoy our favorite work this year and we’ll see you in 2026.] Last year we released Staging Ground to help new question-askers get feedback on their drafts from experienced users in a dedicated space before their question is posted publicly on Stack Overflow. We’ve since seen measurable improvements in the quality of questions posted; however, it still takes time for a question to get human feedback and make it through the full Staging Ground process. Reviewers also noticed that they were repeating the same comments over and over: this post doesn’t belong here, there’s context missing, it’s a duplicate, etc. In classic Stack Overflow fashion, there are even comment templates they can apply for the right situations. This looked like an opportunity to use machine learning and AI to identify those common cases and speed up the process so human reviewers could spend their time tackling the more nuanced cases. Thanks to our partnership with Google , we had a solid AI tool (Gemini) to help us test, identify, and produce automated feedback. In the end, we found that evaluating question quality and determining the appropriate feedback required some classic ML techniques in addition to our generative AI solution. This article will walk through how we considered, implemented, and measured the results of Question Assistant . What is a good question? LLMs can provide a lot of useful insights on text, so we were naturally curious if they could produce a quality rating for a question in a particular category. To start, we used three categories and defined them in prompts: context and background, expected outcome, and formatting and readability. These categories were chosen because they were the most common areas in which reviewers were writing the same comments repeatedly to help new askers improve their questions in Staging Ground. Our tests with LLMs showed they could not reliably predict quality ratings and provide feedback that correlated with each other. The feedback itself was repetitive and did not correspond with the category—for example, all three categories would regularly include feedback about the version of the library or programming language, which was not exactly useful. Worse still, the quality rating and feedback wouldn’t change after the question draft was updated. For an LLM to reliably rate the quality of a question when the concept itself is subjective in nature, we needed to define, through data, what a quality question is. While Stack Overflow has guidelines for how to ask a good question , quality is not something that can be easily translated into a numerical score. That meant we needed to create a labeled dataset that we could use to train and evaluate our ML models. We started by trying to create a ground truth data set, one that contained data on how to rate questions. In a survey sent to 1,000 question-reviewers, we asked them to rate the quality of questions on a scale of 1 to 5 in the three categories. 152 participants fully completed the survey. After running the results through Krippendorff’s alpha , we got a pretty low score, which meant this labeled data wouldn’t make reliable training and evaluation data. As we continued exploring the data, we came to the conclusion that a numerical rating doesn’t provide actionable feedback. If someone gets a 3 in a category, does that mean they need to improve it in order to post their question? The numerical rating doesn’t give context for what, how, or where the question needs to be improved. While we wouldn’t be able to use an LLM to determine quality, our survey did affirm the importance of the feedback categories for that purpose. That led us to our alternative approach: building out feedback indicators for each of the previously mentioned categories. Rather than predicting the score directly, we built out individual models that would indicate whether a question should receive feedback for that specific indicator. Building indicator models Instead of using only an LLM with the possibility of a wide range of responses and generic outputs, we created individual logistic regression models. These produce a binary response based on the question title and body. Essentially: Does this question need a specific comment template applied to it or not? For our first experiment, we chose a single category to build models for: context and background. We broke the category into four individual and actionable feedback indicators: Problem definition : The problem or goal is lacking information to understand what the user is trying to accomplish. Attempt details : The question needs additional information on what you have tried and the pertinent code (as relevant). Error details: The question needs additional information on error messages and debugging logs (as relevant). Missing MRE : Missing a minimal reproducible example using a portion of your code that reproduces the problem. We derived these feedback indicators from clustering reviewer comments on Staging Ground posts to find the common themes between them. Conveniently, these themes also matched our existing comment templates and question close reasons, so we could use past data in training a model to detect them. Those reviewer comments and close comments were all vectorized using term frequency inverse document frequency (TF IDF) before passing in those features to logistic regression models. Although we were building more traditional ML models to flag questions based on quality indicators, we still needed to pair it with an LLM in the workflow to provide actionable feedback. Once an indicator flags a question, it sends a preloaded response text with the question to Gemini, along with some system prompts. Gemini then synthesizes these to produce feedback that addresses the indicator, but is specific to the question. This mermaid diagram shows the flow: We trained and stored these models within our Azure Databricks ecosystem. In production, a dedicated service on Azure Kubernetes downloads from Databricks Unity Catalog and hosts the models to generate predictions upon feedback request. Then our models were ready to start generating feedback. Testing it on site We ran this experiment in two stages: first on Staging Ground only, then on stackoverflow.com for all question askers with Ask Wizard . To measure success, we collected events through Azure Event Hub and logged predictions and results to Datadog to understand whether or not the generated feedback was helpful for the user, and to improve future iterations of the indicator models. Our first experiment was in Staging Ground, where we could focus on new askers who likely needed the most help drafting their first question. We ran it as an A/B test, where all eligible Staging Ground askers were allocated for the experiment, split 50/50 between the control and variant groups. The control group did not receive assistance from Gemini, while the variant group did receive assistance from Gemini. Our goal was to see if the Question Assistant could increase the number of questions approved to the main site and reduce the time questions spent in review. The results of the experiment were inconclusive based on our original goal metrics; neither approval rates nor average review times improved significantly for the variant group compared to the control. But it turns out that this solution actually solves a different problem. We saw a meaningful increase in success rates for questions; that is, questions that stay open on the site and receive an answer or a post score of at least plus two. So while we did not find what we were originally looking for, the experiment still validated that Question Assistant had value to askers and a positive impact on question quality. For the second experiment, we ran the A/B test on all eligible askers on the Ask Question page with the Ask Wizard. This time, we wanted to confirm the results of the first experiment and see if Question Assistant could also help more experienced question-askers. We saw a steady success rate of +12% across both experiments. With the meaningful success rates and consistency of our findings, we made Question Assistant available to all askers on Stack Overflow on March 6, 2025. The next step forward Changing course is not uncommon in research and early development. But realizing when you're on a path that won’t provide impact and pivoting to new logic is key to making sure all the puzzle pieces still fit together, just in a different way. With traditional ML and Gemini working together, we were able to fuse the suggested indicator feedback and the question text in order to provide more specific, contextual feedback that is actionable for the asker in improving their question, making it easier for users to find the knowledge they need. This is one step forward in our work to improve the core Q&A flows to make asking, answering, and contributing to knowledge easier for everyone. And we’re not done with Question Assistant just yet. Our Community Product teams are looking ahead to ways we can iterate on the indicator models and further optimize the question-asking experience with this feature. Author s Derek Cheng Senior Machine Learning Engineer Staff Caroline Thomas Staff Ryan Donovan Staff questions staging ground Question Assistant AI ML Engineering Recent articles January 12, 2026 Now everyone can chat on Stack Overflow January 5, 2026 What’s new at Stack Overflow: January 2026 January 2, 2026 A new worst coder has entered the chat: vibe coding without code knowledge January 1, 2026 Documents: The architect’s programming language Latest Podcast January 13, 2026 Vibe code anything in a Hanselminute Add to the discussion Login with your stackoverflow.com account to take part in the discussion. Our Stack Stack Internal Features Customers Security Pricing Stack Data Licensing Stack Ads Partnerships Services Stack Overflow Company Leadership Press Careers Social Impact Support Contact Stack Overflow help Stack Internal help Terms Privacy policy Cookie policy Your Privacy Choices Elsewhere Blog Dev Newsletter Podcast Releases Dev Survey Site design / logo © 2026 Stack Exchange Inc. Light Dark Auto | 2026-01-13T08:48:28 |
https://dev.to/ngxp/s2e13-chau-tran-tale-of-a-vietnamese-immigrant#main-content | S2E13 - Chau Tran, Tale of a Vietnamese Immigrant - DEV Community Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account DEV Community Close Angular Experience Follow S2E13 - Chau Tran, Tale of a Vietnamese Immigrant Apr 25 '22 play SHOW SUMMARY: In today’s episode of NgXP, we get real and raw with Chau Tran about his journey as a Vietnamese immigrant and developer. Chau shares his experiences working in the U.S. after having immigrated. From the good to the bad, Chau discusses both the opportunities he’s seized to the inequalities, biases, and prejudices he has experienced as a programmer of Asian descent. How can we become aware of racial and national biases or stereotypes? What can we do to help our teams, companies, and the developer community at large be better friends and colleagues to our coworkers from beyond our own borders? LINKS: https://twitter.com/ngvnofficial https://nartc.me/ https://www.youtube.com/c/ChauTran/videos CONNECT WITH US: Chau Tran @NarTC1410 Brooke Avery @JediBravery Erik Slack @Erikslack Episode source Personal Trusted User Create template Templates let you quickly answer FAQs or store snippets for re-use. Submit Preview Dismiss Your browser does not support the audio element. 1x initializing... × 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV DEV Community — A space to discuss and keep up software development and manage your software career Home DEV++ Podcasts Videos DEV Education Tracks DEV Challenges DEV Help Advertise on DEV DEV Showcase About Contact Free Postgres Database Software comparisons Forem Shop Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . DEV Community © 2016 - 2026. We're a place where coders share, stay up-to-date and grow their careers. Log in Create account | 2026-01-13T08:48:28 |
https://dev.to/ngxp/s3e0-now-the-devlife-podcast#main-content | S3E0 - Now the Dev.Life Podcast - DEV Community Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account DEV Community Close Angular Experience Follow S3E0 - Now the Dev.Life Podcast Sep 12 '22 play In this episode we reintroduce ourselves this time as the Co-Hosts of the Dev.Life Podcast. For most of you this will simply be an intro to Season 3 of the Angular Experience Podcast. We discuss our plans and goals for this season and why we changed our name. In short it’s because our content is for all developers regardless of framework or language. Links: https:devlife.show Brooke Avery @JediBravery Erik Slack @erik_slack Episode source Personal Trusted User Create template Templates let you quickly answer FAQs or store snippets for re-use. Submit Preview Dismiss Your browser does not support the audio element. 1x initializing... × 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV DEV Community — A space to discuss and keep up software development and manage your software career Home DEV++ Podcasts Videos DEV Education Tracks DEV Challenges DEV Help Advertise on DEV DEV Showcase About Contact Free Postgres Database Software comparisons Forem Shop Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . DEV Community © 2016 - 2026. We're a place where coders share, stay up-to-date and grow their careers. Log in Create account | 2026-01-13T08:48:28 |
https://stackoverflow.blog/2024/06/04/introducing-staging-ground-the-private-space-to-get-feedback-on-questions-before-they-re-posted/ | Introducing Staging Ground: The private space to get feedback on questions before they’re posted - Stack Overflow Blog Loading… Everything Productivity AI/ML Open Source Business Hub Company Releases Podcast Newsletter Stack Overflow Business Stack Internal : the knowledge intelligence layer that powers enterprise AI. Stack Data Licensing : decades of verified, technical knowledge to boost AI performance and trust. Stack Ads : engage developers where it matters — in their daily workflow. June 4, 2024 Introducing Staging Ground: The private space to get feedback on questions before they’re posted Learn about the workflow designed to help new askers improve their questions on Stack Overflow. Over our fifteen years, Stack Overflow has grown to be an essential knowledge resource for developers and technologists around the world. The entire network is built on the premise that good questions asked with a good process behind them can get good answers. However, we know that asking a good question can be pretty daunting for newcomers and first-time question-askers. If you’ve ever spent time looking for an answer or tried drafting a question on Stack Overflow, you may have experienced this first-hand. In 2022, our team tested a concept in beta called Staging Ground—a private space where new askers could get help from experienced users to iterate on and improve their questions before posting to the broader community. These questions are reviewed by users who have honed a process for asking well-crafted questions and want to help other users succeed. We are thrilled to announce that Staging Ground is now available to all new question-askers on Stack Overflow. What is Staging Ground? Staging Ground is a private place where new askers receive guidance from experienced users before their question is posted publicly. When a question is created, it’s moved to a private sandbox where a group of experienced question reviewers evaluate it to help determine if the question is: Ready to post Requires minor changes Requires major changes Off-topic Duplicate Reviewers provide feedback on how to improve questions by leaving comments and moving questions into different statuses based on how much the questions need to be improved. The author of the question can follow the feedback that reviewers provide and edit their question to help improve its quality before posting it on the site. If the author needs more clarity about the feedback they are receiving, they can use the comments section below their question to ask reviewers questions or for additional guidance. When the question is ready, it will be posted on Stack Overflow to receive answers from the entire community. Learn more about the Staging Ground in this Help Center article. Why did we build Staging Ground? We developed Staging Ground to address the challenge faced by many first-time question-askers. We understand that asking questions is hard, and going through this experience alone makes it even harder. With the support of experienced users in a private space, we believe that authors will be able to learn how to craft better questions and increase their chances of getting an answer. Ultimately, our goal is to improve the new user experience while simultaneously improving the quality of questions on Stack Overflow. How can I get started with Staging Ground? As a question-asker: First-time askers create their questions through the Ask Wizard . After creating their question, their post automatically enters Staging Ground for guidance from experienced users before their question is posted publicly. Askers will receive both inbox and email notifications as they receive feedback on their drafted questions. They’ll also be able to see the status of their question by clicking the “Staging Ground” icon on the left sidebar navigation. As a question-reviewer: If you have earned 500 reputation points , you have access to review queues and can join in the efforts to improve the quality of new questions on the platform. To get started reviewing questions, click on the “Staging Ground” icon in the left sidebar navigation or through this link . Let us know what you think! Let us know your thoughts and provide your feedback about Staging Ground on Meta . Additionally, we’ll be conducting future research studies with askers and reviewers to provide feedback on their experience with Staging Ground. To participate in this research, enable research invitations in your profile settings. Author s Jeff Tan Senior Product Manager Staff Releases Latest releases January 5, 2026 What’s new at Stack Overflow: January 2026 December 16, 2025 Your 2025 Stacked: A year of knowledge, community, and impact December 1, 2025 What’s new at Stack Overflow: December 2025 November 12, 2025 2025.8 release introduces Stack Overflow Internal: The next generation of enterprise knowledge intelligence Add to the discussion Login with your stackoverflow.com account to take part in the discussion. Our Stack Stack Internal Features Customers Security Pricing Stack Data Licensing Stack Ads Partnerships Services Stack Overflow Company Leadership Press Careers Social Impact Support Contact Stack Overflow help Stack Internal help Terms Privacy policy Cookie policy Your Privacy Choices Elsewhere Blog Dev Newsletter Podcast Releases Dev Survey Site design / logo © 2026 Stack Exchange Inc. Light Dark Auto | 2026-01-13T08:48:28 |
https://stackoverflow.blog/2025/10/08/a-new-look-for-comments/ | A new look for comments - Stack Overflow Blog Loading… Everything Productivity AI/ML Open Source Business Hub Company Releases Podcast Newsletter Stack Overflow Business Stack Internal : the knowledge intelligence layer that powers enterprise AI. Stack Data Licensing : decades of verified, technical knowledge to boost AI performance and trust. Stack Ads : engage developers where it matters — in their daily workflow. October 8, 2025 A new look for comments Learn about what’s new with comments on Stack Overflow. We're excited to announce a new comments user interface for posts on Stack Overflow. With this update, all registered users can now comment on questions and answers. Previously, commenting was a privilege that required 50 reputation to use, but is now a standard feature available to all users. Comments on Stack Overflow Comments enable users to engage with the community and begin sharing their point of view on the platform. They add nuance and perspective to the Q&A pages and improve the quality of responses. With this new user interface, we have introduced threaded comments and the ability to vote on comments for everyone. Introducing threading for easy, followable exchanges Following a topic being discussed, especially in dense Q&A conversations, can be challenging. With the new commenting UI update, users can now follow a topic and the exchange around a comment more easily. Threading allows follow up comments to be threaded directly below the parent comment, making back-and-forth discussions more cohesive. Allowing longer-standing comments to live within threads in the Q&A repository adds historical value to the question and answer past its initial resolution and provides evergreen exchanges to have thorough context for future discussions. Drive contribution impact by voting on comments Imagine trying to navigate a repository without a rating system. That sounds a lot like deciphering the best content by yourself every time. To assist in identifying valuable contributions, we have extended our voting system so that all users can now vote on the comments that provide the most value. When you set out to understand a question or answer completely, you can now upvote the comments that help you and future users grasp the full scope of the topic. Additionally, we have enhanced our flagging system to prohibit spamming of the commenting interface with material that does not add value to the Q & A library and to preserve the integrity and value of the repository. Start commenting today Commenting is now available to all users across Stack Overflow . To learn more about how to use comments, review the Help Center article . Author s Kate Smith Product Marketing Manager Staff Community new features comments Releases Latest releases January 5, 2026 What’s new at Stack Overflow: January 2026 December 16, 2025 Your 2025 Stacked: A year of knowledge, community, and impact December 1, 2025 What’s new at Stack Overflow: December 2025 November 12, 2025 2025.8 release introduces Stack Overflow Internal: The next generation of enterprise knowledge intelligence Add to the discussion Login with your stackoverflow.com account to take part in the discussion. Our Stack Stack Internal Features Customers Security Pricing Stack Data Licensing Stack Ads Partnerships Services Stack Overflow Company Leadership Press Careers Social Impact Support Contact Stack Overflow help Stack Internal help Terms Privacy policy Cookie policy Your Privacy Choices Elsewhere Blog Dev Newsletter Podcast Releases Dev Survey Site design / logo © 2026 Stack Exchange Inc. Light Dark Auto | 2026-01-13T08:48:28 |
https://stackoverflow.blog/2025/09/30/turning-investments-into-impact-stack-overflow-for-teams-2025-7/ | Turning investments into impact: Stack Overflow for Teams 2025.7 - Stack Overflow Blog Loading… Everything Productivity AI/ML Open Source Business Hub Company Releases Podcast Newsletter Stack Overflow Business Stack Internal : the knowledge intelligence layer that powers enterprise AI. Stack Data Licensing : decades of verified, technical knowledge to boost AI performance and trust. Stack Ads : engage developers where it matters — in their daily workflow. September 30, 2025 Turning investments into impact: Stack Overflow for Teams 2025.7 Over the past few releases, we’ve been investing in the foundation of Stack Overflow for Teams—strengthening infrastructure, modernizing integrations, and preparing for bigger shifts to come. Over the past few releases, we’ve been investing in the foundation of Stack Overflow for Teams—strengthening infrastructure, modernizing integrations, and preparing for bigger shifts to come. With the 2025.7 release, those investments translate into visible wins throughout Stack Overflow for Teams. Check out what’s new! Stack Overflow for Teams SDK: Build with confidence Developers now have an official way to extend and integrate Stack Overflow for Teams. The new Teams SDK goes beyond API endpoints to provide a higher-level developer experience, complete with official support and TypeScript definitions for all endpoints. With the SDK, organizations can: Build internal tools and extensions to tailor Teams to their workflows Integrate Teams with CI/CD pipelines, project management tools, or custom dashboards Manage knowledge more effectively by connecting Teams with existing systems Create custom applications that activate and distribute knowledge across the enterprise By removing friction and providing a supported foundation, the SDK empowers teams to innovate on top of Stack Overflow for Teams. Commenting improvements: structured, intuitive, and @ mention ready Collaboration works best when it’s easy to follow the conversation. That’s why we’ve redesigned commenting to bring more structure, clarity, and engagement to discussions. Threaded replies keep conversations organized and easier to follow. Redesigned interface makes replying and upvoting feel intuitive and clutter-free. @ mentions let you pull in the right teammate at the right moment. Originally developed for the public Stack Overflow platform, these features are now available to enterprise customers—making it easier than ever to capture knowledge, connect with colleagues, and spark meaningful dialogue. From groundwork to growth What once looked like behind-the-scenes platform work is now delivering visible value—helping end users collaborate more effectively and giving IT admins the tools they need to manage Teams with confidence. All features in the 2025.7 release will be live in Enterprise environments by 12pm ET on October 1, 2025 . To learn more, visit the release notes , or reach out to your Customer Success partner with any questions. Learn more at Microsoft Ignite The 2025.7 release is just one example of how ongoing investments in Stack Overflow for Teams are unlocking better experiences for everyone. Want a deeper glimpse into the future of Stack Overflow for Teams? Join us at Microsoft Ignite, November 18–21, where we’ll share more about how Teams continues to evolve to meet the needs of enterprise organizations. Author s Carrie Koos Staff Stack Internal Releases Stack Overflow Internal Where developers & technologists share private knowledge with coworkers. Learn more Latest releases January 5, 2026 What’s new at Stack Overflow: January 2026 December 16, 2025 Your 2025 Stacked: A year of knowledge, community, and impact December 1, 2025 What’s new at Stack Overflow: December 2025 November 12, 2025 2025.8 release introduces Stack Overflow Internal: The next generation of enterprise knowledge intelligence Add to the discussion Login with your stackoverflow.com account to take part in the discussion. Our Stack Stack Internal Features Customers Security Pricing Stack Data Licensing Stack Ads Partnerships Services Stack Overflow Company Leadership Press Careers Social Impact Support Contact Stack Overflow help Stack Internal help Terms Privacy policy Cookie policy Your Privacy Choices Elsewhere Blog Dev Newsletter Podcast Releases Dev Survey Site design / logo © 2026 Stack Exchange Inc. Light Dark Auto | 2026-01-13T08:48:28 |
https://docs.suprsend.com/docs/managing-notification-categories | Manage Categories and Preferences - SuprSend, Notification infrastructure for Product teams Skip to main content SuprSend, Notification infrastructure for Product teams home page Search... ⌘ K Community Trust Center Platform Status Postman Collection GETTING STARTED What is SuprSend? Quick Start Guide Best Practices Plan Your Integration Go-live checklist CORE CONCEPTS Templates Users Events Workflow Notification Categories Overview Manage Categories and Preferences Preferences Tenants Lists Broadcast Objects Translations DLT Guidelines Whatsapp Template Guidelines WORKFLOW BUILDER Design Workflow Node List Workflow Settings Trigger Workflow Validate Trigger Payload Tenant Workflows Notification Inbox Overview Multi Tabs React Javascript (Angular, Vuejs etc) React Native Flutter (Headless) PREFERENCE CENTRE Embedded Preference Centre Javascript Angular React VENDOR INTEGRATION GUIDE Overview Email Integrations SMS Integrations Android Push Whatsapp Integrations iOS Push Chat Integrations Vendor Fallback Tenant Vendor INTEGRATIONS Webhook Connectors MONITORING & DEBUGGING Logs Audit Logs Error Guides MANAGE YOUR ACCOUNT Authentication Methods Contact Us Get Started SuprSend, Notification infrastructure for Product teams home page Search... ⌘ K Ask AI Contact Us Get Started Get Started Search... Navigation Notification Categories Manage Categories and Preferences Documentation API Reference Management API CLI Reference Developer Resources Changelog Documentation API Reference Management API CLI Reference Developer Resources Changelog Notification Categories Manage Categories and Preferences OpenAI Open in ChatGPT Set up and manage notification categories and preferences in SuprSend. OpenAI Open in ChatGPT Categories are assigned to workflows and are used to manage notification preferences in SuprSend. For detailed concepts, see Notification Categories . Creating sections and sub-categories Go to Developers → Notification categories and select a root-category (System, Transactional, or Promotional). System is for critical account related notifications that users can’t unsubscribe from. Transactional is for notifications sent in response to user actions or transactions. Promotional is for marketing notifications sent to promote products or re-engage users to your platform. Creating a section Sections are optional and help organize sub-categories on the preference page. To create a section: Click +Section Add name and description for the section Click Save Changes You’ll see the updated section inside the category and can edit it later by clicking on the Edit button against that section. Adding sub-categories To add a sub-category: Click +Sub-Category Fill in: Name : What users see (slug (assigned to workflow) will be auto-generated from name) Section : Select the section where this sub-category will be grouped. Leave blank if you don’t want to group it under any section. Description (Optional) : Description is used to describe the kind of notifications sent in the category. Helps users get more context about the category. Don’t change the sub-category name after using it in workflows—it updates the slug and can break existing workflows. Configuring default preferences Select a sub-category and choose a default preference: On , Off , or Can’t Unsubscribe . This determines the default behavior for users who haven’t set their own preference. Preference types On : Users receive notifications by default (they can opt out) Off : Users don’t receive notifications by default (they can opt in) Can’t Unsubscribe : Users cannot fully opt out of these notifications (typically for critical system messages). Users can still opt out of specific channels, but at least one mandatory channel must remain active. Recommended defaults by category type These defaults are recommendations—adjust them based on your product’s requirements and user expectations. System Default: Can't Unsubscribe — Set the channel most users have on as mandatory so they don’t miss critical notifications even if they opt out of all channels. Transactional Default: Can't Unsubscribe — These are notifications sent in response to user actions or transactions. You would generally not want users to opt out of these notifications. However, you can adjust the default preference based on the criticality of the notification. Promotional Default: ON — Users receive notifications by default. For optional categories, set to OFF so users only receive notifications if they explicitly opt in Adding tags (Optional) Tags are used to filter categories on the preference page. Common usecases are to filter categories based on user role or department. They can be added to sections and sub-categories. Select a section or sub-category Add tags (e.g., finance , manager ) Section-level tags apply to all sub-categories in that section Tags within preference categories You can filter categories using the tags query parameter in the get user preference API . Tags do not impact delivery logic or preference rules — they are only used for filtering and organizing the UI. Even if a category is hidden from the user on the preference page due to tag filters, the user can still opt in/out via API, and notifications will still be sent if the default preference is set to opt-in. Preview and publish Before making your categories live, preview how they’ll appear to users, then publish your changes. Category changes are version controlled and are not live until you publish them. This is done to ensure that your users do not see intermittent changes when they are interacting with the preference page. 1 Preview Click Preview to see how categories will appear to users on the preference page. The preview will show how your categories are organized and displayed to users. 2 Publish Click Publish Changes to make categories live. Categories are only available in workflows after publishing and will not appear in workflow dropdowns until published. 3 Clone to production Use Clone to copy changes from staging to production workspace. Not required if you are directly doing changes in production workspace. Clone option is not currently available on UI. Category changes are version controlled and need to be published Categories will only appear in workflow dropdowns after they are published. If you don’t see your category in the dropdown, make sure you’ve published your changes. Assigning category to workflows Via Dashboard in dynamic workflow API Via CLI or Management API In workflow editor, select any delivery node and choose the relevant category from the Notification Category dropdown. Assigning category to workflows Add the category slug to the notification_category field in your workflow trigger. To find the slug: Click the sub-category name in the categories page to copy it. Copying category slug Example: python Copy Ask AI from suprsend import Suprsend, WorkflowTriggerRequest supr_client = Suprsend( "_workspace_key_" , "_workspace_secret_" ) w1 = WorkflowTriggerRequest( body = { "workflow" : "welcome-email" , "recipients" : [{ "distinct_id" : "user-123" }], "notification_category" : "newsletter" # sub-category slug } ) response = supr_client.workflows.trigger(w1) See Trigger Workflow from API for complete workflow payload example. Pass category-slug to category field in workflow payload while updating workflow through management API or CLI . Managing category translations This feature is only available for Enterprise plan customers or the ones who have enabled translation feature in their account. Upload and manage translations for category and section names and descriptions. Once uploaded, translations go live immediately. You can fetch preference translations by passing locale query parameter in the get user preference API . For more details on what it does and how it works, see Overview of category translations . Via Dashboard Via Management API Via CLI 1 Click translation icon On the Preference categories page, click the translation icon in the top right corner to open the “Add / View Translation files” modal. 2 Add translation file Click ”+ Add Translation” . Select a locale and upload the translated JSON file (e.g., es.json , fr.json ), then click “Save & Add” . Translation file structure: Translation files follow this JSON structure with sections and categories objects. Each section and category is identified by its slug. file-structure example Copy Ask AI { "sections" : { "section-slug" : { "name" : "Translated section name" , "description" : "Translated section description" // or null } }, "categories" : { "category-slug" : { "name" : "Translated category name" , "description" : "Translated category description" // or null } } } Note: The en.json file is automatically generated from your preference settings. Download it to use as a template for translations. 3 Preview translations Click the Preview button (next to the translations button) on the Preference categories page to see how if your preview is rendering correctly in different languages. Embeddable preference page preview 4 Clone to production Use CLI command suprsend category translation pull and CLI command suprsend category translation push to copy translations from staging to production workspace. Copy Ask AI suprsend category translation pull suprsend category translation push --workspace production English ( en.json ) is automatically created and cannot be overridden. It serves as the base language for all translations. Use Management API to programmatically add, update, or delete translations for specific locales. See Category Translation API for complete API reference. See CLI Category Translation documentation for category translation pull and category translation push commands. Frequently Asked Questions When should I create sections? Create sections when: Large number of categories : If you have 10+ sub-categories, sections help users navigate the preference page more easily Similar categories : Group related sub-categories together (e.g., “Billing” section for invoice, payment, and subscription categories) Better organization : Sections improve the user experience by organizing categories into logical groups Example: If you have categories like “Invoice Ready”, “Payment Reminder”, and “Subscription Renewal”, group them under a “Billing” section for better organization. How many categories should I create? Keep your category structure simple and focused on the most important notification types. Here are some guidelines: Recommended : 5-8 sub-categories or 5-8 sections and within each section, 2-6 sub-categories. Try to keep total number of categories across all root-categories < 20. Too many categories can overwhelm users and drive them to use channel-level opt-outs instead Too few categories may not give users enough granular control Best practice : Create categories based on user actions or notification flows (e.g., “Order Updates”, “Account Security”, “Marketing Newsletters”) rather than creating a category for every single workflow. My user has opted out of all categories, but they are still receiving notifications This typically happens when you’re using root-categories instead of sub-categories in your workflows. User Preferences do not apply to root-categories (System, Transactional, Promotional). If you’re sending notifications with notification_category: "promotional" or notification_category: "transactional" , users will continue to receive notifications even after opting out of all sub-categories. To fix this : Check your workflow settings and ensure you’re using sub-category slugs (e.g., "marketing" , "order-updates" ) instead of root-category names If you don’t see the sub-categories in dropdown, it is possible that the sub-categories are not published. Category changes are version controlled and are not live until you publish them. How do I show users only the categories relevant to their role or department? Use tags to filter categories based on user roles, departments, or teams. Tags allow you to customize which categories appear on each user’s preference page. How it works : Add tags to sections or sub-categories from the Preference categories page When fetching user preferences via API, pass the tags query parameter to filter categories Only categories matching the specified tags will be returned Important : Tags only affect what’s shown on the preference page—they don’t impact delivery logic. Users can still opt in/out, and notifications will be sent based on default preferences if the category is hidden from the UI. Read more about tags here . Related documentation Notification Categories - Concepts and detailed explanations of notification categories User Preferences - Overview of how users can set their Preferences Tenant Preferences - How to apply admin-level preference settings to all users belonging to a tenant Preference Evaluation - How SuprSend evaluates preferences at runtime Was this page helpful? Yes No Suggest edits Raise issue Previous User Preferences Learn how user preferences work in SuprSend and how to capture them. Next ⌘ I x github linkedin youtube Powered by On this page Creating sections and sub-categories Creating a section Adding sub-categories Configuring default preferences Preference types Recommended defaults by category type Adding tags (Optional) Preview and publish Assigning category to workflows Managing category translations Frequently Asked Questions Related documentation self.__next_f.push([1,"24:I[79890,[\"73473\",\"static/chunks/891cff7f-dcf0b8e94fd9e2cd.js?dpl=dpl_F45GrjC1BSn6PXarH9nZEx4kYLiF\",\"53016\",\"static/chunks/cfdfcc00-442051842d4b5e4f.js?dpl=dpl_F45GrjC1BSn6PXarH9nZEx4kYLiF\",\"41725\",\"static/chunk | 2026-01-13T08:48:28 |
https://www.linkedin.com/posts/mrdbourke_new-machine-learning-cooking-video-fully-activity-7416259735630307328-_Kln | model -> shareable hosted demo on Hugging Face Spaces • Why you can get great results in only 5 minutes of training + more What will we build? We’ll be making FoodExtract, a SLM to extract structured data from raw text into structured JSON data we could put straight into a database. Note: This workflow is highly customizable so even though our project is tailored around food/drink, you could substitute almost any kind of data/problem. All training performed locally on a NVIDIA DGX Spark in partnership with NVIDIA AI. Link to video in the top comments. All code and materials available in the video description. Next week: Vision Language Model (VLM) fine-tuning 👁️"> model -> shareable hosted demo on Hugging Face Spaces • Why you can get great results in only 5 minutes of training + more What will we build? We’ll be making FoodExtract, a SLM to extract structured data from raw text into structured JSON data we could put straight into a database. Note: This workflow is highly customizable so even though our project is tailored around food/drink, you could substitute almost any kind of data/problem. All training performed locally on a NVIDIA DGX Spark in partnership with NVIDIA AI. Link to video in the top comments. All code and materials available in the video description. Next week: Vision Language Model (VLM) fine-tuning 👁️"> model -> shareable hosted demo on Hugging Face Spaces • Why you can get great results in only 5 minutes of training + more What will we build? We’ll be making FoodExtract, a SLM to extract structured data from raw text into structured JSON data we could put straight into a database. Note: This workflow is highly customizable so even though our project is tailored around food/drink, you could substitute almost any kind of data/problem. All training performed locally on a NVIDIA DGX Spark in partnership with NVIDIA AI. Link to video in the top comments. All code and materials available in the video description. Next week: Vision Language Model (VLM) fine-tuning 👁️"> 🎥 New machine learning cooking video: Fully fine-tune a Small Language Model (SLM) for structured data extraction. Inside you’ll find: • Why you should think about fine-tuning your own SLM • What… | Daniel Bourke Agree & Join LinkedIn By clicking Continue to join or sign in, you agree to LinkedIn’s User Agreement , Privacy Policy , and Cookie Policy . Skip to main content LinkedIn Top Content People Learning Jobs Games Sign in Join now Daniel Bourke’s Post Daniel Bourke 1d Report this post 🎥 New machine learning cooking video: Fully fine-tune a Small Language Model (SLM) for structured data extraction. Inside you’ll find: • Why you should think about fine-tuning your own SLM • What an LLM (or SLM) fine-tuning dataset looks like (and how you can make your own) • Where you can get models/datasets ( Hugging Face of course 🤗) • End-to-end code walkthrough of data -> model -> shareable hosted demo on Hugging Face Spaces • Why you can get great results in only 5 minutes of training + more What will we build? We’ll be making FoodExtract, a SLM to extract structured data from raw text into structured JSON data we could put straight into a database. Note: This workflow is highly customizable so even though our project is tailored around food/drink, you could substitute almost any kind of data/problem. All training performed locally on a NVIDIA DGX Spark in partnership with NVIDIA AI . Link to video in the top comments. All code and materials available in the video description. Next week: Vision Language Model (VLM) fine-tuning 👁️ 421 9 Comments Like Comment Share Copy LinkedIn Facebook X Daniel Bourke 1d Report this comment Video link (code + resources in the description): https://youtu.be/2hoNAr-id-E Like Reply 5 Reactions 6 Reactions NVIDIA AI 17h Report this comment You're crushing it with these tutorials! Like Reply 4 Reactions 5 Reactions Nile Green 11h Report this comment Daniel Bourke great walkthrough on fine-tuning for structured extraction. Here's the question I kept hitting: what happens when your extraction patterns change AFTER deployment? Traditional approach: Collect new data → retrain → redeploy (days/weeks) What we built: Agents learn extraction patterns at runtime through prediction errors - no retraining loop needed. Example: FoodExtract learns that 'burger' → 'sandwich' category. Later encounters 'smash burger' → mispredicts → updates internal mapping → gets it right next time. All at the state layer. No gradient descent. Just gap-based learning. Live demo: https://bapxai.com/voidchis.html Code: https://github.com/hustle-rent-due/PermaMind Not replacing fine-tuning - complementing it. Your SLM handles syntax, ours handles runtime adaptation. NVIDIA AI - curious if test-time training could work at the state layer like this? Seems like weight updates + state updates = best of both worlds. Like Reply 1 Reaction Amelia Thompson 16h Report this comment This is a great example of where small, well-fine-tuned models really shine. For structured data extraction, an SLM that’s fast, controllable, and cheap often beats a general-purpose LLM. Love the end-to-end workflow and the emphasis on practical deployment — looking forward to the VLM fine-tuning next week 👁️🚀 Like Reply 1 Reaction Quinton S. 15h Report this comment Solid. As models get easier to fine-tune, governance around execution becomes the real differentiator. Like Reply 1 Reaction Anum Zeeshan 4h Report this comment Information is amazingly important Like Reply 1 Reaction Peter Green 13h Report this comment Finally someone with an example of finetuning where it makes sense. Like Reply 1 Reaction See more comments To view or add a comment, sign in 31,281 followers 690 Posts 54 Articles View Profile Connect More from this author Introducing Nutrify 2.0: Multi-Food Mode, 552 New Foods and Food Share Daniel Bourke 1mo Introducing Nutrify 1.2.3: Whole Food Streaks, Widgets, Quick Summaries and 41 New Foods Daniel Bourke 1y The importance of a test set Daniel Bourke 1y Explore content categories Career Productivity Finance Soft Skills & Emotional Intelligence Project Management Education Technology Leadership Ecommerce User Experience Show more Show less LinkedIn © 2026 About Accessibility User Agreement Privacy Policy Cookie Policy Copyright Policy Brand Policy Guest Controls Community Guidelines العربية (Arabic) বাংলা (Bangla) Čeština (Czech) Dansk (Danish) Deutsch (German) Ελληνικά (Greek) English (English) Español (Spanish) فارسی (Persian) Suomi (Finnish) Français (French) हिंदी (Hindi) Magyar (Hungarian) Bahasa Indonesia (Indonesian) Italiano (Italian) עברית (Hebrew) 日本語 (Japanese) 한국어 (Korean) मराठी (Marathi) Bahasa Malaysia (Malay) Nederlands (Dutch) Norsk (Norwegian) ਪੰਜਾਬੀ (Punjabi) Polski (Polish) Português (Portuguese) Română (Romanian) Русский (Russian) Svenska (Swedish) తెలుగు (Telugu) ภาษาไทย (Thai) Tagalog (Tagalog) Türkçe (Turkish) Українська (Ukrainian) Tiếng Việt (Vietnamese) 简体中文 (Chinese (Simplified)) 正體中文 (Chinese (Traditional)) Language Sign in to view more content Create your free account or sign in to continue your search Sign in Welcome back Email or phone Password Show Forgot password? Sign in or By clicking Continue to join or sign in, you agree to LinkedIn’s User Agreement , Privacy Policy , and Cookie Policy . New to LinkedIn? Join now or New to LinkedIn? Join now By clicking Continue to join or sign in, you agree to LinkedIn’s User Agreement , Privacy Policy , and Cookie Policy . | 2026-01-13T08:48:28 |
https://www.coursera.org/account/accomplishments/verify/SHF8Y2BUYNXZ?trk=public_profile_see-credential | Coursera | Online Courses & Credentials From Top Educators. Join for Free | Coursera For Individuals For Businesses For Universities For Governments Explore Degrees ​ Log In Join for Free Join for Free Course Certificate Sequence Models Completed by Daniel Bourke February 13, 2018 37 hours (approximately) Daniel Bourke's account is verified. Coursera certifies their successful completion of Sequence Models Sequence Models DeepLearning.AI Filled Star Filled Star Filled Star Filled Star Filled Star 4.8 (31,204 ratings) | 454,113 already enrolled Enroll for Free Skills you will gain Embeddings Deep Learning Artificial Neural Networks Transfer Learning Natural Language Processing Hugging Face Recurrent Neural Networks (RNNs) Coursera Footer Skills Artificial Intelligence (AI) Cybersecurity Data Analytics Digital Marketing English Speaking Generative AI (GenAI) Microsoft Excel Microsoft Power BI Project Management Python Certificates & Programs Google Cybersecurity Certificate Google Data Analytics Certificate Google IT Support Certificate Google Project Management Certificate Google UX Design Certificate IBM Data Analyst Certificate IBM Data Science Certificate Machine Learning Certificate Microsoft Power BI Data Analyst Certificate UI / UX Design Certificate Industries & Careers Business Computer Science Data Science Education & Teaching Engineering Finance Healthcare Human Resources (HR) Information Technology (IT) Marketing Career Resources Career Aptitude Test Examples of Strengths and Weaknesses for Job Interviews High-Income Skills to Learn How Does Cryptocurrency Work? How to Highlight Duplicates in Google Sheets How to Learn Artificial Intelligence Popular Cybersecurity Certifications Preparing for the PMP Certification Signs You Will Get the Job After an Interview What Is Artificial Intelligence? Coursera About What We Offer Leadership Careers Catalog Coursera Plus Professional Certificates MasterTrack® Certificates Degrees For Enterprise For Government For Campus Become a Partner Social Impact Free Courses Share your Coursera learning story Community Learners Partners Beta Testers Blog The Coursera Podcast Tech Blog More Press Investors Terms Privacy Help Accessibility Contact Articles Directory Affiliates Modern Slavery Statement Cookies Preference Center Learn Anywhere © 2026 Coursera Inc. All rights reserved. | 2026-01-13T08:48:28 |
https://docs.suprsend.com/docs/connectors | Overview - SuprSend, Notification infrastructure for Product teams Skip to main content SuprSend, Notification infrastructure for Product teams home page Search... ⌘ K Community Trust Center Platform Status Postman Collection GETTING STARTED What is SuprSend? Quick Start Guide Best Practices Plan Your Integration Go-live checklist CORE CONCEPTS Templates Users Events Workflow Notification Categories Preferences Tenants Lists Broadcast Objects Translations DLT Guidelines Whatsapp Template Guidelines WORKFLOW BUILDER Design Workflow Node List Workflow Settings Trigger Workflow Validate Trigger Payload Tenant Workflows Notification Inbox Overview Multi Tabs React Javascript (Angular, Vuejs etc) React Native Flutter (Headless) PREFERENCE CENTRE Embedded Preference Centre Javascript Angular React VENDOR INTEGRATION GUIDE Overview Email Integrations SMS Integrations Android Push Whatsapp Integrations iOS Push Chat Integrations Vendor Fallback Tenant Vendor INTEGRATIONS Webhook Connectors Overview Mixpanel Segment Amazon S3 v2.0 Database MONITORING & DEBUGGING Logs Audit Logs Error Guides MANAGE YOUR ACCOUNT Authentication Methods Contact Us Get Started SuprSend, Notification infrastructure for Product teams home page Search... ⌘ K Ask AI Contact Us Get Started Get Started Search... Navigation Connectors Overview Documentation API Reference Management API CLI Reference Developer Resources Changelog Documentation API Reference Management API CLI Reference Developer Resources Changelog Connectors Overview OpenAI Open in ChatGPT Learn how to connect third-party platforms and data sources on SuprSend for data sync and workflow automation. OpenAI Open in ChatGPT With SuprSend Connectors, you can sync events, users, lists from third-party platforms into SuprSend or export SuprSend tracked logs and notification data to your data warehouse for reporting and analysis. Usecases of connectors Sync users and events from CDP platforms and setup notifications in a no-code manner If you already track customer data in these platforms, you can directly sync user data from these platforms within mins. Sync user cohorts from Analytics platform like Mixpanel and send notifications using SuprSend You can sync user cohorts from third-party platforms like Mixpanel in a list in SuprSend and trigger notifications via broadcast API . Update users and lists in SuprSend on 360 degree data from your data warehouse Connect your database to SuprSend and write SQL queries to sync users and lists in SuprSend. Sync notification logs and metrics to your data warehouse for reporting and analysis You can use Amazon S3 connector to export notification logs and metrics to your data warehouse for reporting and analysis. Connector Types There are 3 types of connectors in SuprSend: Third party data source Used to sync event and user data from a third-party platform to power notifications or sync user cohorts (lists) in SuprSend. Mixpanel Export user cohorts from Mixpanel into SuprSend and create subscriber lists to trigger notifications via broadcast API . Segment Sync users and events from Segment to SuprSend to power automated workflows, a low-code way to trigger notifications. Third party data destination Used to sync data like message templates and notification metrics that we track in SuprSend back to your data warehouse for reporting and analysis. Amazon S3 Export notification logs and metrics in your S3 bucket for internal or in-product reporting and analysis. Database Database connector enables you to setup notifications directly on top of the data from your data warehouse. This way data, product and growth teams can directly setup production notifications and automated marketing campaigns on the 360 degree data without doing any trade-offs on the amount of data available in click stream platforms. Using database connector, you can directly sync user profiles and create lists in SuprSend with a simple SQL query, without any engineering effort. You can then use these lists to send broadcasts. Postgres Sync user profiles and create lists in SuprSend on top of Postgres database. MySQL Sync user profiles and create lists in SuprSend on top of MySQL database. Bigquery Sync user profiles and create lists in SuprSend on top of BigQuery database. Need support for another connector? Please Let us know Add Connectors based on workspaces Most of these platforms have different project for staging and for production. Since each workspace in SuprSend has separate connector settings, you can connect your staging connector project to your staging workspace, and your production connector project to your production workspace. Was this page helpful? Yes No Suggest edits Raise issue Previous Mixpanel Guide to integrate Mixpanel with SuprSend for syncing user cohorts & triggering notifications using subscriber lists. Next ⌘ I x github linkedin youtube Powered by On this page Usecases of connectors Connector Types Third party data source Third party data destination Database Add Connectors based on workspaces | 2026-01-13T08:48:28 |
https://dev.to/t/linux/page/9 | Linux Page 9 - DEV Community Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account DEV Community Close Linux Follow Hide What are clouds made of? Linux servers, mostly. Create Post submission guidelines Articles and discussions should be directly related to Linux operating systems. Questions are encouraged (see the #help tag). Content with the main focus on bash or the Unix shell is permitted, but don't forget to add the #bash or #unix tag as you see it fitting. Articles mainly about WSL should be tagged with #wsl instead of #linux. about #linux Linux is a family of free and open source operating systems built on top of the Linux kernel, first released on 1991 by Linus Torvalds. Older #linux posts 6 7 8 9 10 11 12 13 14 Posts Left menu 👋 Sign in for the ability to sort posts by relevant , latest , or top . Right menu Step-by-Step Guide: Installing wrk (HTTP Benchmarking Tool) on Amazon Linux CloudGrains CloudGrains CloudGrains Follow Dec 13 '25 Step-by-Step Guide: Installing wrk (HTTP Benchmarking Tool) on Amazon Linux # aws # performance # tutorial # linux Comments Add Comment 2 min read DevOps From Scratch: Entry #02 Maame Afua A. P. Fordjour Maame Afua A. P. Fordjour Maame Afua A. P. Fordjour Follow Jan 3 DevOps From Scratch: Entry #02 # devops # linux # learning 19 reactions Comments Add Comment 6 min read Why MCP Servers Change Everything Pasindu Dewviman Pasindu Dewviman Pasindu Dewviman Follow Jan 5 Why MCP Servers Change Everything # cloud # mcp # backend # linux 2 reactions Comments 1 comment 3 min read Built an AI Terminal Assistant Because I Got Tired of Googling "Tar" Flags Pedro Dias Pedro Dias Pedro Dias Follow Dec 17 '25 Built an AI Terminal Assistant Because I Got Tired of Googling "Tar" Flags # devops # ai # productivity # linux Comments 1 comment 2 min read Vite + Antd App works on Windows but Single Page crashes on Linux Production (Minified React Error #130) Prashant Vaghela Prashant Vaghela Prashant Vaghela Follow Dec 13 '25 Vite + Antd App works on Windows but Single Page crashes on Linux Production (Minified React Error #130) # help # devops # linux # react Comments Add Comment 2 min read Sharing uid/gid between multiple Linux users Ky-Anh Huynh Ky-Anh Huynh Ky-Anh Huynh Follow Jan 5 Sharing uid/gid between multiple Linux users # linux Comments Add Comment 1 min read bash Query Filter Query Filter Query Filter Follow Dec 13 '25 bash # bash # cli # automation # linux Comments Add Comment 1 min read Remote SSH Access to Windows from Debian: Complete Setup and Fixes Siddharth Magesh Siddharth Magesh Siddharth Magesh Follow Dec 12 '25 Remote SSH Access to Windows from Debian: Complete Setup and Fixes # ssh # windows # linux # sysadmin Comments Add Comment 3 min read K9s Installation Script for Amazon Linux / RHEL-Based Systems- CloudGrains CloudGrains CloudGrains Follow Dec 12 '25 K9s Installation Script for Amazon Linux / RHEL-Based Systems- # bash # kubernetes # automation # linux Comments Add Comment 1 min read Is there a way to determine if a shared object ( .so ) file was generated from a c or c++ code? Prashant Sharma Prashant Sharma Prashant Sharma Follow Dec 11 '25 Is there a way to determine if a shared object ( .so ) file was generated from a c or c++ code? # cpp # linux # programming Comments Add Comment 3 min read Como corrigir o erro de GPG do repositório do Cursor no Linux Mint Brayan Monteiro Brayan Monteiro Brayan Monteiro Follow Dec 11 '25 Como corrigir o erro de GPG do repositório do Cursor no Linux Mint # cursor # linux # mint Comments Add Comment 2 min read FAR SYNC Data Guard Vahid Yousefzadeh Vahid Yousefzadeh Vahid Yousefzadeh Follow Dec 11 '25 FAR SYNC Data Guard # oracle # devops # linux # database Comments Add Comment 3 min read match Query Filter Query Filter Query Filter Follow Dec 12 '25 match # bash # cli # linux Comments Add Comment 1 min read Descubre Bluestar Linux: Un Sistema Operativo Versátil epubgratis epubgratis epubgratis Follow Dec 12 '25 Descubre Bluestar Linux: Un Sistema Operativo Versátil # archlinux # linux # opensource Comments Add Comment 1 min read Cortex-A SBCs vs. Traditional “Linux Boards”: A Practical Engineering Comparison jasonliu112 jasonliu112 jasonliu112 Follow Dec 11 '25 Cortex-A SBCs vs. Traditional “Linux Boards”: A Practical Engineering Comparison # sbcs # cortex # linux # boards Comments Add Comment 4 min read Advent of Embedded Linux — Day 4 Kanak Shilledar Kanak Shilledar Kanak Shilledar Follow Dec 11 '25 Advent of Embedded Linux — Day 4 # iot # linux # adventofcode # adventofembeddedlinux Comments Add Comment 1 min read Guía completa: Cómo instalé Jenkins X en un clúster K3s Cynthia Vázquez Cynthia Vázquez Cynthia Vázquez Follow Dec 10 '25 Guía completa: Cómo instalé Jenkins X en un clúster K3s # kubernetes # github # linux # jenkins Comments Add Comment 2 min read 🚀 Deploying MongoDB on Docker with Secure Host Directory Mounts Using ACLs (Without Changing Permissions) Ragul Ragul Ragul Follow Dec 10 '25 🚀 Deploying MongoDB on Docker with Secure Host Directory Mounts Using ACLs (Without Changing Permissions) # mongodb # docker # containers # linux Comments Add Comment 3 min read Windows - Instalando o WSL e o Docker Luis Cruz Luis Cruz Luis Cruz Follow Dec 10 '25 Windows - Instalando o WSL e o Docker # linux # microsoft # docker Comments Add Comment 3 min read Migrando desde VMware: Una comparación de las principales alternativas de hipervisores Agustin Ezequiel Acevedo Agustin Ezequiel Acevedo Agustin Ezequiel Acevedo Follow for Adini Jan 2 Migrando desde VMware: Una comparación de las principales alternativas de hipervisores # infrastructure # linux # learning # beginners Comments Add Comment 3 min read parallel2 Query Filter Query Filter Query Filter Follow Dec 10 '25 parallel2 # bash # performance # automation # linux Comments Add Comment 1 min read Shrinking a VirtualBox disk Paul Cochrane 🇪🇺 Paul Cochrane 🇪🇺 Paul Cochrane 🇪🇺 Follow Dec 11 '25 Shrinking a VirtualBox disk # devops # vagrant # virtualbox # linux Comments Add Comment 10 min read parallel Query Filter Query Filter Query Filter Follow Dec 10 '25 parallel # bash # performance # automation # linux Comments Add Comment 1 min read Linux history Precious Chisom Precious Chisom Precious Chisom Follow Dec 9 '25 Linux history # computerscience # linux # opensource Comments Add Comment 6 min read Free Up Storage on Linux: ncdu, APT Cleanup, Log Rotation, and Kernel Removal Explained Payam Hoseini Payam Hoseini Payam Hoseini Follow Dec 9 '25 Free Up Storage on Linux: ncdu, APT Cleanup, Log Rotation, and Kernel Removal Explained # tooling # performance # linux # tutorial Comments Add Comment 6 min read loading... 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV DEV Community — A space to discuss and keep up software development and manage your software career Home DEV++ Podcasts Videos DEV Education Tracks DEV Challenges DEV Help Advertise on DEV DEV Showcase About Contact Free Postgres Database Software comparisons Forem Shop Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . DEV Community © 2016 - 2026. We're a place where coders share, stay up-to-date and grow their careers. Log in Create account | 2026-01-13T08:48:28 |
https://www.linkedin.com/legal/l/cookie-table | Cookie Table Skip to main content Join now Sign in LinkedIn Cookie Table Last Updated: June 9, 2025 We use different types of cookies to collect and use data as part of our Services. We use two types of cookies: persistent cookies and session cookies. A persistent cookie lasts beyond the current session and will stay on your browser until they expire or you delete them. Session cookies last only as long as the session (usually the current visit to a website or a browser session). Third parties, such as our customers, partners and service providers may also use cookies in connection with our Services. Please take a look at our Cookie Policy if you’d like more information on how and why we and third parties use cookies. You can also find more information in our Privacy Policy, including information about how we process data collected through cookies. These tables list some of the cookies that we and third parties place. In addition to cookies strictly required for providing our services, they include information about the cookies that LinkedIn uses on third party sites including when LinkedIn’s Insight Tag is installed on our customers sites. The tables also provide information about the cookies that third parties may use to help us to provide our Services. Since the number and names of cookies may change, these tables may be updated from time to time to provide you with the latest information. The expiration dates for the cookies listed below generally apply on a rolling basis. Authentication Security Preferences/Features/Services Cookies LinkedIn drops on third party sites Personalized Advertising Analytics and Research Functional Authentication Purpose: Authentication Cookie Name Domain Purpose Expiration Provider li_at .www.linkedin.com Used to authenticate Members and API clients 1 year LinkedIn liap .linkedin.com Used by non-www.domains to denote the logged in status of a member 1 year LinkedIn leadgen.api_session forms.linkedin.com Stores client ID for Leadgen applications Session LinkedIn transaction_state linkedin.com Used to redirect users accessing LinkedIn through third party apps for authorization Session LinkedIn lihc_auth_str .linkedin.com Used by LinkedIn HelpCenter Live Chat to store session information. Session LinkedIn lihc_auth_* .linkedin.com Used by LinkedIn HelpCenter Live Chat to store language and chat start timestamp. Example names of this cookie include lihc_auth_en, lihc_auth_es, depending on language preference. Session LinkedIn li_a .www.linkedin.com Used to authenticate enterprise users on Sales Navigator and Recruiter 30 days LinkedIn li_ep_auth_context .www.linkediin.com User to authenticate LinkedIn enterprise customers 1 year LinkedIn sj_sessionid training.talent.linkedin.com training.marketing.linkedin.com training.sales.linkedin.com When visiting a page with tutorial functionality provided by Skilljar, this cookie maintains a logged-in state for the user across multiple pages. Skilljar tutorial functionality is only provided to users who explicitly consent to receive such functionality. 14 days Skilljar cp_session help.linkedin.com This cookie is set to authenticate users into LinkedIn's instance of Oracle Service Cloud which is used by LinkedIn's Help Center. Session Oracle G_AUTHUSER_H .www.linkedin.com Used by Google Single Sign On to identify if a user is logged into Google on their browser. Session Google G_ENABLED_IDPS .www.linkedin.com Used by Google Single Sign On. 2 years Google g_state .www.linkedin.com Stores the timestamp for the purpose of honoring the cool off period and dismiss count for Google's one tap prompt feature. 180 days Google x-ms-cpim-cache|<id> enterpriselogin.linkedin.com Used for maintaining the request state for Azure Active Directory B2C Session Microsoft x-ms-cpim-trans enterpriselogin.linkedin.com Used for tracking the transaction (number of authentication requests to Azure Active Directory B2C) and the current transaction. Session Microsoft x-ms-cpim-sso:linkedinenterprise.onmicrosoft.com_0 enterpriselogin.linkedin.com Used for maintaining SSO sessions for Azure Active Directory B2C Session Microsoft remember_me scommunity.linkedin.com,tcommunity.linkedin.com Used to permit user log-in 1 month Gainsight _s_attr tcommunity.linkedin.com, scommunity.linkedin.com Used in the LinkedIn login integration and logged through user logs for login related information 5 min Gainsight ANONCHK .c.office.com Used by Microsoft forms to identify the user completing a form and for diagnostic purposes Session Microsoft MR (Forms) .c.bing.com Used by Microsoft forms to decide whether to extend the lifetime of the MUID cookie for security and authentication purposes 7 days Microsoft logout-event tcommunity.linkedin.com, scommunity.linkedin.com Used to determine the time or occurrence of a logout action Session LinkedIn Security Purpose: Security Cookie Name Domain Purpose Expiration Service Provider fid linkedin.com Used to track malicious activity on the site 7 days LinkedIn bcookie linkedin.com Browser Identifier cookie to uniquely identify devices accessing LinkedIn to detect abuse on the platform 1 year LinkedIn bscookie .www.linkedin.com Used for remembering that a logged in user is verified by two factor authentication and has previously logged in 1 year LinkedIn fcookie linkedin.com Used for bot detection. 7 days LinkedIn ccookie linkedin.com To remember if a user received a captcha challenge. 20 minutes LinkedIn JSESSIONID .www.linkedin.com Used for Cross Site Request Forgery (CSRF) protection and URL signature validation. Session LinkedIn chp_token .www.linkedin.com Used to denote whether the user has gone through two factor authentication or solved a Captcha. Session LinkedIn li_cu .linkedin.com Used to map a user to a captcha challenge page 15 minutes LinkedIn cf_ob_info Multiple Cloudflare Proxied Domains Used by Cloudflare to track the request path and status through Cloudflare network to end servers for security purposes 3 days Cloudflare cf_use_ob Multiple Cloudflare Proxied Domains Used by Cloudflare in the event servers are down, for showing a cached version of any requested web page 3 days Cloudflare cfuid Multiple Cloudflare Proxied Domains Used to detect potential malicious visitors to Cloudfare proxied sites 30 days Cloudflare __cfruid Multiple Cloudflare Proxied Domains Used by Cloudflare for rate limiting Session Cloudflare __cf_bm Multiple Cloudflare Proxied Domains Bot detection provided by Cloudflare 30 minutes Cloudflare denial-client-ip www.linkedin.com Stores user IP address for anti-scraping and DOS prevention 5 seconds LinkedIn denial-reason-code www.linkedin.com Used for anti-scraping and DOS prevention 5 seconds LinkedIn rtc www.linkedin.com Used as part of anti-abuse processes on LinkedIn 120 seconds LinkedIn trkInfo www.linkedin.com Threat analysis and de-bugging used as part of anti-abuse processes on LinkedIn 5 seconds LinkedIn trkCode www.linkedin.com Used as part of anti-abuse processes on LinkedIn 5 seconds LinkedIn spectroscopyId www.linkedin.com Used to catch malicious activity through browser extensions Session LinkedIn fptctx2 .linkedin.com Used to prevent abuse in payment workflows for LinkedIn Session Microsoft dfpfpt .linkedin.com Unique user identifier to prevent abuse in payment workflows for LinkedIn 2 years Microsoft li_referer .linkedin.com Used to detect bots. Cookie remembers the referring website before redirecting the user to captcha for authorization 15 minutes LinkedIn f_token .linkedin.com Used to detect bots for anti-scraping 3 minutes LinkedIn __ssid linkedin.com Used to prevent fraud and abuse in payment flows 10 years SIFT sj_csrftoken training.talent.linkedin.com, training.sales.linkedin.com, training.marketing.linkedin.com, peopleacademy.glintinc.com, glint-people-academy.skilljar.com, accounts.skilljar.com Required to validate requests from the user's browser and prevent cross-subdomain attacks. 1 year Skilljar x-ms-cpim-csrf enterpriselogin.linkedin.com To prevent Cross Site Request Forgery (CSRF) attacks, Azure Active Directory B2C applies the Synchronizer Token strategy mechnism via this cookie Session Microsoft thx_global_guid h.online-metrix.net Used to prevent fraud on Social Impact microsite 5 years ThreatMetrix thx_guid content.sheerid.com Used to prevent fraud on Social Impact microsite 5 years ThreatMetrix tmx_guid content.sheerid.com Used to prevent fraud on Social Impact microsite 5 years ThreatMetrix _cfuvid .arkoselabs.com Used to allow web application firewall to block malicious traffic Session Arkose Labs _pxvid protechts.net Used for bot detection for abuse prevention 1 year HUMAN Security _pxmvid protechts.net Used for bot detection for abuse prevention 6 hours HUMAN Security _pxhd protechts.net Used for bot detection for abuse prevention 1 year HUMAN Security _pxde protechts.net Used for bot detection for abuse prevention 5 days HUMAN Security pxcts protechts.net Used for bot detection for abuse prevention 1 year HUMAN Security _px{id} protechts.net Used for bot detection for abuse prevention 14 days HUMAN Security _pxff_{id} protechts.net Used for bot detection for abuse prevention 24 hours HUMAN Security _RequestVerificationToken forms.cloud.microsoft Anti-forgery cookie set by web applications built using ASP.NET MVC technologies Session ASP.NET MVC technologies _pxttld protechts.net Determines the appropriate domain settings for cookies to enable site-wide detection functionality by third party scripts 14 days HUMAN Security SRM_B .c.bing.com Used by Microsoft Forms for security purposes 1 year Microsoft li_bapfcc linkedin.com Used to control the number of abuse prevention features collected from member device. 2 years LinkedIn li_apfcdc linkedin.com Used for triggering the abuse prevention features on member device. 10 hours LinkedIn li_odapfcc linkedin.com Used to control the number of abuse prevention features collected from member device. 2 years LinkedIn _GRECAPTCHA google.com Used for bot detection for abuse prevention. LinkedIn's services are protected by reCAPTCHA. Google's Privacy Policy and Terms of Service apply 6 months Google Google ReCAPTCHA google.com Used for bot detection for abuse prevention. LinkedIn's services are protected by reCAPTCHA. Google's Privacy Policy and Terms of Service apply N/A Google Preferences/Features/Services Preferences, Features, Services Cookie Name Domain Purpose Expiration Provider bcookie .linkedin.com Browser Identifier cookie used for diagnostic purposes. 1 year LinkedIn li_rm .www.linkedin.com Used as part of LinkedIn's Remember Me Feature and is set when a user clicks "Remember me" on their device to make logging in on that device easier 1 year LinkedIn BizographicsOptOut .linkedin.com Used to determine opt-out status for non-members 10 years LinkedIn ac_L linkedin.com Counts the number of times the account center banner, which is displayed to inform users with an incomplete profile how to complete their profile, was closed by a user to determine display logic 180 days LinkedIn ac_LD linkedin.com Contains the date when the account center was displayed to a user to determine display logic 180 days LinkedIn recent_history_status .linkedin.com Used to determine whether a user enabled or disabled the Guest Recent History Setting 10 years LinkedIn all_u_b www.linkedin.com To know if a user has opted in to viewing LinkedIn on an unsupported browser 21 days LinkedIn lang .linkedin.com Used to remember a user's language setting to ensure LinkedIn.com displays in the language selected by the user in their settings. Session LinkedIn uh www.linkedin.com Used to set the user preference for the mobile web platform via a user's settings Session LinkedIn pushPermInfo www.linkedin.com Used across multiple LinkedIn services to determine cool off for push notification prompts 365 days LinkedIn pushPermState www.linkedin.com Used across multiple LinkedIn services to determine the user's push notification permission preference 30 days LinkedIn lidc .linkedin.com To facilitate data center selection 24 hours LinkedIn wwepo .www.linkedin.com Used to ensure that useres who choose to sign up using phone only have that setting and preference respected 90 days LinkedIn sdsc linkedin.com Signed data service context cookie used for database routing to ensure consistency across all databases when a change is made. Used to ensure that user-inputted content is immediately available to the submitting user upon submission. Session LinkedIn li_gc .linkedin.com Used to store consent of guests regarding the use of cookies for non-essential purposes 6 months LinkedIn li_mc .linkedin.com Used as a temporary cache to avoid database lookups for a member's consent for use of non-essential cookies and used for having consent information on the client side to enforce consent on the client side 6 months LinkedIn li_ec .linkedin.com Used to store unbound enterprise users' cookie consent 6 months LinkedIn li_gpc .linkedin.com Used to remember a user's preferences on LinkedIn's Global Privacy Control 1 hour LinkedIn li_gp .linkedin.com Stores privacy preferences for guests to LinkedIn 1 year LinkedIn PLAY_FLASH www.linkedin.com Used by some LinkedIn services to facilitate the display of messages on page transitions . Users include notifying a user when a form is successfully submitted or fails , and to provide other similar notifications. Session LinkedIn PLAY_LANG www.linkedin.com Used by some LinkedIn services to remember a user's language preference Session LinkedIn PLAY_SESSION www.linkedin.com Used by some LinkedIn services to store session information Session LinkedIn visit linkedin.com To determine whether to take a non-authenticated user to the registration page or the login page 1 year LinkedIn redirectFromM2MInviteAccept www.linkedin.com Determines the appropriate profile display logic when a user accepts an invitation to connect on LinkedIn from a LinkedIn member via email. Session LinkedIn redirectFromM2MInviteSent www.linkedin.com Used to notify and provide the appropriate profile display logic when the user sends an invitation to connect on LinkedIn from a LinkedIn member via email. Session LinkedIn cookie.policy.banner.eu www.linkedin.com Used to display cookie banner in LinkedIn Lite 365 days LinkedIn cookie.policy.banner.nl www.linkedin.com Used to display cookie banner in LinkedIn Lite on the Netherlands site. 365 days LinkedIn appName www.linkedin.com Used to identify the source as the LinkedIn Lite app to send the right service worker to the app Session LinkedIn appLang www.linkedin.com Used to set the right language on the LinkedIn Lite app Session LinkedIn lls-integration www.linkedin.com Validates whitelisted partners for content integrations 30 days Linkedin feed-sort www.linkedin.com Used to remember a member's preference how the feed should be sorted 1 day LinkedIn abiRedirect .linkedin.com Enables import of address book during onboarding flow for users who choose to import their address book Session LinkedIn timezone .linkedin.com Used to determine user's timezone 14 days LinkedIn lil-lang www.linkedin.com Stores user's selected language setting for LinkedIn Learning Session LinkedIn sj_ubid training.talent.linkedin.com training.marketing.linkedin.com training.sales.linkedin.com Used for debugging across multiple browsers when visiting a page with tutorial functionality provided by Skilljar 20 years Skilljar li_alerts .linkedin.com Used to track impressions of LinkedIn alerts, such as the Cookie Banner and to implement cool off periods for display of alerts 1 year LinkedIn li_theme .linkedin.com Remembers a user's display preference/theme setting 6 months LinkedIn integration_type www.linkedin.com Used to determine which integration traffic is coming from to render the profile namecard experience 30 days LinkedIn li_theme_set linkedin.com Remembers which users have updated their display / theme preferences 6 months LinkedIn sj_lp .linkedin.com Remembers a user's localization preference so the correct language is displayed 1 year Skilljar li_er .linkedin.com Used to keep enterprise data center routing context for the selected contract 8 hours LinkedIn cap_force_desktop .linkedin.com To force the desktop site of Recruiter for a mobile user Session LinkedIn cap_session_id .linkedin.com Used to ensure incoming requests are coming from the same browser associated with an enterprise account, to prevent seat sharing 30 days LinkedIn u_tz .linkedin.com Used for storing timezone in Recruiter 30 days LinkedIn _cap_profile .linkedin.com Used to store contract type in Recruiter 30 days LinkedIn AWSALBCORS services.sheerid.com Used by SheerID forms to route requests for a. particular session to the target hosts of the application. 7 days SheerID li_ce www.linkedin.com Used to allow enterprise users in China to access enterprise features on linkedin.com 7 days LinkedIn li_g_recent_logout .linkedin.com Used to support Google Auto-Login on guest pages for users who have enabled this feature 60 minutes LinkedIn li_g_view .linkedin.com Used to count guest views before prompting a login page 30 days LinkedIn auth_content_wp .linkedin.com; .glintinc.com; .skilljar.com Used by Skilljar to authenticate requests for specific content files to serve SCORM content Session Skilljar cloudfront-key-pair-id .linkedin.com; .glintinc.com; .skilljar.com Used by Cloudfront CDN to control access to SCORM course content requested by the user Session Skilljar/Cloudfront cloudfront-policy .linkedin.com; .glintinc.com; .skilljar.com Used by Cloudfront CDN to control access to SCORM course content requested by the user Session Skilljar/Cloudfront cloudfront-signature .linkedin.com; .glintinc.com; .skilljar.com Used by Cloudfront CDN to control access to SCORM course content requested by the user Session Skilljar/Cloudfront X-Salesforce-CHAT .linkedin.com; salesforceliveagent.com Set by the load balancer to store which server the user was interacting with to enable live chat services requested by the user Session Salesforce Liveagent Session .scommunity.linkedin.com, tcommunity.linkedin.com Used to store user preferences on Community Websites Session Gainsight x-ms-cpim-geo enterpriselogin.linkedin.com Used as a hint for Azure gateways to route subsequent request of the user to the correct tenant 60 minutes Microsoft topics scommunity.linkedin.com, tcommunity.linkedin.com Used to identify the numerical IDs of the topics visited by the user. 2 days Gainsight lastactivity scommunity.linkedin.com, tcommunity.linkedin.com Timestamp cookie used to ensure up to date content is displayed to user. 6 months Gainsight MUID (Forms) forms.cloud.microsoft Microsoft Forms uses this cookie for the purpose of counting unique visitors to a form 1 year Microsoft Forms shownNudgeCount linkedin.com Implements a cool off period to avoid multiple nudges on updates 1 day LinkedIn SM .c.office.com Used on Microsoft Forms to identify whether the MUID cookie is newly issued or not. Session Microsoft MUID (.office.com) .office.com Counts unique users to a Microsoft Form 1 year Microsoft sdui_ver .linkedin.com Used to ensure users' browsers continue using a supported version of the service to maintain consistent performance during updates 24h LinkedIn sj_cookiesenabled training.talent.linkedin.com, training.sales.linkedin.com, training.marketing.linkedin.com Used to check if cookies are enabled in the browser to optimize how content is displayed Session Skilljar _cb tcommunity.linkedin.com, scommunity.linkedin.com Supports secure access to our Customer Communities by ensuring logged-in users receive uncached, up-to-date content 180 days Gainsight _locale tcommunity.linkedin.com, scommunity.linkedin.com Stores users' language and region preferences so relevant content is displayed 1 year Gainsight Cookies LinkedIn drops on third party sites LinkedIn enables third party sites to include some of its services such as Insight Tag, post embeds, Apply with LinkedIn and Sign In with LinkedIn. These services use a subset of cookies listed in the following table. Cookies LinkedIn drops on third party sites Cookie Name Domain Purpose Expiration Provider bcookie .linkedin.com Browser Identifier cookie to uniquely indentify devices accessing LinkedIn to detect abuse on the platform and diagnostic purposes 1 year LinkedIn bscookie .www.linkedin.com Used for remembering that a logged in user is verified by two factor authentication and has previously logged in 1 year LinkedIn JSESSIONID .www.linkedin.com Used for Cross Site Request Forgery (CSRF) protection and URL signature validation Session LinkedIn lang .linkedin.com Used to remember a user's language setting to ensure LinkedIn.com displays in the language selected by the user in their settings Session LinkedIn lidc .linkedin.com To facilitate data center selection 24 hours LinkedIn sdsc .linkedin.com Signed data service context cookie used for database routing to ensure consistency across all databases when a change is made. Used to ensure that user-inputted content is immediately available to the submitting user upon submission Session LinkedIn li_gc .linkedin.com Used to store consent of guests regarding the use of cookies for non-essential purposes 6 months LinkedIn li_mc .linkedin.com Used as a temporary cache to avoid database lookups for a member's consent for use of non-essential cookies and used for having consent information on the client side to enforce consent on the client side 6 months LinkedIn UID scorecardresearch.com Cookie used for market and user research 720 days Scorecard research UserMatchHistory linkedin.com LinkedIn Ads ID syncing 30 days LinkedIn AnalyticsSyncHistory .linkedin.com Used to store information about the time a sync took place with the lms_analytics cookie 30 days LinkedIn lms_ads .linkedin.com Used to identify LinkedIn Members off LinkedIn for advertising 30 days LinkedIn lms_analytics .linkedin.com Used to identify LinkedIn Members off LinkedIn for analytics 30 days LinkedIn li_fat_id Various, first party domain Member indirect identifier for Members for conversion tracking, retargeting, analytics 30 days LinkedIn li_sugr .linkedin.com Used to make a probabilistic match of a user's identity 90 days LinkedIn _guid linkedin.com Used to identify a LinkedIn Member for advertising through Google Ads 90 days LinkedIn BizographicsOptOut .linkedin.com Used to determine opt-out status for non-members 10 years LinkedIn li_giant Various, first-party domain Indirect indentifier for groups of LinkedIn Members used for conversion tracking 7 days LinkedIn oribi_cookie_test Various, first-party domain To determine if tracking can be enabled on current domain Session Oribi oribili_user_guid Various, first-party domain Used to count unique visitors to a website 1 year Oribi ln_or Various, first-party domain Used to determine if Oribi analytics can be carried out on a specific domain 1 day Oribi ar_debug Various, first-party domain Supports Google attribution reporting API integration to mitigate signal loss Session LinkedIn Personalized Advertising Purpose: Personalized Advertising Cookie Name Domain Purpose Expiration Provider UserMatchHistory linkedin.com Used for id sync process. It stores the last sync time to avoid repeating the syncing process in a frequent manner 30 days LinkedIn lms_ads .linkedin.com Used to identify LinkedIn Members off LinkedIn for advertising 30 days LinkedIn li_sugr .linkedin.com Used to make a probabilistic match of a user's identity 90 days LinkedIn _guid linkedin.com Used to identify a LinkedIn Member for advertising through Google ads 90 days LinkedIn A3 .yahoo.com Ads targeting cookie for Yahoo 1 year Yahoo anj .adxns.com Ads targeting cookie for AppNexus 3 months Xandr uuid2 .adxns.com Used by ad nexus analytics by AppNexus 3 months Xandr usersync .adxns.com Used to determine if ID sync with Xandr has occurred 90 days Xandr icu .adxns.com Used to select and limit ads 90 days Xandr uids .adxns.com Used to select ads and measure ad performance 90 days Xandr dpm .dpm.demdex.net Sends events to Adobe Audience Manager 6 months Adobe dextp .demdex.net Records last time a data synchronization call was performed 6 months Adobe demdex .demdex.net Visitor identification 6 months Adobe dst .lnkd.demdex.net Logs when there is an error sending data to destination. Used as part of Adobe Audience Manager 6 months Adobe lnkd .lnkd.demdex.net Sends event to Adobe Audience Manager 6 months Adobe aam_uuid .linkedin.com, .linkedin.cn Set for ID sync for Adobe Audience Manager 6 months Adobe MUID .bing.com Bing Tracking 1 year Microsoft MR microsoft.com Bing Tracking 6 months Microsoft IDE .doubleclick.com Ads targeting cookie for DoubleClick 2 years Google fr .facebook.com Ads targeting cookie for Facebook 3 months Facebook personalization_id .twitter.com Ads targeting cookie for Twitter 2 years Twitter GUC yahoo.com Yahoo Conversion Tracking 5 months Yahoo B .yahoo.com Yahoo Conversion Tracking 1 year Yahoo test_cookie .doubleclick.net Test for cookie setting permissions in user's browser 1 day Google _gcl_au .linkedin.com Used to measure ad and campaign performance and conversion rates for Google ads on a site visited 3 months Google _gcl_aw .linkedin.com Used through Google Ads to understand user interaction with the site and advertising 3 months Google _gcl_dc .linkedin.com Used through Google Campaign Manager and DV 360 to understand user interaction with the site and advertising 3 months Google brwsr LinkedIn Tracking Domain Affiliate Marketing Cookie for LinkedIn 2 years LinkedIn ABSELB LinkedIn Tracking Domain Load Balancer Cookie for affiliate marketing 2 years LinkedIn IRLD LinkedIn Tracking Domain Affiliate Marketing Cookie for LinkedIn 2 years LinkedIn barometric[cuid] trkn.us Used for Veritone/Barometric Podcast Conversion tracking on both linkedin.com (product) and microsites (business.linkedin.com) 1 year Claritas tluid .3lift.com Used to uniquely identify users across webpages for advertising purposes 90 days TripleLift oribi_cookie_test linkedin.com To determine if tracking can be enabled on a current domain Session Oribi oribili_user_guid .oribi.io, oribi.io Used to count unique visitors to a website 1 year Oribi uids .rubiconproject.com Browser ID for advertising purposes. Session Magnite l_page .linkedin.com Used for measuring conversion metrics on LinkedIn 6 months LinkedIn _rdt_uuid .linkedin.com Used to attribute conversions back to Reddit Ads Session Reddit uid-bp-41393 ads.stickyadstv.com Used to determine whether a cookie ID syncs with LinkedIn's partners 60 days FreeWheel _uid ads.stickyadstv.com Used to determine whether a cookie ID syncs with FreeWheel partners 60 days FreeWheel ar_debug N/A Supports Google attribution reporting API integration to mitigate signal loss Session LinkedIn tluidp .3lift.com Used to uniquely identify users across webpages for advertising purposes 90 days TripleLift 33x_ps .33across.com Used to determine whether a cookie ID syncs with 33across partners 1 year 33across 33x_b .33across.com Used to determine whether a cookie ID syncs with 33across partners 1 year 33across receive-cookie-deprecation .rubiconproject.com Used to determine whether a cookie ID syncs with Rubicon partners 60 days Rubicon khaos_p .rubiconproject.com Used to determine whether a cookie ID syncs with Rubicon partners 1 year Rubicon khaos .rubiconproject.com Used to determine whether a cookie ID syncs with Rubicon partners 1 year Rubicon audit_p .rubiconproject.com Used to determine whether a cookie ID syncs with Rubicon partners 1 year Rubicon audit .rubiconproject.com Used to determine whether a cookie ID syncs with Rubicon partners 1 year Rubicon tt_viewer .teads.tv Used to determine whether a cookie ID syncs with Teads partners 60 days Teads UID ("ads.stickyadstv.com") .ads.stickyadstv.com Used to determine whether a cookie ID syncs with FreeWheel partners 60 days FreeWheel barometric[idfa] http://trkn.us/ Used for Claritas/Veritone/Barometric podcast conversions tracking 37 days Claritas Analytics and Research Purpose: Analytics and Research Cookie Name Domain Purpose Expiration Provider lms_analytics .linkedin.com Used to identify LinkedIn Members off LinkedIn for analytics 30 days LinkedIn AnalyticsSyncHistory .linkedin.com Used to store information about the time a sync took place with the lms_analytics cookie 30 days LinkedIn queryString Any LinkedIn microsite This cookie is used to persist marketing tracking parameters 15 days LinkedIn SID .linkedin.com Used to determine what a visitor is doing before they convert on a LinkedIn microsite Session LinkedIn VID .linkedin.com ID associated with a visitor to a LinkedIn microsite which is used to determine conversions for lead gen purposes 1 year LinkedIn UID .scorecardresearch.com Cookie used for market and user research 720 days Scorecard Research UIDR .scorecardresearch.com Cookie used for market and user research 720 days Scorecard Research AMCVS_14215E3D5995 C57C0A495C55%40Adob eOrg .linkedin.com Indicates the start of a session for Adobe Experience Cloud Session Adobe AMCV_14215E3D5995C5 7C0A495C55%40AdobeO rg .linkedin.com Unique Identifier for Adobe Experience Cloud 180 days Adobe s_cc .linkedin.com Used to determine if cookies are enabled for Adobe Analytics Session Adobe s_sq .linkedin.com Used to store information about the previous link that was clicked on by the user by Adobe Analytics Session Adobe s_vi .omtrdc.net Unique identifier for Adobe Analytics 2 years Adobe s_fid .linkedin.com Unique identifier for Adobe Analytics 180 days Adobe ki_r .qualaroo.com Stores the initial page referrer when available for targeting purposes 5 years Qualaroo ki_s .qualaroo.com Stores the current state of any survey the user has viewed or interacted with 5 years Qualaroo ki_t .qualaroo.com Stores the survey timestamps and view counts 5 years Qualaroo ki_u .qualaroo.com Stores a random UID to associate with survey responses 5 years Qualaroo gpv_pn .linkedin.com Used to retain and fetch previous page visited in Adobe Analytics 6 months Adobe s_plt .linkedin.com Tracks the time that the previous page took to load Session Adobe s_tslv .linkedin.com Used to retain and fetch time since last visit in Adobe Analytics 6 months Adobe s_ppv .linkedin.com Used by Adobe Analytics to retain and fetch what percentage of a page was viewed Session Adobe s_pltp .linkedin.com Provides page name value (URL) for use by Adobe Analytics Session Adobe s_ips .linkedin.com Tracks percent of page viewed Session Adobe s_tp .linkedin.com Tracks percent of page viewed Session Adobe oribi_cookie_test linkedin.com To determine if tracking can be enabled on current domain Session Oribi oribili_user_guid .oribi.io, oribi.io Used to count unique visitors to a website 1 year Oribi ln_or .linkedin.com Used to determine if Oribi analytics can be carried out on a specific domain 1 day Oribi QSIPopUnder_PopUnderTarget_SI_<id> .linkedin.com Tracks whether or not a popunder has already been deployed in the user's browser session so that another is not deployed Session Qualtrics QSI_HistorySession .linkedin.com Qualtrics session cookie which stores what pages a visitor has visited for the current session Session Qualtrics QSI_SI_<id>_intercept .linkedin.com Used to determine whether or not we should display a survey on repeated user visits within a period 30 days Qualtrics QSI_S_<ZoneID> .linkedin.com Used to track visits and sampling rate set in the survey 7 days Qualtrics QST .linkedin.com Used to prevent multiple survey responses 180 days Qualtrics PageReferrer .linkedin.com Used to identify which page referred to the survey page Session Qualtrics ActionSetHistory .linkedin.com Used to identify time the survey action set was last seen Session Qualtrics FocusTime .linkedin.com Used to identify how long a user has been viewing the survey page Session Qualtrics SearchTerm .linkedin.com Used to identify which search term led to the survey page (Google, Yahoo, or Bing) Session Qualtrics SiteReferrer .linkedin.com Used to identify which site referred to the survey page Session Qualtrics gdpr .id5-sync.com Used to evaluate performance of id synchronization 90 days ID5 cnac .id5-sync.com Used to evaluate performance of id synchronization 90 days ID5 cip .id5-sync.com Used to evaluate performance of id synchronization 90 days ID5 cf .id5-sync.com Used to evaluate performance of id synchronization 90 days ID5 car .id5-sync.com Used to evaluate performance of id synchronization 90 days ID5 callback .id5-sync.com Used to evaluate performance of id synchronization 90 days ID5 _clck .linkedin.com Used for Microsoft Clarity analytical purposes 1 year Microsoft _clsk .linkedin.com Used for Microsoft Clarity analytical purposes Session Microsoft _ga .linkedin.com Google Analytics Cookie used to distinguish users [for trial period in US only] 2 years LinkedIn _ga_T1C4ZK6V3H .linkedin.com Used to persist session state [for trial period in US only] 2 years LinkedIn Functional Purpose: Functional Cookie Name Domain Purpose Expiration Provider recent_history .linkedin.com Used to remember URLs visited by the guest to show the pages back where they left off 90 days LinkedIn liveagent_chatted .linkedin.com Used to enable live chat functionality 10 years Salesforce liveagent_oref .linkedin.com Used to enable live chat functionality 10 years Salesforce liveagent_ptid .linkedin.com Used to enable live chat functionality 10 years Salesforce liveagent_sid .linkedin.com Used to enable live chat functionality Session Salesforce liveagent_vc .linkedin.com Used to enable live chat functionality 10 years Salesforce NID .google.com Used by Google to store user preferences 6 months Google sharebox-suggestion www.linkedin.com Displays a banner that provides help text to first time users of the Elevate share box Session LinkedIn at_check .linkedin.com Used to determine if a visitor has accepted the use of cookies for Adobe Target Session Adobe mbox .linkedin.com Used by Adobe Target to analyze the relevance of online content 180 days Adobe li_cc www.linkedin.com Used to ensure a user's phone number is inputted in China 1 week LinkedIn lss_bundle_viewer .linkedin.com Stores consent when a user agrees to view a Smartlinks link 1 month LinkedIn interstitial_page_reg_oauth_url www.linkedin.com Stores the referring page to ensure the Authentication screen displays correctly 1 day LinkedIn t scommunity.linkedin.com, tcommunity.linkedin.com Used for accurately tracking user actions and activities in session for user experience purposes 1 year Gainsight tu scommunity.linkedin.com, tcommunity.linkedin.com Used for accurately tracking user actions and activities in session for user experience purposes 1 year Gainsight new_visit scommunity.linkedin.com, tcommunity.linkedin.com Used to present first time user screen to new users 30 minutes Gainsight FormsWebSessionId forms.cloud.microsoft Saves login data for a Microsoft forms session and tracks data necessary to run the service 61 days Microsoft Forms MC1 .microsoft.com Long term session identification cookie for Microsoft forms 1 year Microsoft Forms MS0 .microsoft.com Short term session identification cookie for Microsoft forms 30 mins Microsoft Forms df_ts linkedin.com Device fingerprinting sampling for performance optimization 1 day LinkedIn li_feed_xray linkedin.com Used to show new items in developer option 'Feed X-ray' Session LinkedIn edge_gateway linkedin.com Used to determine relevant endpoint 5 minutes LinkedIn LinkedIn © 2026 About Accessibility User Agreement Privacy Policy Cookie Policy Copyright Policy Brand Policy Guest Controls Community Guidelines العربية (Arabic) বাংলা (Bangla) Čeština (Czech) Dansk (Danish) Deutsch (German) Ελληνικά (Greek) English (English) Español (Spanish) فارسی (Persian) Suomi (Finnish) Français (French) हिंदी (Hindi) Magyar (Hungarian) Bahasa Indonesia (Indonesian) Italiano (Italian) עברית (Hebrew) 日本語 (Japanese) 한국어 (Korean) मराठी (Marathi) Bahasa Malaysia (Malay) Nederlands (Dutch) Norsk (Norwegian) ਪੰਜਾਬੀ (Punjabi) Polski (Polish) Português (Portuguese) Română (Romanian) Русский (Russian) Svenska (Swedish) తెలుగు (Telugu) ภาษาไทย (Thai) Tagalog (Tagalog) Türkçe (Turkish) Українська (Ukrainian) Tiếng Việt (Vietnamese) 简体中文 (Chinese (Simplified)) 正體中文 (Chinese (Traditional)) Language | 2026-01-13T08:48:28 |
https://www.linkedin.com/legal/cookie-policy?trk=registration_footer-cookie-policy | Cookie Policy | LinkedIn Skip to main content User Agreement Summary of User Agreement Privacy Policy Professional Community Policies Cookie Policy Copyright Policy Regional Info EU Notice California Privacy Disclosure U.S. State Privacy Laws User Agreement Summary of User Agreement Privacy Policy Professional Community Policies Cookie Policy Copyright Policy Regional Info EU Notice California Privacy Disclosure U.S. State Privacy Laws Cookie Policy Effective on June 3, 2022 At LinkedIn, we believe in being clear and open about how we collect and use data related to you. This Cookie Policy applies to any LinkedIn product or service that links to this policy or incorporates it by reference. We use cookies and similar technologies such as pixels, local storage and mobile ad IDs (collectively referred to in this policy as “cookies”) to collect and use data as part of our Services, as defined in our Privacy Policy (“Services”) and which includes our sites, communications, mobile applications and off-site Services, such as our ad services and the “Apply with LinkedIn” and “Share with LinkedIn” plugins or tags. In the spirit of transparency, this policy provides detailed information about how and when we use these technologies. By continuing to visit or use our Services, you are agreeing to the use of cookies and similar technologies for the purposes described in this policy. What technologies are used? ENTER A SUMMARY Type of technology Description Cookies A cookie is a small file placed onto your device that enables LinkedIn features and functionality. Any browser visiting our sites may receive cookies from us or cookies from third parties such as our customers, partners or service providers. We or third parties may also place cookies in your browser when you visit non-LinkedIn sites that display ads or that host our plugins or tags . We use two types of cookies: persistent cookies and session cookies. A persistent cookie lasts beyond the current session and is used for many purposes, such as recognizing you as an existing user, so it’s easier to return to LinkedIn and interact with our Services without signing in again. Since a persistent cookie stays in your browser, it will be read by LinkedIn when you return to one of our sites or visit a third party site that uses our Services. Session cookies last only as long as the session (usually the current visit to a website or a browser session). Pixels A pixel is a tiny image that may be embedded within web pages and emails, requiring a call (which provides device and visit information) to our servers in order for the pixel to be rendered in those web pages and emails. We use pixels to learn more about your interactions with email content or web content, such as whether you interacted with ads or posts. Pixels can also enable us and third parties to place cookies on your browser. Local storage Local storage enables a website or application to store information locally on your device(s). Local storage may be used to improve the LinkedIn experience, for example, by enabling features, remembering your preferences and speeding up site functionality. Other similar technologies We also use other tracking technologies, such as mobile advertising IDs and tags for similar purposes as described in this Cookie Policy. References to similar technologies in this policy includes pixels, local storage, and other tracking technologies. Our cookie tables lists cookies and similar technologies that are used as part of our Services. Please note that the names of cookies and similar technologies may change over time. What are these technologies used for? Below we describe the purposes for which we use these technologies. ENTER SUMMARY Purpose Description Authentication We use cookies and similar technologies to recognize you when you visit our Services. If you’re signed into LinkedIn, these technologies help us show you the right information and personalize your experience in line with your settings. For example, cookies enable LinkedIn to identify you and verify your account. Security We use cookies and similar technologies to make your interactions with our Services faster and more secure. For example, we use cookies to enable and support our security features, keep your account safe and to help us detect malicious activity and violations of our User Agreement. Preferences, features and services We use cookies and similar technologies to enable the functionality of our Services, such as helping you to fill out forms on our Services more easily and providing you with features, insights and customized content in conjunction with our plugins. We also use these technologies to remember information about your browser and your preferences. For example, cookies can tell us which language you prefer and what your communications preferences are. We may also use local storage to speed up site functionality. Customized content We use cookies and similar technologies to customize your experience on our Services. For example, we may use cookies to remember previous searches so that when you return to our services, we can offer additional information that relates to your previous search. Plugins on and off LinkedIn We use cookies and similar technologies to enable LinkedIn plugins both on and off the LinkedIn sites. For example, our plugins, including the "Apply with LinkedIn" button or the "Share" button may be found on LinkedIn or third-party sites, such as the sites of our customers and partners. Our plugins use cookies and other technologies to provide analytics and recognize you on LinkedIn and third-party sites. If you interact with a plugin (for instance, by clicking "Apply"), the plugin will use cookies to identify you and initiate your request to apply. You can learn more about plugins in our Privacy Policy . Advertising Cookies and similar technologies help us show relevant advertising to you more effectively, both on and off our Services and to measure the performance of such ads. We use these technologies to learn whether content has been shown to you or whether someone who was presented with an ad later came back and took an action (e.g., downloaded a white paper or made a purchase) on another site. Similarly, our partners or service providers may use these technologies to determine whether we've shown an ad or a post and how it performed or provide us with information about how you interact with ads. We may also work with our customers and partners to show you an ad on or off LinkedIn, such as after you’ve visited a customer’s or partner’s site or application. These technologies help us provide aggregated information to our customers and partners. For further information regarding the use of cookies for advertising purposes, please see Sections 1.4 and 2.4 of the Privacy Policy . As noted in Section 1.4 of our Privacy Policy, outside Designated Countries , we also collect (or rely on others who collect) information about your device where you have not engaged with our Services (e.g., ad ID, IP address, operating system and browser information) so we can provide our Members with relevant ads and better understand their effectiveness. For further information, please see Section 1.4 of the Privacy Policy . Analytics and research Cookies and similar technologies help us learn more about how well our Services and plugins perform in different locations. We or our service providers use these technologies to understand, improve, and research products, features and services, including as you navigate through our sites or when you access LinkedIn from other sites, applications or devices. We or our service providers, use these technologies to determine and measure the performance of ads or posts on and off LinkedIn and to learn whether you have interacted with our websites, content or emails and provide analytics based on those interactions. We also use these technologies to provide aggregated information to our customers and partners as part of our Services. If you are a LinkedIn member but logged out of your account on a browser, LinkedIn may still continue to log your interaction with our Services on that browser until the expiration of the cookie in order to generate usage analytics for our Services. We may share these analytics in aggregate form with our customers. What third parties use these technologies in connection with our Services? Third parties such as our customers, partners and service providers may use cookies in connection with our Services. For example, third parties may use cookies in their LinkedIn pages, job posts and their advertisements on and off LinkedIn for their own marketing purposes. For an illustration, please visit LinkedIn’s Help Center . Third parties may also use cookies in connection with our off-site Services, such as LinkedIn ad services. Third parties may use cookies to help us to provide our Services. We may also work with third parties for our own marketing purposes and to enable us to analyze and research our Services. Your Choices You have choices on how LinkedIn uses cookies and similar technologies. Please note that if you limit the ability of LinkedIn to set cookies and similar technologies, you may worsen your overall user experience, since it may no longer be personalized to you. It may also stop you from saving customized settings like login information. Opt out of targeted advertising As described in Section 2.4 of the Privacy Policy , you have choices regarding the personalized ads you may see. LinkedIn Members can adjust their settings here . Visitor controls can be found here . Some mobile device operating systems such as Android provide the ability to control the use of mobile advertising IDs for ads personalization. You can learn how to use these controls by visiting the manufacturer’s website. We do not use iOS mobile advertising IDs for targeted advertising. Browser Controls Most browsers allow you to control cookies through their settings, which may be adapted to reflect your consent to the use of cookies. Further, most browsers also enable you to review and erase cookies, including LinkedIn cookies. To learn more about browser controls, please consult the documentation that your browser manufacturer provides. What is Do Not Track (DNT)? DNT is a concept that has been promoted by regulatory agencies such as the U.S. Federal Trade Commission (FTC), for the Internet industry to develop and implement a mechanism for allowing Internet users to control the tracking of their online activities across websites by using browser settings. As such, LinkedIn does not generally respond to “do not track” signals. Other helpful resources To learn more about advertisers’ use of cookies, please visit the following links: Internet Advertising Bureau (US) European Interactive Digital Advertising Alliance (EU) Internet Advertising Bureau (EU) LinkedIn © 2026 About Accessibility User Agreement Privacy Policy Cookie Policy Copyright Policy Brand Policy Guest Controls Community Guidelines العربية (Arabic) বাংলা (Bangla) Čeština (Czech) Dansk (Danish) Deutsch (German) Ελληνικά (Greek) English (English) Español (Spanish) فارسی (Persian) Suomi (Finnish) Français (French) हिंदी (Hindi) Magyar (Hungarian) Bahasa Indonesia (Indonesian) Italiano (Italian) עברית (Hebrew) 日本語 (Japanese) 한국어 (Korean) मराठी (Marathi) Bahasa Malaysia (Malay) Nederlands (Dutch) Norsk (Norwegian) ਪੰਜਾਬੀ (Punjabi) Polski (Polish) Português (Portuguese) Română (Romanian) Русский (Russian) Svenska (Swedish) తెలుగు (Telugu) ภาษาไทย (Thai) Tagalog (Tagalog) Türkçe (Turkish) Українська (Ukrainian) Tiếng Việt (Vietnamese) 简体中文 (Chinese (Simplified)) 正體中文 (Chinese (Traditional)) Language | 2026-01-13T08:48:28 |
https://youtu.be/r67SfaiYaDI?ref=mrdbourke.com | Intro to Machine Learning & Data Science (+Pandas, NumPy, Matplotlib) - YouTube 정보 보도자료 저작권 문의하기 크리에이터 광고 개발자 약관 개인정보처리방침 정책 및 안전 YouTube 작동의 원리 새로운 기능 테스트하기 © 2026 Google LLC, Sundar Pichai, 1600 Amphitheatre Parkway, Mountain View CA 94043, USA, 0807-882-594 (무료), yt-support-solutions-kr@google.com, 호스팅: Google LLC, 사업자정보 , 불법촬영물 신고 크리에이터들이 유튜브 상에 게시, 태그 또는 추천한 상품들은 판매자들의 약관에 따라 판매됩니다. 유튜브는 이러한 제품들을 판매하지 않으며, 그에 대한 책임을 지지 않습니다. var ytInitialData = {"responseContext":{"serviceTrackingParams":[{"service":"CSI","params":[{"key":"c","value":"WEB"},{"key":"cver","value":"2.20260109.01.00"},{"key":"yt_li","value":"0"},{"key":"GetWatchNext_rid","value":"0xab9fc1d2bab8ea18"}]},{"service":"GFEEDBACK","params":[{"key":"logged_in","value":"0"},{"key":"visitor_data","value":"CgttMFJPOGJmRlJxNCjWjZjLBjIKCgJLUhIEGgAgZA%3D%3D"}]},{"service":"GUIDED_HELP","params":[{"key":"logged_in","value":"0"}]},{"service":"ECATCHER","params":[{"key":"client.version","value":"2.20260109"},{"key":"client.name","value":"WEB"}]}],"mainAppWebResponseContext":{"loggedOut":true,"trackingParam":"kx_fmPxhoPZRjDuI48S9EuEhP5eZMUeKXQ0rvfiO0vo534HRgkussh7BwOcCE59TDtslLKPQ-SS"},"webResponseContextExtensionData":{"webResponseContextPreloadData":{"preloadMessageNames":["twoColumnWatchNextResults","results","videoPrimaryInfoRenderer","videoViewCountRenderer","menuRenderer","menuServiceItemRenderer","segmentedLikeDislikeButtonViewModel","likeButtonViewModel","toggleButtonViewModel","buttonViewModel","modalWithTitleAndButtonRenderer","buttonRenderer","dislikeButtonViewModel","unifiedSharePanelRenderer","menuFlexibleItemRenderer","videoSecondaryInfoRenderer","videoOwnerRenderer","subscribeButtonRenderer","subscriptionNotificationToggleButtonRenderer","menuPopupRenderer","confirmDialogRenderer","metadataRowContainerRenderer","compositeVideoPrimaryInfoRenderer","itemSectionRenderer","continuationItemRenderer","secondaryResults","lockupViewModel","thumbnailViewModel","thumbnailOverlayBadgeViewModel","thumbnailBadgeViewModel","thumbnailHoverOverlayToggleActionsViewModel","lockupMetadataViewModel","avatarStackViewModel","avatarViewModel","dialogViewModel","dialogHeaderViewModel","listViewModel","listItemViewModel","contentMetadataViewModel","sheetViewModel","decoratedAvatarViewModel","badgeViewModel","autoplay","playerOverlayRenderer","menuNavigationItemRenderer","watchNextEndScreenRenderer","endScreenVideoRenderer","thumbnailOverlayTimeStatusRenderer","thumbnailOverlayNowPlayingRenderer","playerOverlayAutoplayRenderer","playerOverlayVideoDetailsRenderer","autoplaySwitchButtonRenderer","quickActionsViewModel","decoratedPlayerBarRenderer","multiMarkersPlayerBarRenderer","chapterRenderer","notificationActionRenderer","speedmasterEduViewModel","engagementPanelSectionListRenderer","engagementPanelTitleHeaderRenderer","sortFilterSubMenuRenderer","sectionListRenderer","adsEngagementPanelContentRenderer","chipBarViewModel","chipViewModel","macroMarkersListRenderer","macroMarkersListItemRenderer","toggleButtonRenderer","structuredDescriptionContentRenderer","videoDescriptionHeaderRenderer","factoidRenderer","viewCountFactoidRenderer","expandableVideoDescriptionBodyRenderer","horizontalCardListRenderer","richListHeaderRenderer","videoDescriptionCourseSectionRenderer","structuredDescriptionPlaylistLockupRenderer","thumbnailOverlayBottomPanelRenderer","courseProgressViewModel","videoDescriptionTranscriptSectionRenderer","videoDescriptionInfocardsSectionRenderer","compactInfocardRenderer","mediaLockupRenderer","structuredDescriptionVideoLockupRenderer","desktopTopbarRenderer","topbarLogoRenderer","fusionSearchboxRenderer","topbarMenuButtonRenderer","multiPageMenuRenderer","hotkeyDialogRenderer","hotkeyDialogSectionRenderer","hotkeyDialogSectionOptionRenderer","voiceSearchDialogRenderer","cardCollectionRenderer","cardRenderer","simpleCardTeaserRenderer","cinematicContainerRenderer"]},"ytConfigData":{"visitorData":"CgttMFJPOGJmRlJxNCjWjZjLBjIKCgJLUhIEGgAgZA%3D%3D","rootVisualElementType":3832},"webPrefetchData":{"navigationEndpoints":[{"clickTrackingParams":"CAAQg2ciEwi42vbukIiSAxWjTzgFHdLfHIkyDHJlbGF0ZWQtYXV0b0iy0OHE2s-0168BmgEFCAMQ-B3KAQTS_0Lw","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=E0Hmnixke2g\u0026pp=QAFIAdIHCQmjAp4VBgUm4g%3D%3D","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"E0Hmnixke2g","params":"EAEYAdoBBAgBKgA%3D","playerParams":"QAFIAdIHCQmjAp4VBgUm4g%3D%3D","watchEndpointSupportedPrefetchConfig":{"prefetchHintConfig":{"prefetchPriority":0,"countdownUiRelativeSecondsPrefetchCondition":-3}}}},{"clickTrackingParams":"CAAQg2ciEwi42vbukIiSAxWjTzgFHdLfHIkyDHJlbGF0ZWQtYXV0b0iy0OHE2s-0168BmgEFCAMQ-B3KAQTS_0Lw","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=E0Hmnixke2g\u0026pp=QAFIAdIHCQmjAp4VBgUm4g%3D%3D","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"E0Hmnixke2g","params":"EAEYAdoBBAgBKgA%3D","playerParams":"QAFIAdIHCQmjAp4VBgUm4g%3D%3D","watchEndpointSupportedPrefetchConfig":{"prefetchHintConfig":{"prefetchPriority":0,"countdownUiRelativeSecondsPrefetchCondition":-3}}}},{"clickTrackingParams":"CAAQg2ciEwi42vbukIiSAxWjTzgFHdLfHIkyDHJlbGF0ZWQtYXV0b0iy0OHE2s-0168BmgEFCAMQ-B3KAQTS_0Lw","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=E0Hmnixke2g\u0026pp=QAFIAdIHCQmjAp4VBgUm4g%3D%3D","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"E0Hmnixke2g","params":"EAEYAdoBBAgBKgA%3D","playerParams":"QAFIAdIHCQmjAp4VBgUm4g%3D%3D","watchEndpointSupportedPrefetchConfig":{"prefetchHintConfig":{"prefetchPriority":0,"countdownUiRelativeSecondsPrefetchCondition":-3}}}}]},"hasDecorated":true}},"contents":{"twoColumnWatchNextResults":{"results":{"results":{"contents":[{"videoPrimaryInfoRenderer":{"title":{"runs":[{"text":"Intro to Machine Learning \u0026 Data Science (+Pandas, NumPy, Matplotlib)"}]},"viewCount":{"videoViewCountRenderer":{"viewCount":{"simpleText":"조회수 71,321회"},"shortViewCount":{"simpleText":"조회수 7.1만회"},"originalViewCount":"0"}},"videoActions":{"menuRenderer":{"items":[{"menuServiceItemRenderer":{"text":{"runs":[{"text":"신고"}]},"icon":{"iconType":"FLAG"},"serviceEndpoint":{"clickTrackingParams":"CO8FEMyrARgAIhMIuNr27pCIkgMVo084BR3S3xyJygEE0v9C8A==","showEngagementPanelEndpoint":{"identifier":{"tag":"PAabuse_report"},"globalConfiguration":{"params":"qgdxCAESC3I2N1NmYWlZYURJGmBFZ3R5TmpkVFptRnBXV0ZFU1VBQldBQjRCWklCTWdvd0VpNW9kSFJ3Y3pvdkwya3VlWFJwYldjdVkyOXRMM1pwTDNJMk4xTm1ZV2xaWVVSSkwyUmxabUYxYkhRdWFuQm4%3D"},"engagementPanelPresentationConfigs":{"engagementPanelPopupPresentationConfig":{"popupType":"PANEL_POPUP_TYPE_DIALOG"}}}},"trackingParams":"CO8FEMyrARgAIhMIuNr27pCIkgMVo084BR3S3xyJ"}}],"trackingParams":"CO8FEMyrARgAIhMIuNr27pCIkgMVo084BR3S3xyJ","topLevelButtons":[{"segmentedLikeDislikeButtonViewModel":{"likeButtonViewModel":{"likeButtonViewModel":{"toggleButtonViewModel":{"toggleButtonViewModel":{"defaultButtonViewModel":{"buttonViewModel":{"iconName":"LIKE","title":"1.9천","onTap":{"serialCommand":{"commands":[{"logGestureCommand":{"gestureType":"GESTURE_EVENT_TYPE_LOG_GENERIC_CLICK","trackingParams":"CPsFEKVBIhMIuNr27pCIkgMVo084BR3S3xyJ"}},{"innertubeCommand":{"clickTrackingParams":"CPsFEKVBIhMIuNr27pCIkgMVo084BR3S3xyJygEE0v9C8A==","commandMetadata":{"webCommandMetadata":{"ignoreNavigation":true}},"modalEndpoint":{"modal":{"modalWithTitleAndButtonRenderer":{"title":{"simpleText":"동영상이 마음에 드시나요?"},"content":{"simpleText":"로그인하여 의견을 알려주세요."},"button":{"buttonRenderer":{"style":"STYLE_MONO_FILLED","size":"SIZE_DEFAULT","isDisabled":false,"text":{"simpleText":"로그인"},"navigationEndpoint":{"clickTrackingParams":"CPwFEPqGBCITCLja9u6QiJIDFaNPOAUd0t8cicoBBNL_QvA=","commandMetadata":{"webCommandMetadata":{"url":"https://accounts.google.com/ServiceLogin?service=youtube\u0026uilel=3\u0026passive=true\u0026continue=https%3A%2F%2Fwww.youtube.com%2Fsignin%3Faction_handle_signin%3Dtrue%26app%3Ddesktop%26hl%3Dko\u0026hl=ko\u0026ec=66426","webPageType":"WEB_PAGE_TYPE_UNKNOWN","rootVe":83769}},"signInEndpoint":{"nextEndpoint":{"clickTrackingParams":"CPwFEPqGBCITCLja9u6QiJIDFaNPOAUd0t8cicoBBNL_QvA=","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/like/like"}},"likeEndpoint":{"status":"LIKE","target":{"videoId":"r67SfaiYaDI"},"likeParams":"Cg0KC3I2N1NmYWlZYURJIAAyDAjXjZjLBhCTzqPSAg%3D%3D"}},"idamTag":"66426"}},"trackingParams":"CPwFEPqGBCITCLja9u6QiJIDFaNPOAUd0t8ciQ=="}}}}}}}]}},"accessibilityText":"다른 사용자 1,945명과 함께 이 동영상에 좋아요 표시","style":"BUTTON_VIEW_MODEL_STYLE_MONO","trackingParams":"CPsFEKVBIhMIuNr27pCIkgMVo084BR3S3xyJ","isFullWidth":false,"type":"BUTTON_VIEW_MODEL_TYPE_TONAL","buttonSize":"BUTTON_VIEW_MODEL_SIZE_DEFAULT","accessibilityId":"id.video.like.button","tooltip":"이 동영상이 마음에 듭니다."}},"toggledButtonViewModel":{"buttonViewModel":{"iconName":"LIKE","title":"1.9천","onTap":{"serialCommand":{"commands":[{"logGestureCommand":{"gestureType":"GESTURE_EVENT_TYPE_LOG_GENERIC_CLICK","trackingParams":"CPoFEKVBIhMIuNr27pCIkgMVo084BR3S3xyJ"}},{"innertubeCommand":{"clickTrackingParams":"CPoFEKVBIhMIuNr27pCIkgMVo084BR3S3xyJygEE0v9C8A==","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/like/removelike"}},"likeEndpoint":{"status":"INDIFFERENT","target":{"videoId":"r67SfaiYaDI"},"removeLikeParams":"Cg0KC3I2N1NmYWlZYURJGAAqDAjXjZjLBhCT-KTSAg%3D%3D"}}}]}},"accessibilityText":"다른 사용자 1,945명과 함께 이 동영상에 좋아요 표시","style":"BUTTON_VIEW_MODEL_STYLE_MONO","trackingParams":"CPoFEKVBIhMIuNr27pCIkgMVo084BR3S3xyJ","isFullWidth":false,"type":"BUTTON_VIEW_MODEL_TYPE_TONAL","buttonSize":"BUTTON_VIEW_MODEL_SIZE_DEFAULT","accessibilityId":"id.video.like.button","tooltip":"좋아요 취소"}},"identifier":"watch-like","trackingParams":"CO8FEMyrARgAIhMIuNr27pCIkgMVo084BR3S3xyJ","isTogglingDisabled":true}},"likeStatusEntityKey":"EgtyNjdTZmFpWWFESSA-KAE%3D","likeStatusEntity":{"key":"EgtyNjdTZmFpWWFESSA-KAE%3D","likeStatus":"INDIFFERENT"}}},"dislikeButtonViewModel":{"dislikeButtonViewModel":{"toggleButtonViewModel":{"toggleButtonViewModel":{"defaultButtonViewModel":{"buttonViewModel":{"iconName":"DISLIKE","title":"싫어요","onTap":{"serialCommand":{"commands":[{"logGestureCommand":{"gestureType":"GESTURE_EVENT_TYPE_LOG_GENERIC_CLICK","trackingParams":"CPgFEKiPCSITCLja9u6QiJIDFaNPOAUd0t8ciQ=="}},{"innertubeCommand":{"clickTrackingParams":"CPgFEKiPCSITCLja9u6QiJIDFaNPOAUd0t8cicoBBNL_QvA=","commandMetadata":{"webCommandMetadata":{"ignoreNavigation":true}},"modalEndpoint":{"modal":{"modalWithTitleAndButtonRenderer":{"title":{"simpleText":"동영상이 마음에 안 드시나요?"},"content":{"simpleText":"로그인하여 의견을 알려주세요."},"button":{"buttonRenderer":{"style":"STYLE_MONO_FILLED","size":"SIZE_DEFAULT","isDisabled":false,"text":{"simpleText":"로그인"},"navigationEndpoint":{"clickTrackingParams":"CPkFEPmGBCITCLja9u6QiJIDFaNPOAUd0t8cicoBBNL_QvA=","commandMetadata":{"webCommandMetadata":{"url":"https://accounts.google.com/ServiceLogin?service=youtube\u0026uilel=3\u0026passive=true\u0026continue=https%3A%2F%2Fwww.youtube.com%2Fsignin%3Faction_handle_signin%3Dtrue%26app%3Ddesktop%26hl%3Dko\u0026hl=ko\u0026ec=66425","webPageType":"WEB_PAGE_TYPE_UNKNOWN","rootVe":83769}},"signInEndpoint":{"nextEndpoint":{"clickTrackingParams":"CPkFEPmGBCITCLja9u6QiJIDFaNPOAUd0t8cicoBBNL_QvA=","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/like/dislike"}},"likeEndpoint":{"status":"DISLIKE","target":{"videoId":"r67SfaiYaDI"},"dislikeParams":"Cg0KC3I2N1NmYWlZYURJEAAiDAjXjZjLBhDo9abSAg%3D%3D"}},"idamTag":"66425"}},"trackingParams":"CPkFEPmGBCITCLja9u6QiJIDFaNPOAUd0t8ciQ=="}}}}}}}]}},"accessibilityText":"동영상에 싫어요 표시","style":"BUTTON_VIEW_MODEL_STYLE_MONO","trackingParams":"CPgFEKiPCSITCLja9u6QiJIDFaNPOAUd0t8ciQ==","isFullWidth":false,"type":"BUTTON_VIEW_MODEL_TYPE_TONAL","buttonSize":"BUTTON_VIEW_MODEL_SIZE_DEFAULT","accessibilityId":"id.video.dislike.button","tooltip":"이 동영상이 마음에 들지 않습니다."}},"toggledButtonViewModel":{"buttonViewModel":{"iconName":"DISLIKE","title":"싫어요","onTap":{"serialCommand":{"commands":[{"logGestureCommand":{"gestureType":"GESTURE_EVENT_TYPE_LOG_GENERIC_CLICK","trackingParams":"CPcFEKiPCSITCLja9u6QiJIDFaNPOAUd0t8ciQ=="}},{"innertubeCommand":{"clickTrackingParams":"CPcFEKiPCSITCLja9u6QiJIDFaNPOAUd0t8cicoBBNL_QvA=","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/like/removelike"}},"likeEndpoint":{"status":"INDIFFERENT","target":{"videoId":"r67SfaiYaDI"},"removeLikeParams":"Cg0KC3I2N1NmYWlZYURJGAAqDAjXjZjLBhCLtKfSAg%3D%3D"}}}]}},"accessibilityText":"동영상에 싫어요 표시","style":"BUTTON_VIEW_MODEL_STYLE_MONO","trackingParams":"CPcFEKiPCSITCLja9u6QiJIDFaNPOAUd0t8ciQ==","isFullWidth":false,"type":"BUTTON_VIEW_MODEL_TYPE_TONAL","buttonSize":"BUTTON_VIEW_MODEL_SIZE_DEFAULT","accessibilityId":"id.video.dislike.button","tooltip":"이 동영상이 마음에 들지 않습니다."}},"trackingParams":"CO8FEMyrARgAIhMIuNr27pCIkgMVo084BR3S3xyJ","isTogglingDisabled":true}},"dislikeEntityKey":"EgtyNjdTZmFpWWFESSA-KAE%3D"}},"iconType":"LIKE_ICON_TYPE_UNKNOWN","likeCountEntity":{"key":"unset_like_count_entity_key"},"dynamicLikeCountUpdateData":{"updateStatusKey":"like_count_update_status_key","placeholderLikeCountValuesKey":"like_count_placeholder_values_key","updateDelayLoopId":"like_count_update_delay_loop_id","updateDelaySec":5},"teasersOrderEntityKey":"EgtyNjdTZmFpWWFESSD8AygB"}},{"buttonViewModel":{"iconName":"SHARE","title":"공유","onTap":{"serialCommand":{"commands":[{"logGestureCommand":{"gestureType":"GESTURE_EVENT_TYPE_LOG_GENERIC_CLICK","trackingParams":"CPUFEOWWARgDIhMIuNr27pCIkgMVo084BR3S3xyJ"}},{"innertubeCommand":{"clickTrackingParams":"CPUFEOWWARgDIhMIuNr27pCIkgMVo084BR3S3xyJygEE0v9C8A==","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/share/get_share_panel"}},"shareEntityServiceEndpoint":{"serializedShareEntity":"CgtyNjdTZmFpWWFESaABAQ%3D%3D","commands":[{"clickTrackingParams":"CPUFEOWWARgDIhMIuNr27pCIkgMVo084BR3S3xyJygEE0v9C8A==","openPopupAction":{"popup":{"unifiedSharePanelRenderer":{"trackingParams":"CPYFEI5iIhMIuNr27pCIkgMVo084BR3S3xyJ","showLoadingSpinner":true}},"popupType":"DIALOG","beReused":true}}]}}}]}},"accessibilityText":"공유","style":"BUTTON_VIEW_MODEL_STYLE_MONO","trackingParams":"CPUFEOWWARgDIhMIuNr27pCIkgMVo084BR3S3xyJ","isFullWidth":false,"type":"BUTTON_VIEW_MODEL_TYPE_TONAL","buttonSize":"BUTTON_VIEW_MODEL_SIZE_DEFAULT","state":"BUTTON_VIEW_MODEL_STATE_ACTIVE","accessibilityId":"id.video.share.button","tooltip":"공유"}}],"accessibility":{"accessibilityData":{"label":"추가 작업"}},"flexibleItems":[{"menuFlexibleItemRenderer":{"menuItem":{"menuServiceItemRenderer":{"text":{"runs":[{"text":"저장"}]},"icon":{"iconType":"PLAYLIST_ADD"},"serviceEndpoint":{"clickTrackingParams":"CPMFEOuQCSITCLja9u6QiJIDFaNPOAUd0t8cicoBBNL_QvA=","commandMetadata":{"webCommandMetadata":{"ignoreNavigation":true}},"modalEndpoint":{"modal":{"modalWithTitleAndButtonRenderer":{"title":{"runs":[{"text":"나중에 다시 보고 싶으신가요?"}]},"content":{"runs":[{"text":"로그인하여 동영상을 재생목록에 추가하세요."}]},"button":{"buttonRenderer":{"style":"STYLE_MONO_FILLED","size":"SIZE_DEFAULT","isDisabled":false,"text":{"simpleText":"로그인"},"navigationEndpoint":{"clickTrackingParams":"CPQFEPuGBCITCLja9u6QiJIDFaNPOAUd0t8cicoBBNL_QvA=","commandMetadata":{"webCommandMetadata":{"url":"https://accounts.google.com/ServiceLogin?service=youtube\u0026uilel=3\u0026passive=true\u0026continue=https%3A%2F%2Fwww.youtube.com%2Fsignin%3Faction_handle_signin%3Dtrue%26app%3Ddesktop%26hl%3Dko%26next%3D%252Fwatch%253Fv%253Dr67SfaiYaDI\u0026hl=ko\u0026ec=66427","webPageType":"WEB_PAGE_TYPE_UNKNOWN","rootVe":83769}},"signInEndpoint":{"nextEndpoint":{"clickTrackingParams":"CPQFEPuGBCITCLja9u6QiJIDFaNPOAUd0t8cicoBBNL_QvA=","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=r67SfaiYaDI","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"r67SfaiYaDI","watchEndpointSupportedOnesieConfig":{"html5PlaybackOnesieConfig":{"commonConfig":{"url":"https://rr8---sn-ab02a0nfpgxapox-jwwk.googlevideo.com/initplayback?source=youtube\u0026oeis=1\u0026c=WEB\u0026oad=3200\u0026ovd=3200\u0026oaad=11000\u0026oavd=11000\u0026ocs=700\u0026oewis=1\u0026oputc=1\u0026ofpcc=1\u0026msp=1\u0026odepv=1\u0026id=afaed27da8986832\u0026ip=1.208.108.242\u0026initcwndbps=3355000\u0026mt=1768293662\u0026oweuc="}}}}},"idamTag":"66427"}},"trackingParams":"CPQFEPuGBCITCLja9u6QiJIDFaNPOAUd0t8ciQ=="}}}}}},"trackingParams":"CPMFEOuQCSITCLja9u6QiJIDFaNPOAUd0t8ciQ=="}},"topLevelButton":{"buttonViewModel":{"iconName":"PLAYLIST_ADD","title":"저장","onTap":{"serialCommand":{"commands":[{"logGestureCommand":{"gestureType":"GESTURE_EVENT_TYPE_LOG_GENERIC_CLICK","trackingParams":"CPEFEOuQCSITCLja9u6QiJIDFaNPOAUd0t8ciQ=="}},{"innertubeCommand":{"clickTrackingParams":"CPEFEOuQCSITCLja9u6QiJIDFaNPOAUd0t8cicoBBNL_QvA=","commandMetadata":{"webCommandMetadata":{"ignoreNavigation":true}},"modalEndpoint":{"modal":{"modalWithTitleAndButtonRenderer":{"title":{"runs":[{"text":"나중에 다시 보고 싶으신가요?"}]},"content":{"runs":[{"text":"로그인하여 동영상을 재생목록에 추가하세요."}]},"button":{"buttonRenderer":{"style":"STYLE_MONO_FILLED","size":"SIZE_DEFAULT","isDisabled":false,"text":{"simpleText":"로그인"},"navigationEndpoint":{"clickTrackingParams":"CPIFEPuGBCITCLja9u6QiJIDFaNPOAUd0t8cicoBBNL_QvA=","commandMetadata":{"webCommandMetadata":{"url":"https://accounts.google.com/ServiceLogin?service=youtube\u0026uilel=3\u0026passive=true\u0026continue=https%3A%2F%2Fwww.youtube.com%2Fsignin%3Faction_handle_signin%3Dtrue%26app%3Ddesktop%26hl%3Dko%26next%3D%252Fwatch%253Fv%253Dr67SfaiYaDI\u0026hl=ko\u0026ec=66427","webPageType":"WEB_PAGE_TYPE_UNKNOWN","rootVe":83769}},"signInEndpoint":{"nextEndpoint":{"clickTrackingParams":"CPIFEPuGBCITCLja9u6QiJIDFaNPOAUd0t8cicoBBNL_QvA=","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=r67SfaiYaDI","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"r67SfaiYaDI","watchEndpointSupportedOnesieConfig":{"html5PlaybackOnesieConfig":{"commonConfig":{"url":"https://rr8---sn-ab02a0nfpgxapox-jwwk.googlevideo.com/initplayback?source=youtube\u0026oeis=1\u0026c=WEB\u0026oad=3200\u0026ovd=3200\u0026oaad=11000\u0026oavd=11000\u0026ocs=700\u0026oewis=1\u0026oputc=1\u0026ofpcc=1\u0026msp=1\u0026odepv=1\u0026id=afaed27da8986832\u0026ip=1.208.108.242\u0026initcwndbps=3355000\u0026mt=1768293662\u0026oweuc="}}}}},"idamTag":"66427"}},"trackingParams":"CPIFEPuGBCITCLja9u6QiJIDFaNPOAUd0t8ciQ=="}}}}}}}]}},"accessibilityText":"재생목록에 저장","style":"BUTTON_VIEW_MODEL_STYLE_MONO","trackingParams":"CPEFEOuQCSITCLja9u6QiJIDFaNPOAUd0t8ciQ==","isFullWidth":false,"type":"BUTTON_VIEW_MODEL_TYPE_TONAL","buttonSize":"BUTTON_VIEW_MODEL_SIZE_DEFAULT","tooltip":"저장"}}}}]}},"trackingParams":"CO8FEMyrARgAIhMIuNr27pCIkgMVo084BR3S3xyJ","superTitleLink":{"runs":[{"text":"Crash Courses","navigationEndpoint":{"clickTrackingParams":"CPAFEJmtCRgAIhMIuNr27pCIkgMVo084BR3S3xyJygEE0v9C8A==","commandMetadata":{"webCommandMetadata":{"url":"/playlist?list=PL2HX_yT71umB_oqitnmDgYSKltddPfZ-k","webPageType":"WEB_PAGE_TYPE_PLAYLIST","rootVe":5754,"apiUrl":"/youtubei/v1/browse"}},"browseEndpoint":{"browseId":"VLPL2HX_yT71umB_oqitnmDgYSKltddPfZ-k"}},"loggingDirectives":{"trackingParams":"CPAFEJmtCRgAIhMIuNr27pCIkgMVo084BR3S3xyJ","visibility":{"types":"12"}}}]},"dateText":{"simpleText":"2023. 6. 13."},"relativeDateText":{"accessibility":{"accessibilityData":{"label":"2년 전"}},"simpleText":"2년 전"}}},{"videoSecondaryInfoRenderer":{"owner":{"videoOwnerRenderer":{"thumbnail":{"thumbnails":[{"url":"https://yt3.ggpht.com/ZmhWf1RNwIItXpRwgxl69BTbD0Rd12RaUdJCRCwqFHsoozStfHunMgUcy3afuxLbCG2-J8nRsis=s48-c-k-c0x00ffffff-no-rj","width":48,"height":48},{"url":"https://yt3.ggpht.com/ZmhWf1RNwIItXpRwgxl69BTbD0Rd12RaUdJCRCwqFHsoozStfHunMgUcy3afuxLbCG2-J8nRsis=s88-c-k-c0x00ffffff-no-rj","width":88,"height":88},{"url":"https://yt3.ggpht.com/ZmhWf1RNwIItXpRwgxl69BTbD0Rd12RaUdJCRCwqFHsoozStfHunMgUcy3afuxLbCG2-J8nRsis=s176-c-k-c0x00ffffff-no-rj","width":176,"height":176}]},"title":{"runs":[{"text":"Zero To Mastery","navigationEndpoint":{"clickTrackingParams":"CO4FEOE5IhMIuNr27pCIkgMVo084BR3S3xyJygEE0v9C8A==","commandMetadata":{"webCommandMetadata":{"url":"/@ZeroToMastery","webPageType":"WEB_PAGE_TYPE_CHANNEL","rootVe":3611,"apiUrl":"/youtubei/v1/browse"}},"browseEndpoint":{"browseId":"UCt7T2EvYBqvlxNU3fbE4Y7g","canonicalBaseUrl":"/@ZeroToMastery"}}}]},"subscriptionButton":{"type":"FREE"},"navigationEndpoint":{"clickTrackingParams":"CO4FEOE5IhMIuNr27pCIkgMVo084BR3S3xyJygEE0v9C8A==","commandMetadata":{"webCommandMetadata":{"url":"/@ZeroToMastery","webPageType":"WEB_PAGE_TYPE_CHANNEL","rootVe":3611,"apiUrl":"/youtubei/v1/browse"}},"browseEndpoint":{"browseId":"UCt7T2EvYBqvlxNU3fbE4Y7g","canonicalBaseUrl":"/@ZeroToMastery"}},"subscriberCountText":{"accessibility":{"accessibilityData":{"label":"구독자 25.1만명"}},"simpleText":"구독자 25.1만명"},"trackingParams":"CO4FEOE5IhMIuNr27pCIkgMVo084BR3S3xyJ"}},"subscribeButton":{"subscribeButtonRenderer":{"buttonText":{"runs":[{"text":"구독"}]},"subscribed":false,"enabled":true,"type":"FREE","channelId":"UCt7T2EvYBqvlxNU3fbE4Y7g","showPreferences":false,"subscribedButtonText":{"runs":[{"text":"구독중"}]},"unsubscribedButtonText":{"runs":[{"text":"구독"}]},"trackingParams":"COAFEJsrIhMIuNr27pCIkgMVo084BR3S3xyJKPgdMgV3YXRjaA==","unsubscribeButtonText":{"runs":[{"text":"구독 취소"}]},"subscribeAccessibility":{"accessibilityData":{"label":"Zero To Mastery을(를) 구독합니다."}},"unsubscribeAccessibility":{"accessibilityData":{"label":"Zero To Mastery을(를) 구독 취소합니다."}},"notificationPreferenceButton":{"subscriptionNotificationToggleButtonRenderer":{"states":[{"stateId":3,"nextStateId":3,"state":{"buttonRenderer":{"style":"STYLE_TEXT","size":"SIZE_DEFAULT","isDisabled":false,"icon":{"iconType":"NOTIFICATIONS_NONE"},"accessibility":{"label":"현재 설정은 맞춤설정 알림 수신입니다. Zero To Mastery 채널의 알림 설정을 변경하려면 탭하세요."},"trackingParams":"CO0FEPBbIhMIuNr27pCIkgMVo084BR3S3xyJ","accessibilityData":{"accessibilityData":{"label":"현재 설정은 맞춤설정 알림 수신입니다. Zero To Mastery 채널의 알림 설정을 변경하려면 탭하세요."}}}}},{"stateId":0,"nextStateId":0,"state":{"buttonRenderer":{"style":"STYLE_TEXT","size":"SIZE_DEFAULT","isDisabled":false,"icon":{"iconType":"NOTIFICATIONS_OFF"},"accessibility":{"label":"현재 설정은 알림 수신 안함입니다. Zero To Mastery 채널의 알림 설정을 변경하려면 탭하세요."},"trackingParams":"COwFEPBbIhMIuNr27pCIkgMVo084BR3S3xyJ","accessibilityData":{"accessibilityData":{"label":"현재 설정은 알림 수신 안함입니다. Zero To Mastery 채널의 알림 설정을 변경하려면 탭하세요."}}}}}],"currentStateId":3,"trackingParams":"COUFEJf5ASITCLja9u6QiJIDFaNPOAUd0t8ciQ==","command":{"clickTrackingParams":"COUFEJf5ASITCLja9u6QiJIDFaNPOAUd0t8cicoBBNL_QvA=","commandExecutorCommand":{"commands":[{"clickTrackingParams":"COUFEJf5ASITCLja9u6QiJIDFaNPOAUd0t8cicoBBNL_QvA=","openPopupAction":{"popup":{"menuPopupRenderer":{"items":[{"menuServiceItemRenderer":{"text":{"simpleText":"맞춤설정"},"icon":{"iconType":"NOTIFICATIONS_NONE"},"serviceEndpoint":{"clickTrackingParams":"COsFEOy1BBgDIhMIuNr27pCIkgMVo084BR3S3xyJMhJQUkVGRVJFTkNFX0RFRkFVTFTKAQTS_0Lw","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/notification/modify_channel_preference"}},"modifyChannelNotificationPreferenceEndpoint":{"params":"ChhVQ3Q3VDJFdllCcXZseE5VM2ZiRTRZN2cSAggBGAAgBFITCgIIAxILcjY3U2ZhaVlhREkYAA%3D%3D"}},"trackingParams":"COsFEOy1BBgDIhMIuNr27pCIkgMVo084BR3S3xyJ","isSelected":true}},{"menuServiceItemRenderer":{"text":{"simpleText":"없음"},"icon":{"iconType":"NOTIFICATIONS_OFF"},"serviceEndpoint":{"clickTrackingParams":"COoFEO21BBgEIhMIuNr27pCIkgMVo084BR3S3xyJMhtQUkVGRVJFTkNFX05PX05PVElGSUNBVElPTlPKAQTS_0Lw","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/notification/modify_channel_preference"}},"modifyChannelNotificationPreferenceEndpoint":{"params":"ChhVQ3Q3VDJFdllCcXZseE5VM2ZiRTRZN2cSAggDGAAgBFITCgIIAxILcjY3U2ZhaVlhREkYAA%3D%3D"}},"trackingParams":"COoFEO21BBgEIhMIuNr27pCIkgMVo084BR3S3xyJ","isSelected":false}},{"menuServiceItemRenderer":{"text":{"runs":[{"text":"구독 취소"}]},"icon":{"iconType":"PERSON_MINUS"},"serviceEndpoint":{"clickTrackingParams":"COYFENuLChgFIhMIuNr27pCIkgMVo084BR3S3xyJygEE0v9C8A==","commandMetadata":{"webCommandMetadata":{"sendPost":true}},"signalServiceEndpoint":{"signal":"CLIENT_SIGNAL","actions":[{"clickTrackingParams":"COYFENuLChgFIhMIuNr27pCIkgMVo084BR3S3xyJygEE0v9C8A==","openPopupAction":{"popup":{"confirmDialogRenderer":{"trackingParams":"COcFEMY4IhMIuNr27pCIkgMVo084BR3S3xyJ","dialogMessages":[{"runs":[{"text":"Zero To Mastery"},{"text":" 구독을 취소하시겠습니까?"}]}],"confirmButton":{"buttonRenderer":{"style":"STYLE_BLUE_TEXT","size":"SIZE_DEFAULT","isDisabled":false,"text":{"runs":[{"text":"구독 취소"}]},"serviceEndpoint":{"clickTrackingParams":"COkFEPBbIhMIuNr27pCIkgMVo084BR3S3xyJMgV3YXRjaMoBBNL_QvA=","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/subscription/unsubscribe"}},"unsubscribeEndpoint":{"channelIds":["UCt7T2EvYBqvlxNU3fbE4Y7g"],"params":"CgIIAxILcjY3U2ZhaVlhREkYAA%3D%3D"}},"accessibility":{"label":"구독 취소"},"trackingParams":"COkFEPBbIhMIuNr27pCIkgMVo084BR3S3xyJ"}},"cancelButton":{"buttonRenderer":{"style":"STYLE_TEXT","size":"SIZE_DEFAULT","isDisabled":false,"text":{"runs":[{"text":"취소"}]},"accessibility":{"label":"취소"},"trackingParams":"COgFEPBbIhMIuNr27pCIkgMVo084BR3S3xyJ"}},"primaryIsCancel":false}},"popupType":"DIALOG"}}]}},"trackingParams":"COYFENuLChgFIhMIuNr27pCIkgMVo084BR3S3xyJ"}}]}},"popupType":"DROPDOWN"}}]}},"targetId":"notification-bell","secondaryIcon":{"iconType":"EXPAND_MORE"}}},"targetId":"watch-subscribe","signInEndpoint":{"clickTrackingParams":"COAFEJsrIhMIuNr27pCIkgMVo084BR3S3xyJygEE0v9C8A==","commandMetadata":{"webCommandMetadata":{"ignoreNavigation":true}},"modalEndpoint":{"modal":{"modalWithTitleAndButtonRenderer":{"title":{"simpleText":"채널을 구독하시겠습니까?"},"content":{"simpleText":"채널을 구독하려면 로그인하세요."},"button":{"buttonRenderer":{"style":"STYLE_MONO_FILLED","size":"SIZE_DEFAULT","isDisabled":false,"text":{"simpleText":"로그인"},"navigationEndpoint":{"clickTrackingParams":"COQFEP2GBCITCLja9u6QiJIDFaNPOAUd0t8ciTIJc3Vic2NyaWJlygEE0v9C8A==","commandMetadata":{"webCommandMetadata":{"url":"https://accounts.google.com/ServiceLogin?service=youtube\u0026uilel=3\u0026passive=true\u0026continue=https%3A%2F%2Fwww.youtube.com%2Fsignin%3Faction_handle_signin%3Dtrue%26app%3Ddesktop%26hl%3Dko%26next%3D%252Fwatch%253Fv%253Dr67SfaiYaDI%26continue_action%3DQUFFLUhqbkdYWmVWbUpsRTdfTlhfTXRVWk11WG1oT1M3Z3xBQ3Jtc0tuaWlJUU5TTHRqN3Z5b0otTzhsLWtZd24zQzE1d3V2Rm02XzV2dWstM0duUDhIRTFDNWM5YjJnOHZjWnlVWWVZbC1qelJPcVBnM3IyU2ppVWxVVWdNc1VXX2F5R1ItclV5S3RoT0xvR0ZENzBpUTRqZEhqa01oZnF3dzVXT2hIOURyNmp4SU4xT3JXajNfUVYzTTRDZVIxU2R5SnRORU5GZEVxLVd5LVMtMldqYzl2SjN1TENNQ2E5X3dUUi1ncC1BeGVxbzc\u0026hl=ko\u0026ec=66429","webPageType":"WEB_PAGE_TYPE_UNKNOWN","rootVe":83769}},"signInEndpoint":{"nextEndpoint":{"clickTrackingParams":"COQFEP2GBCITCLja9u6QiJIDFaNPOAUd0t8cicoBBNL_QvA=","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=r67SfaiYaDI","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"r67SfaiYaDI","watchEndpointSupportedOnesieConfig":{"html5PlaybackOnesieConfig":{"commonConfig":{"url":"https://rr8---sn-ab02a0nfpgxapox-jwwk.googlevideo.com/initplayback?source=youtube\u0026oeis=1\u0026c=WEB\u0026oad=3200\u0026ovd=3200\u0026oaad=11000\u0026oavd=11000\u0026ocs=700\u0026oewis=1\u0026oputc=1\u0026ofpcc=1\u0026msp=1\u0026odepv=1\u0026id=afaed27da8986832\u0026ip=1.208.108.242\u0026initcwndbps=3355000\u0026mt=1768293662\u0026oweuc="}}}}},"continueAction":"QUFFLUhqbkdYWmVWbUpsRTdfTlhfTXRVWk11WG1oT1M3Z3xBQ3Jtc0tuaWlJUU5TTHRqN3Z5b0otTzhsLWtZd24zQzE1d3V2Rm02XzV2dWstM0duUDhIRTFDNWM5YjJnOHZjWnlVWWVZbC1qelJPcVBnM3IyU2ppVWxVVWdNc1VXX2F5R1ItclV5S3RoT0xvR0ZENzBpUTRqZEhqa01oZnF3dzVXT2hIOURyNmp4SU4xT3JXajNfUVYzTTRDZVIxU2R5SnRORU5GZEVxLVd5LVMtMldqYzl2SjN1TENNQ2E5X3dUUi1ncC1BeGVxbzc","idamTag":"66429"}},"trackingParams":"COQFEP2GBCITCLja9u6QiJIDFaNPOAUd0t8ciQ=="}}}}}},"subscribedEntityKey":"EhhVQ3Q3VDJFdllCcXZseE5VM2ZiRTRZN2cgMygB","onSubscribeEndpoints":[{"clickTrackingParams":"COAFEJsrIhMIuNr27pCIkgMVo084BR3S3xyJKPgdMgV3YXRjaMoBBNL_QvA=","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/subscription/subscribe"}},"subscribeEndpoint":{"channelIds":["UCt7T2EvYBqvlxNU3fbE4Y7g"],"params":"EgIIAxgAIgtyNjdTZmFpWWFESQ%3D%3D"}}],"onUnsubscribeEndpoints":[{"clickTrackingParams":"COAFEJsrIhMIuNr27pCIkgMVo084BR3S3xyJygEE0v9C8A==","commandMetadata":{"webCommandMetadata":{"sendPost":true}},"signalServiceEndpoint":{"signal":"CLIENT_SIGNAL","actions":[{"clickTrackingParams":"COAFEJsrIhMIuNr27pCIkgMVo084BR3S3xyJygEE0v9C8A==","openPopupAction":{"popup":{"confirmDialogRenderer":{"trackingParams":"COEFEMY4IhMIuNr27pCIkgMVo084BR3S3xyJ","dialogMessages":[{"runs":[{"text":"Zero To Mastery"},{"text":" 구독을 취소하시겠습니까?"}]}],"confirmButton":{"buttonRenderer":{"style":"STYLE_BLUE_TEXT","size":"SIZE_DEFAULT","isDisabled":false,"text":{"runs":[{"text":"구독 취소"}]},"serviceEndpoint":{"clickTrackingParams":"COMFEPBbIhMIuNr27pCIkgMVo084BR3S3xyJKPgdMgV3YXRjaMoBBNL_QvA=","commandMetadata":{"webCommandMetadata":{"sendPost":true,"apiUrl":"/youtubei/v1/subscription/unsubscribe"}},"unsubscribeEndpoint":{"channelIds":["UCt7T2EvYBqvlxNU3fbE4Y7g"],"params":"CgIIAxILcjY3U2ZhaVlhREkYAA%3D%3D"}},"accessibility":{"label":"구독 취소"},"trackingParams":"COMFEPBbIhMIuNr27pCIkgMVo084BR3S3xyJ"}},"cancelButton":{"buttonRenderer":{"style":"STYLE_TEXT","size":"SIZE_DEFAULT","isDisabled":false,"text":{"runs":[{"text":"취소"}]},"accessibility":{"label":"취소"},"trackingParams":"COIFEPBbIhMIuNr27pCIkgMVo084BR3S3xyJ"}},"primaryIsCancel":false}},"popupType":"DIALOG"}}]}}]}},"metadataRowContainer":{"metadataRowContainerRenderer":{"collapsedItemCount":0,"trackingParams":"CN0FEM2rARgBIhMIuNr27pCIkgMVo084BR3S3xyJ"}},"showMoreText":{"simpleText":"...더보기"},"showLessText":{"simpleText":"간략히"},"trackingParams":"CN0FEM2rARgBIhMIuNr27pCIkgMVo084BR3S3xyJ","defaultExpanded":false,"descriptionCollapsedLines":3,"showMoreCommand":{"clickTrackingParams":"CN0FEM2rARgBIhMIuNr27pCIkgMVo084BR3S3xyJygEE0v9C8A==","commandExecutorCommand":{"commands":[{"clickTrackingParams":"CN0FEM2rARgBIhMIuNr27pCIkgMVo084BR3S3xyJygEE0v9C8A==","changeEngagementPanelVisibilityAction":{"targetId":"engagement-panel-structured-description","visibility":"ENGAGEMENT_PANEL_VISIBILITY_EXPANDED"}},{"clickTrackingParams":"CN0FEM2rARgBIhMIuNr27pCIkgMVo084BR3S3xyJygEE0v9C8A==","scrollToEngagementPanelCommand":{"targetId":"engagement-panel-structured-description"}}]}},"showLessCommand":{"clickTrackingParams":"CN0FEM2rARgBIhMIuNr27pCIkgMVo084BR3S3xyJygEE0v9C8A==","changeEngagementPanelVisibilityAction":{"targetId":"engagement-panel-structured-description","visibility":"ENGAGEMENT_PANEL_VISIBILITY_HIDDEN"}},"attributedDescription":{"content":"Become a Machine Learning Engineer! Join Daniel Bourke \u0026 Andrei Neagoie as they take you from complete beginner to learning the basics of Machine Learning \u0026 Data Science. In this 10-hour beginner course, you'll learn: machine learning 101, environment setup, data analysis, and some popular ML libraries like Pandas, NumPy \u0026 Matplotlib!\n\nThis Crash Course is ~25% of Andrei \u0026 Daniel's Machine Learning \u0026 Data Science Bootcamp course.\n\nSo if you like this video, you'll LOVE their full course which has 30+ hours of additional lectures where you'll get to build your own machine learning models from scratch!\n\nWant to get hired as a professional ML Engineer or Data Scientist? Then take the full course 👇\n\n🤖 Full Machine Learning \u0026 Data Science Bootcamp Course: https://zerotomastery.io/courses/mach...\n\n🎁 [LIMITED TIME ONLY] Use code: YTMLDS10 to get 10% OFF (for life!)\n\n==========\n\n🗂 Crash Course Files: https://links.zerotomastery.io/machin... \n📓 Course Handbook: https://dev.mrdbourke.com/zero-to-mas...\n🐍 Free Python Crash Course: • Python 101 Crash Course: Learn Python v3 (... \n\n==========\n\n⏲ Timestamps:\n\n00:00 Course Intro\n01:50 Your First Day\n05:50 What Is Machine Learning?\n12:54 AI/Machine Learning/Data Science\n17:57 \rExercise: Machine Learning Playground\n24:25 \rHow Did We Get Here?\n30:40 Exercise: YouTube Recommendation Engine\n35:18 \rTypes of Machine Learning\n40:11 What Is Machine Learning? Round 2\n42:11 \rSection Review\n47:08 Section Overview: Machine Learning and Data Science Framework\n50:28 \rIntroducing Our Framework\n53:17 \r6-Step Machine Learning Framework\n58:29 Types of Machine Learning Problems\n1:09:13 \rTypes of Data\n1:14:16 Types of Evaluation\n1:17:59 \rFeatures in Data\n1:23:33 Modelling - Splitting Data\n1:29:44 Modelling - Picking the Model\n1:37:59 Modelling - Comparison\n1:47:44 \rOverfitting and Underfitting Definitions: Experimentation\n1:51:47 Tools We Will Use\n1:55:59 \rQuick Announcement\n1:57:04 \rSection Overview: Data Science Environment Setup\n1:58:24 \rIntroducing Our Tools\n2:02:06 \rWhat is Conda?\n2:04:52 \rConda Environments\n2:09:35 \rMac Environment Setup\n2:27:14 Mac Environment Setup 2\n2:47:06 \rWindows Environment Setup 2\n3:10:35 \rLinux Environment Setup\n3:10:51 \rSharing your Conda Environment\n3:11:03 Jupyter Notebook Walkthrough\n3:21:37 Jupyter Notebook Walkthrough 2\n3:38:06 J\rupyter Notebook Walkthrough 3\n3:46:28 Section Overview: Pandas - Data Analysis\n3:49:08 \rDownloading Workbooks \u0026 Assignments - https://github.com/mrdbourke/zero-to-...\n3:49:19 Pandas Introduction\n3:54:00 Series, Data Frames \u0026 CSVs\n4:07:34 \rData from URLs\n4:07:45 Describing Data with Pandas\n4:17:46 \rSelecting and Viewing Data with Pandas\n4:29:07 \rSelecting and Viewing Data with Pandas Part 2\n4:42:25 Manipulating Data\n4:56:34 Manipulating Data 2\n5:06:43 \rManipulating Data 3\n5:17:07 \rAssignment: Pandas Practice\n5:17:18 \rHow To Download The Course Assignments - https://github.com/mrdbourke/zero-to-...\n5:25:14 \rSection Overview: NumPy\n5:28:06 NumPy Introduction\n5:33:35 Quick Note: Correction in the next video\n5:34:23 NumPy DataTypes and Attributes\n5:48:40 Creating NumPy Arrays\n5:58:15 \rNumPy Random Seed\n6:05:43 Viewing Arrays and Matrices\n6:15:33 \rManipulating Arrays\n6:27:16 \rManipulating Arrays 2\n6:37:11 \rStandard Deviation and Variance\n6:44:34 \rReshape and Transpose\n6:52:12 Dot Product vs Element Wise\n7:04:08 \rExercise: Nut Butter Store Sales\n7:17:24 \rComparison Operators\n7:21:10 \rSorting Arrays\n7:27:41 T\rurn Images Into NumPy Arrays\n7:35:31 Assignment: NumPy Practice\n7:35:42 Section Overview: Matplotlib - Plotting and Data Visualization\n7:37:45 Matplotlib Introduction\n7:43:14 \rImporting And Using Matplotlib\n7:55:02 \rAnatomy Of A Matplotlib Figure\n8:04:24 Scatter Plot And Bar Plot\n8:14:45 Histograms And Subplots\n8:23:37 \rSubplots Option 2\n8:28:05 \rQuick Tip: Data Visualizations\n8:34:15 Plotting From Pandas DataFrames\n8:36:15 Quick Note: Regular Expressions\n8:36:27 Plotting From Pandas DataFrames 2\n8:47:13 Plotting from Pandas DataFrames 3\n8:55:57 \rPlotting from Pandas DataFrames 4\n9:02:44 \rPlotting from Pandas DataFrames 5\n9:11:25 \rPlotting from Pandas DataFrames 6\n9:20:06 \rPlotting from Pandas DataFrames 7\n9:31:38 \rCustomizing Your Plots\n9:41:59 \rCustomizing Your Plots 2\n9:51:52 Saving And Sharing Your Plots\n9:56:18 \rAssignment: Matplotlib Practice\n9:56:30 Section Overview: Scikit-learn Creating Machine Learning Models\n9:59:10\r Where To Keep Learning\n\n==========\n\nGraduates of Zero To Mastery are now working at Google, Tesla, Amazon, Apple, IBM, JP Morgan, Facebook, Shopify + other top tech companies. Many are also working as top-rated Freelancers getting paid $1,000s while working remotely around the world.\n\n🎓 Here are just a few of them: https://zerotomastery.io/testimonials\n\nThis could be you 👆\n\n==========\n\nFull ML Bootcamp 👉 https://zerotomastery.io/courses/mach...\n\n#zerotomastery #machinelearning","commandRuns":[{"startIndex":764,"length":40,"onTap":{"innertubeCommand":{"clickTrackingParams":"CN0FEM2rARgBIhMIuNr27pCIkgMVo084BR3S3xyJSLLQ4cTaz7TXrwHKAQTS_0Lw","commandMetadata":{"webCommandMetadata":{"url":"https://www.youtube.com/redirect?event=video_description\u0026redir_token=QUFFLUhqbW1UOVc0SENCWTYtSVBaNXJ1NWtiMmRqcnlUd3xBQ3Jtc0trVlZIY21IV05TSE9CVTNiTlB3WU5WVFYxNlpJQS1Ca1JDVExiREVzWWNmcE1mbml6OUpPOEhadEk0ZWxoU3hoMm9ZRG5aSGN4QjQxTUtCQzZlUGw3WDcxcms0TUxoQUNZeE40anRwOEt6VjhmSlBmaw\u0026q=https%3A%2F%2Fzerotomastery.io%2Fcourses%2Fmachine-learning-and-data-science-bootcamp%2F\u0026v=r67SfaiYaDI","webPageType":"WEB_PAGE_TYPE_UNKNOWN","rootVe":83769}},"urlEndpoint":{"url":"https://www.youtube.com/redirect?event=video_description\u0026redir_token=QUFFLUhqbW1UOVc0SENCWTYtSVBaNXJ1NWtiMmRqcnlUd3xBQ3Jtc0trVlZIY21IV05TSE9CVTNiTlB3WU5WVFYxNlpJQS1Ca1JDVExiREVzWWNmcE1mbml6OUpPOEhadEk0ZWxoU3hoMm9ZRG5aSGN4QjQxTUtCQzZlUGw3WDcxcms0TUxoQUNZeE40anRwOEt6VjhmSlBmaw\u0026q=https%3A%2F%2Fzerotomastery.io%2Fcourses%2Fmachine-learning-and-data-science-bootcamp%2F\u0026v=r67SfaiYaDI","target":"TARGET_NEW_WINDOW","nofollow":true}}}},{"startIndex":911,"length":40,"onTap":{"innertubeCommand":{"clickTrackingParams":"CN0FEM2rARgBIhMIuNr27pCIkgMVo084BR3S3xyJSLLQ4cTaz7TXrwHKAQTS_0Lw","commandMetadata":{"webCommandMetadata":{"url":"https://www.youtube.com/redirect?event=video_description\u0026redir_token=QUFFLUhqbkNTZXlDWkJKYWlNbkhOdFlpV2lQLUViYkcyZ3xBQ3Jtc0trTEdQblFaTHd1azBFVXZuaWZGYk50cWs3ZjlieTh3V1ROSnFxbFpyYWhlVUx5QTV5T29kZjFyS3I3YTBGSm1TRDBPZk5QQWRZVmd1dXhXR3U1TzRYeGJjNlJONW9ZT0ZWcE5IYkxycEktSlBKU0Fmdw\u0026q=https%3A%2F%2Flinks.zerotomastery.io%2Fmachine-learning-crash-course\u0026v=r67SfaiYaDI","webPageType":"WEB_PAGE_TYPE_UNKNOWN","rootVe":83769}},"urlEndpoint":{"url":"https://www.youtube.com/redirect?event=video_description\u0026redir_token=QUFFLUhqbkNTZXlDWkJKYWlNbkhOdFlpV2lQLUViYkcyZ3xBQ3Jtc0trTEdQblFaTHd1azBFVXZuaWZGYk50cWs3ZjlieTh3V1ROSnFxbFpyYWhlVUx5QTV5T29kZjFyS3I3YTBGSm1TRDBPZk5QQWRZVmd1dXhXR3U1TzRYeGJjNlJONW9ZT0ZWcE5IYkxycEktSlBKU0Fmdw\u0026q=https%3A%2F%2Flinks.zerotomastery.io%2Fmachine-learning-crash-course\u0026v=r67SfaiYaDI","target":"TARGET_NEW_WINDOW","nofollow":true}}}},{"startIndex":973,"length":40,"onTap":{"innertubeCommand":{"clickTrackingParams":"CN0FEM2rARgBIhMIuNr27pCIkgMVo084BR3S3xyJSLLQ4cTaz7TXrwHKAQTS_0Lw","commandMetadata":{"webCommandMetadata":{"url":"https://www.youtube.com/redirect?event=video_description\u0026redir_token=QUFFLUhqa0xtcUhuOFpMbUdVWTFlYk1XUDZnSXF0bm4zZ3xBQ3Jtc0tsRS1PNlpLakJENnBJSHA2R3BUQjF2cEhwNkR5THB5SUdTbXJobkVia1lNY0ljNUdMZGp4c1J3d3k1d3NwbV9yeThTT0tjeXJDVThtYWhmZ0RRN01lZldTbjBfaDRiUVhDa2hkUzRkbG1SVGNjbWtHdw\u0026q=https%3A%2F%2Fdev.mrdbourke.com%2Fzero-to-mastery-ml%2F\u0026v=r67SfaiYaDI","webPageType":"WEB_PAGE_TYPE_UNKNOWN","rootVe":83769}},"urlEndpoint":{"url":"https://www.youtube.com/redirect?event=video_description\u0026redir_token=QUFFLUhqa0xtcUhuOFpMbUdVWTFlYk1XUDZnSXF0bm4zZ3xBQ3Jtc0tsRS1PNlpLakJENnBJSHA2R3BUQjF2cEhwNkR5THB5SUdTbXJobkVia1lNY0ljNUdMZGp4c1J3d3k1d3NwbV9yeThTT0tjeXJDVThtYWhmZ0RRN01lZldTbjBfaDRiUVhDa2hkUzRkbG1SVGNjbWtHdw\u0026q=https%3A%2F%2Fdev.mrdbourke.com%2Fzero-to-mastery-ml%2F\u0026v=r67SfaiYaDI","target":"TARGET_NEW_WINDOW","nofollow":true}}}},{"startIndex":1043,"length":52,"onTap":{"innertubeCommand":{"clickTrackingParams":"CN0FEM2rARgBIhMIuNr27pCIkgMVo084BR3S3xyJygEE0v9C8A==","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=4uBbCUjJ_G8","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"4uBbCUjJ_G8","startTimeSeconds":0,"watchEndpointSupportedOnesieConfig":{"html5PlaybackOnesieConfig":{"commonConfig":{"url":"https://rr7---sn-ab02a0nfpgxapox-bh26d.googlevideo.com/initplayback?source=youtube\u0026oeis=1\u0026c=WEB\u0026oad=3200\u0026ovd=3200\u0026oaad=11000\u0026oavd=11000\u0026ocs=700\u0026oewis=1\u0026oputc=1\u0026ofpcc=1\u0026msp=1\u0026odepv=1\u0026id=e2e05b0948c9fc6f\u0026ip=1.208.108.242\u0026initcwndbps=4492500\u0026mt=1768293662\u0026oweuc="}}}}}},"onTapOptions":{"accessibilityInfo":{"accessibilityLabel":"YouTube Channel Link: Python 101 Crash Course: Learn Python v3 (8 HOURS!) | Python Course + Projects"}}},{"startIndex":1125,"length":5,"onTap":{"innertubeCommand":{"clickTrackingParams":"CN0FEM2rARgBIhMIuNr27pCIkgMVo084BR3S3xyJygEE0v9C8A==","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=r67SfaiYaDI","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"r67SfaiYaDI","continuePlayback":true,"startTimeSeconds":0,"watchEndpointSupportedOnesieConfig":{"html5PlaybackOnesieConfig":{"commonConfig":{"url":"https://rr8---sn-ab02a0nfpgxapox-jwwk.googlevideo.com/initplayback?source=youtube\u0026oeis=1\u0026c=WEB\u0026oad=3200\u0026ovd=3200\u0026oaad=11000\u0026oavd=11000\u0026ocs=700\u0026oewis=1\u0026oputc=1\u0026ofpcc=1\u0026msp=1\u0026odepv=1\u0026id=afaed27da8986832\u0026ip=1.208.108.242\u0026initcwndbps=3355000\u0026mt=1768293662\u0026oweuc="}}}}}},"onTapOptions":{"accessibilityInfo":{"accessibilityLabel":"0초"}}},{"startIndex":1144,"length":5,"onTap":{"innertubeCommand":{"clickTrackingParams":"CN0FEM2rARgBIhMIuNr27pCIkgMVo084BR3S3xyJygEE0v9C8A==","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=r67SfaiYaDI\u0026t=110s","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"r67SfaiYaDI","continuePlayback":true,"startTimeSeconds":110,"watchEndpointSupportedOnesieConfig":{"html5PlaybackOnesieConfig":{"commonConfig":{"url":"https://rr8---sn-ab02a0nfpgxapox-jwwk.googlevideo.com/initplayback?source=youtube\u0026oeis=1\u0026c=WEB\u0026oad=3200\u0026ovd=3200\u0026oaad=11000\u0026oavd=11000\u0026ocs=700\u0026oewis=1\u0026oputc=1\u0026ofpcc=1\u0026msp=1\u0026odepv=1\u0026id=afaed27da8986832\u0026ip=1.208.108.242\u0026osts=110\u0026initcwndbps=3355000\u0026mt=1768293662\u0026oweuc="}}}}}},"onTapOptions":{"accessibilityInfo":{"accessibilityLabel":"1분 50초"}}},{"startIndex":1165,"length":5,"onTap":{"innertubeCommand":{"clickTrackingParams":"CN0FEM2rARgBIhMIuNr27pCIkgMVo084BR3S3xyJygEE0v9C8A==","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=r67SfaiYaDI\u0026t=350s","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"r67SfaiYaDI","continuePlayback":true,"startTimeSeconds":350,"watchEndpointSupportedOnesieConfig":{"html5PlaybackOnesieConfig":{"commonConfig":{"url":"https://rr8---sn-ab02a0nfpgxapox-jwwk.googlevideo.com/initplayback?source=youtube\u0026oeis=1\u0026c=WEB\u0026oad=3200\u0026ovd=3200\u0026oaad=11000\u0026oavd=11000\u0026ocs=700\u0026oewis=1\u0026oputc=1\u0026ofpcc=1\u0026msp=1\u0026odepv=1\u0026id=afaed27da8986832\u0026ip=1.208.108.242\u0026osts=350\u0026initcwndbps=3355000\u0026mt=1768293662\u0026oweuc="}}}}}},"onTapOptions":{"accessibilityInfo":{"accessibilityLabel":"5분 50초"}}},{"startIndex":1197,"length":5,"onTap":{"innertubeCommand":{"clickTrackingParams":"CN0FEM2rARgBIhMIuNr27pCIkgMVo084BR3S3xyJygEE0v9C8A==","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=r67SfaiYaDI\u0026t=774s","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"r67SfaiYaDI","continuePlayback":true,"startTimeSeconds":774,"watchEndpointSupportedOnesieConfig":{"html5PlaybackOnesieConfig":{"commonConfig":{"url":"https://rr8---sn-ab02a0nfpgxapox-jwwk.googlevideo.com/initplayback?source=youtube\u0026oeis=1\u0026c=WEB\u0026oad=3200\u0026ovd=3200\u0026oaad=11000\u0026oavd=11000\u0026ocs=700\u0026oewis=1\u0026oputc=1\u0026ofpcc=1\u0026msp=1\u0026odepv=1\u0026id=afaed27da8986832\u0026ip=1.208.108.242\u0026osts=774\u0026initcwndbps=3355000\u0026mt=1768293662\u0026oweuc="}}}}}},"onTapOptions":{"accessibilityInfo":{"accessibilityLabel":"12분 54초"}}},{"startIndex":1236,"length":5,"onTap":{"innertubeCommand":{"clickTrackingParams":"CN0FEM2rARgBIhMIuNr27pCIkgMVo084BR3S3xyJygEE0v9C8A==","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=r67SfaiYaDI\u0026t=1077s","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"r67SfaiYaDI","continuePlayback":true,"startTimeSeconds":1077,"watchEndpointSupportedOnesieConfig":{"html5PlaybackOnesieConfig":{"commonConfig":{"url":"https://rr8---sn-ab02a0nfpgxapox-jwwk.googlevideo.com/initplayback?source=youtube\u0026oeis=1\u0026c=WEB\u0026oad=3200\u0026ovd=3200\u0026oaad=11000\u0026oavd=11000\u0026ocs=700\u0026oewis=1\u0026oputc=1\u0026ofpcc=1\u0026msp=1\u0026odepv=1\u0026id=afaed27da8986832\u0026ip=1.208.108.242\u0026osts=1077\u0026initcwndbps=3355000\u0026mt=1768293662\u0026oweuc="}}}}}},"onTapOptions":{"accessibilityInfo":{"accessibilityLabel":"17분 57초"}}},{"startIndex":1281,"length":5,"onTap":{"innertubeCommand":{"clickTrackingParams":"CN0FEM2rARgBIhMIuNr27pCIkgMVo084BR3S3xyJygEE0v9C8A==","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=r67SfaiYaDI\u0026t=1465s","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"r67SfaiYaDI","continuePlayback":true,"startTimeSeconds":1465,"watchEndpointSupportedOnesieConfig":{"html5PlaybackOnesieConfig":{"commonConfig":{"url":"https://rr8---sn-ab02a0nfpgxapox-jwwk.googlevideo.com/initplayback?source=youtube\u0026oeis=1\u0026c=WEB\u0026oad=3200\u0026ovd=3200\u0026oaad=11000\u0026oavd=11000\u0026ocs=700\u0026oewis=1\u0026oputc=1\u0026ofpcc=1\u0026msp=1\u0026odepv=1\u0026id=afaed27da8986832\u0026ip=1.208.108.242\u0026osts=1465\u0026initcwndbps=3355000\u0026mt=1768293662\u0026oweuc="}}}}}},"onTapOptions":{"accessibilityInfo":{"accessibilityLabel":"24분 25초"}}},{"startIndex":1309,"length":5,"onTap":{"innertubeCommand":{"clickTrackingParams":"CN0FEM2rARgBIhMIuNr27pCIkgMVo084BR3S3xyJygEE0v9C8A==","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=r67SfaiYaDI\u0026t=1840s","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"r67SfaiYaDI","continuePlayback":true,"startTimeSeconds":1840,"watchEndpointSupportedOnesieConfig":{"html5PlaybackOnesieConfig":{"commonConfig":{"url":"https://rr8---sn-ab02a0nfpgxapox-jwwk.googlevideo.com/initplayback?source=youtube\u0026oeis=1\u0026c=WEB\u0026oad=3200\u0026ovd=3200\u0026oaad=11000\u0026oavd=11000\u0026ocs=700\u0026oewis=1\u0026oputc=1\u0026ofpcc=1\u0026msp=1\u0026odepv=1\u0026id=afaed27da8986832\u0026ip=1.208.108.242\u0026osts=1840\u0026initcwndbps=3355000\u0026mt=1768293662\u0026oweuc="}}}}}},"onTapOptions":{"accessibilityInfo":{"accessibilityLabel":"30분 40초"}}},{"startIndex":1355,"length":5,"onTap":{"innertubeCommand":{"clickTrackingParams":"CN0FEM2rARgBIhMIuNr27pCIkgMVo084BR3S3xyJygEE0v9C8A==","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=r67SfaiYaDI\u0026t=2118s","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"r67SfaiYaDI","continuePlayback":true,"startTimeSeconds":2118,"watchEndpointSupportedOnesieConfig":{"html5PlaybackOnesieConfig":{"commonConfig":{"url":"https://rr8---sn-ab02a0nfpgxapox-jwwk.googlevideo.com/initplayback?source=youtube\u0026oeis=1\u0026c=WEB\u0026oad=3200\u0026ovd=3200\u0026oaad=11000\u0026oavd=11000\u0026ocs=700\u0026oewis=1\u0026oputc=1\u0026ofpcc=1\u0026msp=1\u0026odepv=1\u0026id=afaed27da8986832\u0026ip=1.208.108.242\u0026osts=2118\u0026initcwndbps=3355000\u0026mt=1768293662\u0026oweuc="}}}}}},"onTapOptions":{"accessibilityInfo":{"accessibilityLabel":"35분 18초"}}},{"startIndex":1388,"length":5,"onTap":{"innertubeCommand":{"clickTrackingParams":"CN0FEM2rARgBIhMIuNr27pCIkgMVo084BR3S3xyJygEE0v9C8A==","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=r67SfaiYaDI\u0026t=2411s","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"r67SfaiYaDI","continuePlayback":true,"startTimeSeconds":2411,"watchEndpointSupportedOnesieConfig":{"html5PlaybackOnesieConfig":{"commonConfig":{"url":"https://rr8---sn-ab02a0nfpgxapox-jwwk.googlevideo.com/initplayback?source=youtube\u0026oeis=1\u0026c=WEB\u0026oad=3200\u0026ovd=3200\u0026oaad=11000\u0026oavd=11000\u0026ocs=700\u0026oewis=1\u0026oputc=1\u0026ofpcc=1\u0026msp=1\u0026odepv=1\u0026id=afaed27da8986832\u0026ip=1.208.108.242\u0026osts=2411\u0026initcwndbps=3355000\u0026mt=1768293662\u0026oweuc="}}}}}},"onTapOptions":{"accessibilityInfo":{"accessibilityLabel":"40분 11초"}}},{"startIndex":1428,"length":5,"onTap":{"innertubeCommand":{"clickTrackingParams":"CN0FEM2rARgBIhMIuNr27pCIkgMVo084BR3S3xyJygEE0v9C8A==","commandMetadata":{"webCommandMetadata":{"url":"/watch?v=r67SfaiYaDI\u0026t=2531s","webPageType":"WEB_PAGE_TYPE_WATCH","rootVe":3832}},"watchEndpoint":{"videoId":"r67SfaiYaDI","continuePlayback":true,"startTimeSeconds":2531,"watchEndpointSupportedOnesieConfig":{"html5PlaybackOnesieConfig":{"commonConfig":{"url":"https://rr8---sn-ab02a0nfpgxapox-jwwk.googlevideo.com/initplayback?source=youtube\u0026oeis=1\u0026c=WEB\u0026oad=3200\u0026ovd=3200\u0026oaad=11000\u0026oavd=11000\u0026ocs=700\u0026oewis=1\u0026oputc=1\u0026ofpcc=1\u0026msp=1\u0026odepv=1\u0026id=afaed27da8986832\u0026ip=1.208.108.242\u0026osts=2531\u0026initcwndbp | 2026-01-13T08:48:28 |
https://stackoverflow.blog/author/pchandrasekar/ | Prashanth Chandrasekar - Stack Overflow Blog Loading… Everything Productivity AI/ML Open Source Business Hub Company Releases Podcast Newsletter Stack Overflow Business Stack Internal : the knowledge intelligence layer that powers enterprise AI. Stack Data Licensing : decades of verified, technical knowledge to boost AI performance and trust. Stack Ads : engage developers where it matters — in their daily workflow. Staff Prashanth Chandrasekar December 30, 2025 A new era of Stack Overflow Live from the stage of WeAreDevelopers, we’re unveiling our new vision and mission for the future of Stack Overflow and our community. Prashanth Chandrasekar , Jody Bailey 11 comment s Company December 2, 2025 Disrupting yourself in the age of AI The internet is facing a fundamental shift—and the way we measure success online is shifting too. Reach, trust, attribution, and influence are the new metrics to measure against in the post GenAI era. Prashanth Chandrasekar 1 comment generative AI artificial intelligence traffic Company May 20, 2025 CEO Update: Exploration and experimentation for bold evolution As we envision what the ideal future version of Stack Overflow looks like, we’re committed to engaging with our community. Prashanth Chandrasekar 5 comment s ceo quarterly post Company May 8, 2025 A new look for what’s next The world has changed a lot since Stack Overflow started. It's time for our brand to change with it. Prashanth Chandrasekar , David Longworth 8 comment s Company brand February 27, 2025 Our next phase—Q&A was just the beginning For those that missed our February AMA, let’s discuss the future of Stack Overflow Prashanth Chandrasekar , Philippe Beaudette 16 comment s Community Company February 6, 2025 Investing in the Stack Exchange Network and the future of Stack Overflow Mark your calendars to learn more about Stack’s Future—Feb 26th. Prashanth Chandrasekar 6 comment s Community October 22, 2024 CEO Update: Building trust in AI is key to a thriving knowledge ecosystem The internet and its business models are changing. Stack Overflow has been at the forefront, helping to shape the future of the web. Prashanth Chandrasekar 5 comment s ceo quarterly post Knowledge as a service Company November 15, 2023 CEO update: Giving thanks and building upon our product & engineering foundation We're looking across the calendar year and seeing how much our team has accomplished and where we need to double down on efforts in the months ahead. Prashanth Chandrasekar 0 comment s ceo quarterly post Company October 16, 2023 A Message from Prashanth Chandrasekar, CEO Stack Overflow Over the last 15 years, we’ve built Stack Overflow into an industry-crucial knowledge base for millions of developers and technologists. During this time we’ve experienced years filled with opportunities and challenges. This year is no different. Prashanth Chandrasekar Company July 27, 2023 Announcing OverflowAI Let’s highlight the new features and products we announced today from the stage of WeAreDevelopers. Prashanth Chandrasekar 23 comment s AI Announcements Community Company ide Stack Internal overflow ai May 31, 2023 CEO Update: Paving the road forward with AI and community at the center With all the significant changes in the industry, one thing has remained the same: companies are committed to driving productivity and efficiency throughout their organizations, and we continue to help our customers and community deliver both. Prashanth Chandrasekar 0 comment s ceo quarterly post Company May 10, 2023 A Message from Prashanth Chandrasekar, CEO Stack Overflow An update from our CEO. Prashanth Chandrasekar 0 comment s Uncategorized April 17, 2023 Community is the future of AI To keep knowledge open and accessible to all, we must come together to build the future of AI. Prashanth Chandrasekar 16 comment s Announcements Announcements Community Company January 31, 2023 CEO update: Eliminating obstacles to productivity, efficiency, and learning It was a busy and successful quarter, so although my first update of 2023 takes place in a fundamentally different environment than my first of 2022, my optimism for the future has not changed. It’s simply joined by a dose of pragmatism. Prashanth Chandrasekar 0 comment s ceo quarterly post Company October 26, 2022 CEO update: Breaking down barriers to unlock innovation We’re fortunate to continue to grow at a rapid pace. In dynamic times, whether it be in times of hyper growth or in times of market volatility, we are seeing from our community and customers alike that breaking down the barriers to knowledge is essential for success. Prashanth Chandrasekar 1 comment ceo quarterly post Company July 27, 2022 Always learning It’s been a busy quarter for the company. We celebrated a handful of big milestones over the last three months. We added a new Chief Technology Officer, Jody Bailey, to our leadership team, announced Stack Overflow for Teams entering the Microsoft Azure Marketplace, launched exciting initiatives like Staging Ground, and released insights from this year’s Developer Survey. Prashanth Chandrasekar 0 comment s Announcements Announcements ceo quarterly post collectives Community Community Company Culture developer survey Diversity Stack Internal April 28, 2022 Agility starts with trust Prashanth Chandrasekar 3 comment s ceo quarterly post Company January 26, 2022 Keeping technologists in the flow state It’s hard to believe we’re already four weeks into the New Year, especially as everything we have to celebrate from 2021 is still fresh in my mind. Prashanth Chandrasekar 1 comment Company Company winter bash October 27, 2021 Strong teams are more than just connected, they are communities Organizations and leaders have a responsibility to ensure people are heard, to build high levels of trust and enable them to show up authentically— all so they can do their best work. Prashanth Chandrasekar 4 comment s ceo quarterly post Community Company August 2, 2021 Communities are a catalyst for technology development It's a big day at Stack Overflow! Our Prosus deal has closed and our latest Dev Survey is live. Prashanth Chandrasekar 2 comment s Announcements Announcements Community Community Company June 2, 2021 Prosus’s Acquisition of Stack Overflow: Our Exciting Next Chapter This morning, Prosus (PROSY) has announced its intention to acquire Stack Overflow for 1.8 billion dollars. This is tremendously exciting news for our employees, our customers, our community members, and for our shareholders, and I will share a bit more about what it all means. Prashanth Chandrasekar 29 comment s announcement Announcements Company Company prosus stack overflow April 26, 2021 Accelerating Stack Overflow’s transformation This quarter's post from our CEO focuses on two strategic priorities: Product-led Transformation and Predictable and Reliable Financial Performance, both of which add value to our community and our customers by allowing us to continue to support and resource them better. Prashanth Chandrasekar 0 comment s ceo quarterly post Company April 7, 2021 An update on our product-led SaaS transformation Prashanth Chandrasekar 2 comment s Company Company January 27, 2021 Building momentum in our transition to a product led SaaS company We're excited to share our latest results and our plans for the future. Prashanth Chandrasekar 1 comment Company Stack Internal Show more Our Stack Stack Internal Features Customers Security Pricing Stack Data Licensing Stack Ads Partnerships Services Stack Overflow Company Leadership Press Careers Social Impact Support Contact Stack Overflow help Stack Internal help Terms Privacy policy Cookie policy Your Privacy Choices Elsewhere Blog Dev Newsletter Podcast Releases Dev Survey Site design / logo © 2026 Stack Exchange Inc. Light Dark Auto | 2026-01-13T08:48:28 |
https://www.linkedin.com/legal/cookie-policy?trk=linkedin-tc_auth-button_cookie-policy | Cookie Policy | LinkedIn Skip to main content User Agreement Summary of User Agreement Privacy Policy Professional Community Policies Cookie Policy Copyright Policy Regional Info EU Notice California Privacy Disclosure U.S. State Privacy Laws User Agreement Summary of User Agreement Privacy Policy Professional Community Policies Cookie Policy Copyright Policy Regional Info EU Notice California Privacy Disclosure U.S. State Privacy Laws Cookie Policy Effective on June 3, 2022 At LinkedIn, we believe in being clear and open about how we collect and use data related to you. This Cookie Policy applies to any LinkedIn product or service that links to this policy or incorporates it by reference. We use cookies and similar technologies such as pixels, local storage and mobile ad IDs (collectively referred to in this policy as “cookies”) to collect and use data as part of our Services, as defined in our Privacy Policy (“Services”) and which includes our sites, communications, mobile applications and off-site Services, such as our ad services and the “Apply with LinkedIn” and “Share with LinkedIn” plugins or tags. In the spirit of transparency, this policy provides detailed information about how and when we use these technologies. By continuing to visit or use our Services, you are agreeing to the use of cookies and similar technologies for the purposes described in this policy. What technologies are used? ENTER A SUMMARY Type of technology Description Cookies A cookie is a small file placed onto your device that enables LinkedIn features and functionality. Any browser visiting our sites may receive cookies from us or cookies from third parties such as our customers, partners or service providers. We or third parties may also place cookies in your browser when you visit non-LinkedIn sites that display ads or that host our plugins or tags . We use two types of cookies: persistent cookies and session cookies. A persistent cookie lasts beyond the current session and is used for many purposes, such as recognizing you as an existing user, so it’s easier to return to LinkedIn and interact with our Services without signing in again. Since a persistent cookie stays in your browser, it will be read by LinkedIn when you return to one of our sites or visit a third party site that uses our Services. Session cookies last only as long as the session (usually the current visit to a website or a browser session). Pixels A pixel is a tiny image that may be embedded within web pages and emails, requiring a call (which provides device and visit information) to our servers in order for the pixel to be rendered in those web pages and emails. We use pixels to learn more about your interactions with email content or web content, such as whether you interacted with ads or posts. Pixels can also enable us and third parties to place cookies on your browser. Local storage Local storage enables a website or application to store information locally on your device(s). Local storage may be used to improve the LinkedIn experience, for example, by enabling features, remembering your preferences and speeding up site functionality. Other similar technologies We also use other tracking technologies, such as mobile advertising IDs and tags for similar purposes as described in this Cookie Policy. References to similar technologies in this policy includes pixels, local storage, and other tracking technologies. Our cookie tables lists cookies and similar technologies that are used as part of our Services. Please note that the names of cookies and similar technologies may change over time. What are these technologies used for? Below we describe the purposes for which we use these technologies. ENTER SUMMARY Purpose Description Authentication We use cookies and similar technologies to recognize you when you visit our Services. If you’re signed into LinkedIn, these technologies help us show you the right information and personalize your experience in line with your settings. For example, cookies enable LinkedIn to identify you and verify your account. Security We use cookies and similar technologies to make your interactions with our Services faster and more secure. For example, we use cookies to enable and support our security features, keep your account safe and to help us detect malicious activity and violations of our User Agreement. Preferences, features and services We use cookies and similar technologies to enable the functionality of our Services, such as helping you to fill out forms on our Services more easily and providing you with features, insights and customized content in conjunction with our plugins. We also use these technologies to remember information about your browser and your preferences. For example, cookies can tell us which language you prefer and what your communications preferences are. We may also use local storage to speed up site functionality. Customized content We use cookies and similar technologies to customize your experience on our Services. For example, we may use cookies to remember previous searches so that when you return to our services, we can offer additional information that relates to your previous search. Plugins on and off LinkedIn We use cookies and similar technologies to enable LinkedIn plugins both on and off the LinkedIn sites. For example, our plugins, including the "Apply with LinkedIn" button or the "Share" button may be found on LinkedIn or third-party sites, such as the sites of our customers and partners. Our plugins use cookies and other technologies to provide analytics and recognize you on LinkedIn and third-party sites. If you interact with a plugin (for instance, by clicking "Apply"), the plugin will use cookies to identify you and initiate your request to apply. You can learn more about plugins in our Privacy Policy . Advertising Cookies and similar technologies help us show relevant advertising to you more effectively, both on and off our Services and to measure the performance of such ads. We use these technologies to learn whether content has been shown to you or whether someone who was presented with an ad later came back and took an action (e.g., downloaded a white paper or made a purchase) on another site. Similarly, our partners or service providers may use these technologies to determine whether we've shown an ad or a post and how it performed or provide us with information about how you interact with ads. We may also work with our customers and partners to show you an ad on or off LinkedIn, such as after you’ve visited a customer’s or partner’s site or application. These technologies help us provide aggregated information to our customers and partners. For further information regarding the use of cookies for advertising purposes, please see Sections 1.4 and 2.4 of the Privacy Policy . As noted in Section 1.4 of our Privacy Policy, outside Designated Countries , we also collect (or rely on others who collect) information about your device where you have not engaged with our Services (e.g., ad ID, IP address, operating system and browser information) so we can provide our Members with relevant ads and better understand their effectiveness. For further information, please see Section 1.4 of the Privacy Policy . Analytics and research Cookies and similar technologies help us learn more about how well our Services and plugins perform in different locations. We or our service providers use these technologies to understand, improve, and research products, features and services, including as you navigate through our sites or when you access LinkedIn from other sites, applications or devices. We or our service providers, use these technologies to determine and measure the performance of ads or posts on and off LinkedIn and to learn whether you have interacted with our websites, content or emails and provide analytics based on those interactions. We also use these technologies to provide aggregated information to our customers and partners as part of our Services. If you are a LinkedIn member but logged out of your account on a browser, LinkedIn may still continue to log your interaction with our Services on that browser until the expiration of the cookie in order to generate usage analytics for our Services. We may share these analytics in aggregate form with our customers. What third parties use these technologies in connection with our Services? Third parties such as our customers, partners and service providers may use cookies in connection with our Services. For example, third parties may use cookies in their LinkedIn pages, job posts and their advertisements on and off LinkedIn for their own marketing purposes. For an illustration, please visit LinkedIn’s Help Center . Third parties may also use cookies in connection with our off-site Services, such as LinkedIn ad services. Third parties may use cookies to help us to provide our Services. We may also work with third parties for our own marketing purposes and to enable us to analyze and research our Services. Your Choices You have choices on how LinkedIn uses cookies and similar technologies. Please note that if you limit the ability of LinkedIn to set cookies and similar technologies, you may worsen your overall user experience, since it may no longer be personalized to you. It may also stop you from saving customized settings like login information. Opt out of targeted advertising As described in Section 2.4 of the Privacy Policy , you have choices regarding the personalized ads you may see. LinkedIn Members can adjust their settings here . Visitor controls can be found here . Some mobile device operating systems such as Android provide the ability to control the use of mobile advertising IDs for ads personalization. You can learn how to use these controls by visiting the manufacturer’s website. We do not use iOS mobile advertising IDs for targeted advertising. Browser Controls Most browsers allow you to control cookies through their settings, which may be adapted to reflect your consent to the use of cookies. Further, most browsers also enable you to review and erase cookies, including LinkedIn cookies. To learn more about browser controls, please consult the documentation that your browser manufacturer provides. What is Do Not Track (DNT)? DNT is a concept that has been promoted by regulatory agencies such as the U.S. Federal Trade Commission (FTC), for the Internet industry to develop and implement a mechanism for allowing Internet users to control the tracking of their online activities across websites by using browser settings. As such, LinkedIn does not generally respond to “do not track” signals. Other helpful resources To learn more about advertisers’ use of cookies, please visit the following links: Internet Advertising Bureau (US) European Interactive Digital Advertising Alliance (EU) Internet Advertising Bureau (EU) LinkedIn © 2026 About Accessibility User Agreement Privacy Policy Cookie Policy Copyright Policy Brand Policy Guest Controls Community Guidelines العربية (Arabic) বাংলা (Bangla) Čeština (Czech) Dansk (Danish) Deutsch (German) Ελληνικά (Greek) English (English) Español (Spanish) فارسی (Persian) Suomi (Finnish) Français (French) हिंदी (Hindi) Magyar (Hungarian) Bahasa Indonesia (Indonesian) Italiano (Italian) עברית (Hebrew) 日本語 (Japanese) 한국어 (Korean) मराठी (Marathi) Bahasa Malaysia (Malay) Nederlands (Dutch) Norsk (Norwegian) ਪੰਜਾਬੀ (Punjabi) Polski (Polish) Português (Portuguese) Română (Romanian) Русский (Russian) Svenska (Swedish) తెలుగు (Telugu) ภาษาไทย (Thai) Tagalog (Tagalog) Türkçe (Turkish) Українська (Ukrainian) Tiếng Việt (Vietnamese) 简体中文 (Chinese (Simplified)) 正體中文 (Chinese (Traditional)) Language | 2026-01-13T08:48:28 |
https://www.devcycle.com/pricing | Pricing | DevCycle Product Solutions Resources Pricing Docs Book Demo Login Create Account Powerful Feature Flags. Fair Pricing. DevCycle is affordable on all plans. With all the features your team needs and none you don't. Monthly Use setting Annually (Save 20%) Free $0 No credit card required For small projects, or people that just want to give DevCycle a try. Unlimited Seats Up to 1,000 Client-side MAUs A Monthly Active User (MAU) is a unique user with at least one Client-Side SDK initialization in a month. All the features you need to get started. Get Started Core Features, including Unlimited Seats Unlimited Flags All Integrations A/B Testing MCP Server ...and more Developer $ 10 Per Month, Billed Annually For startups who are trying to improve their development process. Unlimited Seats 1,000 MAUs Included A Monthly Active User (MAU) is a unique user with at least one Client-Side SDK initialization in a month. 10,000 Events per Month Included Pricing Estimate: 1,000 MAUs Create Account Everything in Free, plus AI Generated Feature Summaries AI Generated Schemas Audit Logging Feature Opt-in Flag Schemas Custom Property Schemas Business $ 500 Per Month, Billed Annually For organizations with multiple teams that need permissions. Unlimited Seats 100,000 MAUs Included A Monthly Active User (MAU) is a unique user with at least one Client-Side SDK initialization in a month 500,000 Events per Month Included Pricing Estimate: 100,000 MAUs Create Account Everything in Developer, plus Roles & Permissions Stale Flag Detection Custom Property Storage (EdgeDB) Custom Domain Proxy Enterprise Custom Billed Annually For enterprise teams that have strict governance and SLA requirements. Unlimited Seats Custom plans with no limits Contact our team to build a custom plan suited to your needs. Book a Call Everything in Business, plus Approval Workflows Custom SSO/SAML SCIM Provisioning 3rd Party Data ETL Event Relay Proxy Premium Support Uptime SLA Pricing that grows with your business DevCycle Feature List Free Developer Business Enterprise Pricing Breakdown Base Price Free $12.50 / month $625 / month Custom Client-Side MAUs 1,000 Included 1,000 Included then $7.00 per 1,000 100,000 Included then $2.50 per 1,000 Custom Cloud Config Requests 10,000 / month Included 10,000 / month Included then $6 per 10,000 1,000,000 / month Included then $2 per 10,000 Custom Server Config Requests 100,000 / month Included 100,000 / month Included then $6 per 100,000 10,000,000 / month Included then $2 per 100,000 Custom Events 5,000 / month Included 10,000 / month Included then $1 per 10,000 500,000 / month Included then $0.5 per 10,000 Custom Core Features Feature Flags Unlimited Unlimited Unlimited Unlimited Seats Unlimited Unlimited Unlimited Unlimited Environments Unlimited Unlimited Unlimited Unlimited Projects Unlimited Unlimited Unlimited Unlimited A/B Testing & Experimentation Debugging Tools All Integrations Real-Time Updates Targeting & Segmentation Percentage-Based Rollouts Global Flag State Visibility OpenFeature Support Across All SDKs REST API CLI Advanced Features Variable Types Multi-Step Rollouts Rollouts by Custom Property Reusable Audiences Custom Property Targeting One-Click Self Targeting Flag Name Obfuscation Realtime Updates Feature Opt-in Custom Property Schemas Flag Schemas Stale Flag Detection/Notification EdgeDB (Stored Custom Properties) Roles & Permissions Approval Workflows AI-Enabled Features MCP Server AI Generated Feature Summaries AI Generated Schemas Workflow Tools Embedded Debugging Tools Code Generation Tools Flag Importer Code Pipeline Integrations Code References Webhooks VS Code Extension Terraform Provider Slack App Snowflake Data Sharing 3rd party ETL Security & Compliance SOC 2 Type 2 Certified Audit Logging Custom Domain Proxy SAML SSO SCIM Provisioning SDK Proxy Implementation Support & Service Guarantees Discord Community Email Support Shared Slack Channel Custom Migration Support First Reply SLA Uptime SLA Custom Legal Terms Frequently Asked Questions What is a Monthly Active User (MAU)? A Monthly Active User (MAU) is a unique user ID that has at least one Client-Side SDK initialization in a month. What is a Cloud Config Request? A Cloud Config Request happens on initialization or identification update of a client-side SDK such as web and mobile, as well as all calls to our Bucketing API or our server-side SDKs, when configured to run in cloud-bucketing mode. All of these calls grab the latest Feature Flag value/configuration from DevCycle's Edge Workers. What is a Server Config Request? A Server Config Request is a request to the DevCycle config CDN to fetch the latest project Configuration by any of our local bucketing server-side SDKs whether on startup, via polling or triggered by an SSE event. What is an Event? An Event is a single data point sent to DevCycle using the Track API or Track function in our SDKs. These can be any custom event whether tracking conversions or latency. Events serve as a foundation for creating custom metrics. NOTE: Tracking that is built into the DevCycle SDK does not count against billable events. What is EdgeDB? EdgeDB is a lightning-fast, globally replicated edge storage tool that allows you to store information about your users for future use in Targeting Rules. For example, you can set a custom property when a user performs a key action in your application, and then target based on that property in the future without having to continuously provide that data in the SDK. How are Overages Billed? The Developer and Business plans include a set number of Client-Side MAUs, Cloud Config Requests, Server Config Requests, and Events. If you exceed these limits, you'll be billed monthly at the rate specified for your plan, subject to applicable annual discounts. Build Better Software With DevCycle DevCycle is designed from the ground up to help you ship better software, faster. Sign up today and start improving your software development process. Create Account Book a Demo Footer DevCycle What are Feature Flags? OpenFeature Create a Free Account Request a Demo Pricing Resources Documentation SDKs APIs Integrations Blog Contact Support Company About Us Careers Terms of Service Security & Compliance Privacy Policy Contact Us Discord X GitHub LinkedIn Bluesky © 2026 DevCycle All rights reserved. | 2026-01-13T08:48:28 |
https://stackoverflow.blog/documentation/ | documentation - Stack Overflow Blog Loading… Everything Productivity AI/ML Open Source Business Hub Company Releases Podcast Newsletter Stack Overflow Business Stack Internal : the knowledge intelligence layer that powers enterprise AI. Stack Data Licensing : decades of verified, technical knowledge to boost AI performance and trust. Stack Ads : engage developers where it matters — in their daily workflow. documentation Subscribe to the podcast Get The Stack Overflow Podcast at your favorite listening service. Apple Podcasts Overcast Overcast Pocket Casts Spotify RSS feed January 1, 2026 Documents: The architect’s programming language Senior developers know how to deploy code to systems made of code. Architects know how to deploy ideas to systems made of people. Isaac Lyman 2 comment s architecture documentation October 6, 2025 Beyond code generation: How AI is changing tech teams' dynamics While AI coding assistants are helping developers become more productive, the true value of AI lies in its ability to automate the non-coding tasks that have historically been bottlenecks, allowing leaders to create more agile teams and focus on higher-level strategic problems. Phoebe Sajor 1 comment Business Hub AI documentation generative AI ai coding autonomous agents workflow automation December 19, 2024 Why do developers love clean code but hate writing documentation? It's time to delegate to the robots. Ben Popper 33 comment s documentation code quality ai coding Business Hub November 26, 2024 Your docs are your infrastructure Fabrizio Ferri-Benedetti, who spent many years as a technical writer for Splunk and New Relic, joins Ben and Ryan for a conversation about the evolving role of documentation in software development. They explore how documentation can (and should) be integrated with code, the importance of quality control, and the hurdles to maintaining up-to-date documentation. Plus: Why technical writers shouldn’t be afraid of LLMs. Eira May 2 comment s The Stack Overflow Podcast llm AI generative AI documentation technical writing software development December 21, 2022 I spent two years trying to do what Backstage does for free Absent a time machine, telling others how to avoid my mistakes is the best I can do. Ryan Donovan 7 comment s Code for a Living developer experience documentation June 21, 2022 Experts from Stripe and Waymo explain how to craft great documentation (Ep. 455) We chat with Jared Bhatti and Zachary Sarah Corleissen, two technical writers with deep experience at major tech companies and open source projects, about their approach to documentation and the new book they helped co-author, Doc For Devs. Eira May 5 comment s docs for devs documentation technical writing The Stack Overflow Podcast the stack overflow podcast May 2, 2022 Building a community of open-source documentation contributors When your open-source project starts getting contributors, it can feel great! But as a project grows, contributors can neglect to document everything. Jared Bhatti , Zachary Sarah Corleissen 3 comment s Code for a Living Community documentation Open Source contributed April 25, 2022 Empathy for the Dev: Avoiding common pitfalls when communicating with developers All too often, developers go deep on the wrong things, when writing documentation. A little bit of empathy can get your docs back on track. Heidi Waterhouse 15 comment s Code for a Living documentation empathy contributed December 21, 2021 “This should never happen. If it does, call the developers.” If there is one thing developers like less than writing documentation, it's responding to unnecessary escalations. 26 comment s Code for a Living devops documentation sre September 28, 2020 How Stackers ditched the wiki and migrated to Articles In an effort to rethink how documentation works, we recently introduced Articles, longer-form prose that can sit side by side with shorter Q&A. Ben Popper , Medi Madelen Gwosdz 18 comment s articles Code for a Living Company documentation Stack Internal July 13, 2020 Tales from documentation: Write for your clueless users When you're documenting anything technical, it's easy to forget what it's like being ignorant of how the software works, especially if you built the thing. Ryan Donovan 44 comment s Code for a Living documentation Show more Our Stack Stack Internal Features Customers Security Pricing Stack Data Licensing Stack Ads Partnerships Services Stack Overflow Company Leadership Press Careers Social Impact Support Contact Stack Overflow help Stack Internal help Terms Privacy policy Cookie policy Your Privacy Choices Elsewhere Blog Dev Newsletter Podcast Releases Dev Survey Site design / logo © 2026 Stack Exchange Inc. Light Dark Auto | 2026-01-13T08:48:28 |
https://www.facebook.com/r.php?r=101#sharing-partner-information | Facebook 한국어 English (US) Tiếng Việt Bahasa Indonesia ภาษาไทย Español 中文(简体) 언어 더 보기... 가입하기 로그인 Messenger Facebook Lite 동영상 Meta Pay Meta 스토어 Meta Quest Ray-Ban Meta Meta AI Meta AI 콘텐츠 더 보기 Instagram Threads 투표 정보 센터 개인정보처리방침 개인정보 보호 센터 정보 광고 만들기 페이지 만들기 개발자 채용 정보 쿠키 AdChoices 약관 고객 센터 연락처 업로드 및 비사용자 Meta © 2026 Facebook에서 시작하기 계정을 만들어 친구, 가족 및 같은 관심사를 가진 사람들의 커뮤니티와 소통해보세요. 이름 성 이름 생년월일 성별 성별 선택 휴대폰 번호 또는 이메일 주소 휴대폰 번호 또는 이메일 주소 회원님은 저희가 보내는 알림을 받을 수 있습니다. 회원님의 연락처 정보가 필요한 이유를 알아보세요 비밀번호 비밀번호 저희 서비스를 이용하는 사람이 회원님의 연락처 정보를 Facebook에 업로드했을 수도 있습니다. 더 알아보기 . 회원님은 저희가 보내는 SMS를 받을 수 있으며 언제든지 이를 수신 거부할 수 있습니다. 더 알아보기 제출 이미 계정이 있습니다 | 2026-01-13T08:48:28 |
https://stackoverflow.blog/2026/01/02/a-new-worst-coder-has-entered-the-chat-vibe-coding-without-code-knowledge/#comments | A new worst coder has entered the chat: vibe coding without code knowledge - Stack Overflow Blog Loading… Everything Productivity AI/ML Open Source Business Hub Company Releases Podcast Newsletter Stack Overflow Business Stack Internal : the knowledge intelligence layer that powers enterprise AI. Stack Data Licensing : decades of verified, technical knowledge to boost AI performance and trust. Stack Ads : engage developers where it matters — in their daily workflow. January 2, 2026 A new worst coder has entered the chat: vibe coding without code knowledge In the age of AI, being able to make applications and create code has never been easier. But is it any good? Here's what vibe coding is like for someone without technical skills. [Ed. note: While we take some time to rest up over the holidays and prepare for next year, we are re-publishing our top ten posts for the year. Please enjoy our favorite work this year and we’ll see you in 2026.] If I asked you to guess the job title of someone coding an app for work, your first guess probably wouldn’t be “writer”. It probably wouldn’t be your second or fifth guess either. The fact I wouldn’t be the first person you think of doesn’t offend me. None of my resumes have ever listed coding expertise as a skill. Most of what I know I picked up through work, which necessitates an understanding of technical language and an interest in programming trends. A little of what I know is osmosis from living in the Bay Area, where tech conversations are unavoidable for anyone with a social life. But life is full of little surprises, and one of those is that I did in fact create an app for work. I’ll add an unsurprising caveat: I didn’t actually code it—instead it was created completely through vibes, doing what a lot of code curious folks are doing with vibe coding apps like Bolt. Is vibe coding as powerful as it seems? “ Vibe coding ” as a concept only emerged in early 2025, but it’s already one of the most talked-about usages of large language models. It’s sparked a lot of debate on its effectiveness as a tool for coding and a lot of anxiety over how it will change the tech landscape, especially for junior developers . Even for experienced developers, it holds the existential threat of imposter syndrome , and past that complete replacement. The promise that vibe coding will give anyone, even those with a nontechnical background, the power to create their own usable applications is also debatable. I can say that from my own experience. It felt like hitting one of those “That was easy!” buttons from Staples. But it was too easy, and immediately upon handing the output over to someone with more technical expertise than me, the holes began to show. While it may be a powerful tool in the hands of someone who knows what they’re doing, in my hands it was like one of those AI filters that makes you look like a Studio Ghibli character: fun to post, but not actually substantive. Creating the “Do Not Go In There” app I created my “app” as part of Bolt’s Hackathon . In collaboration with Reddit, the contest prompt was to create something silly that was irreverent and overall useless. I often have useless ideas, so it was perfect for me. “It’s like Yelp but for bathrooms. And it’s for the worst bathrooms in the world,” I told my mom. “Uh, what do you do for work again?” she replied. The process for getting started was fairly easy. Or, it should have been fairly easy. For someone who doesn’t know where the terminal is on her computer, it was not. Devpost, the hosts of the contest, touted that it would take me less than one minute to start building my application with Bolt. They had provided several resources for me to look through, including links to Reddit’s Developer Quickstart. I ended up sinking a lot of time into that particular resource because I didn’t know what I was doing. I’ll take this time to formally apologize to the Help Desk at Stack Overflow for trying to download node . js onto my work laptop even though I definitely didn’t need it. When I figured out that Bolt could do everything I needed, it became much easier. That is a true statement, by the way. Bolt can create a simple app end-to-end almost seamlessly, as long as the person doing it has a rudimentary knowledge of code or clear instructions on what to run. I fell into the second category; I didn’t have a clue about what commands I would need to make the program work until I read one of the Devpost resources. Whether the app would be any good was what I would find out. Bolt’s interface is sleek and intuitive, with a live preview of your creation on the side. It also allows you to look through your codebase and manually update lines as needed. For my purposes, I used the natural language prompt box, which came with some tips for efficient prompt engineering. I used none of them. My prompt was simply, “Create an app for Reddit that’s like Yelp but for bad bathrooms.” (Come on, it’s a joke app for bathrooms; I don’t have to be an eloquent prompt engineer.) My friendly vibe coding AI immediately started working, creating folders to dump code into. All in all, it took about ten minutes to create the foundation of what I had asked for. The app was launchable on my tester subreddit, including a slightly silly UI that used a toilet emoji. It had a place to leave reviews, a rating scale, and a page that would populate with reviews as people wrote them. All of these things were automatically created in a lovely little UI I could click around in on my tester Subreddit. It also didn’t work at all. Almost immediately, error messages popped up in both my Bolt interface and the app itself. No matter how much I tried, I couldn’t upload a bathroom review. I got several error messages in scary red text telling me that location services weren’t available and that I wouldn’t be able to upload a review. Although it had hardly been any work on my end, I did feel the sting of defeat. So I told my Bolt AI, “The app doesn’t work.” What came was about 45 minutes of troubleshooting, where the AI told me exactly where to find error messages. I didn’t have to understand any of them myself; I just had to paste them into the dialogue box verbatim, unformatted, and Bolt would deal with the issue. And while Bolt did provide me with information on what it had fixed, it wasn’t useful to me as a non-coder, who didn’t know what it meant when API endpoints were not being served at the root level. I’m sure if I had any understanding of what exactly was happening inside my app, I could ask it to dig deeper, but the whole point of this experiment was that I didn’t . My lack of understanding went beyond the codebase and to some of the basics of testing and working with my app. For instance, I didn’t realize the `npm run dev` command would update the existing tester app in my tester subreddit. I thought I had to relaunch and repost the app every time edits were made to test a new “version” of the app. In my head, each version of the app was its own respective entity, as opposed to an evolving application that would update itself. Because of this, my tester subreddit had 20 posts on it by the time I had an actual working toilet app. But Bolt was a powerful helper. I cannot overstate how lost I was in the process of creating this application and how easy Bolt made it for me to make something. It even helped me make simple changes to the interface, allowing me to play with the design in a way that was more comfortable for me as someone with a graphic design background. Eventually, I made something that worked, with the use of the word “I” being loose. Really, Bolt had created something; all I had done was give it a prompt and feed it error messages when it asked me to. With each iteration of the application, more and more started to work. I was able to input information, look through reviews, and even add little flourishes like a Bolt badge and different review options. But even with the app live and working , was it any good? Sharing the fruits of my non-labor I felt I had fulfilled the challenge posed by the hackathon competition: I had created something silly, irreverent, and totally useless. Immediately, my coworkers started inputting some of their least favorite bathrooms. It was a ball, for sure. When I met with Ryan Donovan , who you definitely know if you’ve ever listened to our podcast or read anything on the blog, to review my app, the holes started showing immediately. To start with, he was pleasantly [ Ed. note: I don’t know if “pleasantly” is the right word here ] surprised by how many technologies were being used in my simple app. He asked if I knew what JSON or Redis were, as they were both formats being used to run my toilet application. My answer was a resounding no. Ryan didn’t even need to look at my actual code to find issues. He could find glaring ones just from visiting my testing Subreddit and hitting the inspect feature. He let me know right away that my application was ripe for hacking, as there were no security features present to stop someone from accessing any of the data it was storing. This is obviously a big deal, but I’ll get back to it later. As part of my edification, Ryan suggested I get feedback on the code itself. He mentioned posting it publicly to GitHub and asking the community to give me feedback, but as I started to understand just how bad what I had created was, I shied away from the idea of a public lashing. It wasn’t that I was afraid to kill my darling; in fact, there was no darling to be killed. It was more of a simmering feeling of dread, the kind one gets when they know they didn’t do their homework very well and are afraid of what the teacher will say. Luckily, I live in the Bay Area, which means almost all my friends are developers. So before I let strangers play around in my code, I turned to them. It was a cowardly move, because the added layer of context meant that my friends would go easy on me, knowing that my creation was vibe coded and that I probably didn’t understand any of the feedback they were giving me. The main piece of feedback from my friends was that the code was messy and nearly impossible to understand. I intentionally gave them little context on what was being built, instead letting the ` .readme ` that Bolt created for my project speak for itself. The lack of organization started there, mainly because I have no experience using GitHub. “You have a nice readme, but for some reason you buried everything inside ` ./project` ,” one of my friends, a software engineer in Palo Alto, wrote. “Would you consider putting all that stuff in the top level, so people can see everything automatically when they visit your repo?” Another friend wrote, “All the styling is inlined into the ` tsx ` components, which makes it much more cluttered/hard to read.” I didn’t know if that meant I had done something wrong in my GitHub upload or if the code itself was the issue. Her overarching piece of feedback was that the code wasn’t created in a way that facilitated feedback or understanding: “For example, the block of code that is returned from ` LocationDetails.tsx ` is huge. I would split it into several smaller components.” Then at the end she added, “There are no unit tests .” I took this to mean that she couldn’t understand if the components of what I had created even made sense, or could exist on their own. That, I thought to myself, was probably not good. An unmet promise A clear disconnect then stood out to me between the vibe coding of this app and the actual practiced work of coding. Because this app existed solely as an experiment for myself, the fact that it didn’t work so well and the code wasn’t great didn’t really matter. But vibe coding isn’t being touted as “a great use of AI if you’re just mucking about and don’t really care.” It’s supposed to be a tool for developer productivity, a bridge for nontechnical people into development, and someday a replacement for junior developers. That was the promise. And, sure, if I wanted to, I could probably take the feedback from my software engineer pals and plug it into Bolt. One of my friends recommended adding “descriptive class names” to help with the readability, and it took almost no time for Bolt to update the code. It even had an innate understanding of why I might want to add descriptive classnames, something I wouldn’t have understood unless my friend had explained it to me. But what if I wasn’t someone with developer friends? What if the project I was working on wasn’t just for the fun of it but instead something I was really passionate about, or even wanted to bring to market? The mess of my code would be a problem in any of those situations. Even though I made something that worked , did it really? Had this been a real work project, a developer would have had to come in after the fact to clean up everything I had made, lest future developers be lost in the mayhem of my creation. This is called the “ productivity tax ,” the biggest frustration that developers have with AI tools, because they spit out code that is almost—but not quite—right. Our Developer Survey found that 66% of developers experience this tax when they use these coding tools. But even if we weren’t to worry about my good buddies down at engineering, there is an even bigger problem: security. I want to touch back on the point that Ryan made about none of the data being protected on my silly toilet app. Luckily, in this case at least, no data of importance is being shared or stored on my application. But there are many instances where this would not be the case. Because these tools are promising powerful results without the need for developer experience, there are probably a lot of people without experience who will use something like Bolt to create their passion projects. And probably a lot of these passion projects will be well-meaning, and will work, on the front end at least. And maybe some of these programs will ask for information like ZIP code, or email address, or date of birth, or to even create a password. You can probably see where I’m going here; GDPR can too. It does seem unlikely that something that’s going to be pushed to market would go live without having someone with a development background look at it, but what of the fun side projects like mine? I could easily imagine an evil world where someone vibe codes something for their loved ones that includes identifying information about the people in their lives, and that falls into the hands of malicious folks who know how to use the inspect function. Was what Bolt created good enough for my purposes? Sure. And with the help of a few knowledgeable friends and coworkers, could I have fixed the issues I had with security and organization without ever having to learn a single command? Yes, definitely. But for a technology that is supposedly going to make junior developers obsolete, it needed a lot of help from my friends—all of whom are junior developers. On the other side of this story, I want to share something about one of my best friends who also regularly vibe codes. He’s a theoretical physicist with a doctorate from Stanford. He had wanted to remain in research after finishing his PhD, but found the opportunities slim and the pay even slimmer because of the current state of higher education. So he pivoted, pretty hard, into a role that meant he had to learn how to code quickly. He shared with me that LLMs had increased his learning capabilities ten-fold because they allowed him to find information fast. He talked about his mish-mashed usage of CoPilot, Gemini, and ChatGPT almost like it was a fond tutor of his, referencing times when he couldn’t figure out a bug and so had Gemini explain it to him. This, he told me, helped him the next time he experienced a similar bug. This, I think, is the real promise of vibe coding tools—that you can learn how to code without a CS degree. There is no one in the world who would say my friend isn’t intelligent enough to code, but the issue was that he had no experience. And after five years in the Stanford physics department, there was no way he was going back for another degree. Vibe coding tools were giving him the support and knowledge he needed, so he could learn these skills himself. Like anything in the wild west that is this age of AI, it all depends on how you use it. To take a page from my friend, I want my vibe coding experience to be the first step in me learning how to code. So, I’m offering up my vibe code for feedback, criticism, and tips from the community. Let me know what you think of my GitHub, and what you think I should do next to stop being the worst coder in the world. Author s Phoebe Sajor Content Associate Staff vibe coding ai coding generative AI worst coder in the world Recent articles January 12, 2026 Now everyone can chat on Stack Overflow January 5, 2026 What’s new at Stack Overflow: January 2026 January 1, 2026 Documents: The architect’s programming language December 31, 2025 A look under the hood: How (and why) we built Question Assistant Latest Podcast January 13, 2026 Vibe code anything in a Hanselminute Add to the discussion Login with your stackoverflow.com account to take part in the discussion. Our Stack Stack Internal Features Customers Security Pricing Stack Data Licensing Stack Ads Partnerships Services Stack Overflow Company Leadership Press Careers Social Impact Support Contact Stack Overflow help Stack Internal help Terms Privacy policy Cookie policy Your Privacy Choices Elsewhere Blog Dev Newsletter Podcast Releases Dev Survey Site design / logo © 2026 Stack Exchange Inc. Light Dark Auto | 2026-01-13T08:48:28 |
https://dev.to/t/programming/page/73#main-content | Programming Page 73 - DEV Community Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account DEV Community Close Programming Follow Hide The magic behind computers. 💻 🪄 Create Post Older #programming posts 70 71 72 73 74 75 76 77 78 Posts Left menu 👋 Sign in for the ability to sort posts by relevant , latest , or top . Right menu Why I Rewrote Portage in Go: Introducing GRPM v0.1.0 Andrey Kolkov Andrey Kolkov Andrey Kolkov Follow Jan 8 Why I Rewrote Portage in Go: Introducing GRPM v0.1.0 # go # linux # opensource # programming 5 reactions Comments Add Comment 5 min read Start, Stop, and Continue for 2026 Aaron McCollum Aaron McCollum Aaron McCollum Follow Dec 19 '25 Start, Stop, and Continue for 2026 # webdev # programming # learning Comments Add Comment 3 min read Amazon S3 Explained: Simple Storage in the Cloud MATHAN S MATHAN S MATHAN S Follow Dec 18 '25 Amazon S3 Explained: Simple Storage in the Cloud # cloud # devops # aws # programming Comments Add Comment 1 min read MURAL: A Visual Collaboration Tool in the DevSecOps Periodic Table MATHAN S MATHAN S MATHAN S Follow Dec 18 '25 MURAL: A Visual Collaboration Tool in the DevSecOps Periodic Table # devops # mural # programming # opensource Comments Add Comment 1 min read Leetcode 39 Combination Sum Wincy H Wincy H Wincy H Follow Dec 17 '25 Leetcode 39 Combination Sum # leetcode # programming # python # tutorial Comments Add Comment 3 min read Torrance Motors: Building a Fast, Reliable Automotive Website with C++ — Challenges Faced and Future Goals Alfie John Alfie John Alfie John Follow Dec 18 '25 Torrance Motors: Building a Fast, Reliable Automotive Website with C++ — Challenges Faced and Future Goals # webdev # programming # ai # javascript Comments Add Comment 9 min read A Better Way to Run Git Worktrees Finally! Julio Daniel Reyes Julio Daniel Reyes Julio Daniel Reyes Follow Dec 16 '25 A Better Way to Run Git Worktrees Finally! # git # vibecoding # programming # ai 27 reactions Comments Add Comment 1 min read How We Actually Ship Complex Systems with AI Agents Ali Baqbani Ali Baqbani Ali Baqbani Follow Dec 18 '25 How We Actually Ship Complex Systems with AI Agents # ai # programming # softwaredevelopment # architecture Comments Add Comment 3 min read Productionizing Model Context Protocol Servers OnlineProxy OnlineProxy OnlineProxy Follow Dec 17 '25 Productionizing Model Context Protocol Servers # programming # ai # beginners # tutorial Comments Add Comment 7 min read 🚀 Launching Vyoma Labs: A Research-First Space for Building the Future of the Web Prasoon Jadon Prasoon Jadon Prasoon Jadon Follow Dec 17 '25 🚀 Launching Vyoma Labs: A Research-First Space for Building the Future of the Web # webdev # programming # startup # opensource Comments Add Comment 3 min read Vibe Coding hit a wall: How I fixed $0.30/error OOMs and cut AI costs by 70% renming wang renming wang renming wang Follow Dec 17 '25 Vibe Coding hit a wall: How I fixed $0.30/error OOMs and cut AI costs by 70% # webdev # ai # programming # productivity 1 reaction Comments 1 comment 2 min read Introducing temporal-contract: Type-Safe Temporal. io Workflows for TypeScript Benoit Travers Benoit Travers Benoit Travers Follow Dec 21 '25 Introducing temporal-contract: Type-Safe Temporal. io Workflows for TypeScript # typescript # node # programming # productivity 2 reactions Comments Add Comment 8 min read AWS CodeDeploy: A Beginner-Friendly Guide to Automated Deployments Ege Pakten Ege Pakten Ege Pakten Follow Dec 17 '25 AWS CodeDeploy: A Beginner-Friendly Guide to Automated Deployments # aws # codedeploy # programming # infrastructureascode Comments Add Comment 5 min read The New Field Keyword Improves Properties in C# 14 Adrián Bailador Adrián Bailador Adrián Bailador Follow Dec 17 '25 The New Field Keyword Improves Properties in C# 14 # csharp # dotnet # programming # webdev Comments Add Comment 6 min read Atlassian Bamboo in the DevSecOps Periodic Table ABITHA N 24CB001 ABITHA N 24CB001 ABITHA N 24CB001 Follow Dec 18 '25 Atlassian Bamboo in the DevSecOps Periodic Table # devops # devsecops # programming # learning Comments Add Comment 1 min read I Built a Clean Age Calculator Because Most of Them Get the Details Wrong Momin Ali Momin Ali Momin Ali Follow Dec 18 '25 I Built a Clean Age Calculator Because Most of Them Get the Details Wrong # programming # webdev # javascript 1 reaction Comments 1 comment 2 min read StableJSON: A Practical Workspace for Serious JSON Work Debjit Dey Debjit Dey Debjit Dey Follow Dec 31 '25 StableJSON: A Practical Workspace for Serious JSON Work # programming # webdev # devtool # json Comments 1 comment 2 min read How One Can Start Their Journey in Data Engineering Chetan Gupta Chetan Gupta Chetan Gupta Follow Jan 10 How One Can Start Their Journey in Data Engineering # programming # dataengineering # sql # beginners Comments 2 comments 4 min read AI-Powered Programming: Creating My Own Magical Flashcards Study App Daniel Daniel Daniel Follow for Datalaria Jan 10 AI-Powered Programming: Creating My Own Magical Flashcards Study App # showdev # ai # programming 5 reactions Comments 2 comments 5 min read Beyond the Screen: Why LLMs Don't Need Browsers (And Why We Think They Do) Edward Burton Edward Burton Edward Burton Follow Dec 17 '25 Beyond the Screen: Why LLMs Don't Need Browsers (And Why We Think They Do) # webdev # programming # ai # browser 1 reaction Comments Add Comment 8 min read YAML Formatter Pineapple Pineapple Pineapple Follow Dec 22 '25 YAML Formatter # webdev # programming # beginners # kubernetes Comments Add Comment 2 min read Day 73: Python Longest Palindromic Substring – Expand-Around-Center O(n^2) Technique for Max Palindrome (LeetCode #5 Guide) Shahrouz Nikseresht Shahrouz Nikseresht Shahrouz Nikseresht Follow Dec 23 '25 Day 73: Python Longest Palindromic Substring – Expand-Around-Center O(n^2) Technique for Max Palindrome (LeetCode #5 Guide) # challenge # python # algorithms # programming Comments Add Comment 2 min read The Time Our Pipeline Processed the Same Day’s Data 47 Times Pradeep Kalluri Pradeep Kalluri Pradeep Kalluri Follow Dec 17 '25 The Time Our Pipeline Processed the Same Day’s Data 47 Times # dataengineering # airflow # python # programming Comments Add Comment 5 min read How I Use AI to Build Full-Stack Apps (The Pipeline Nobody Talks About) Edjere Evelyn Oghenetejiri Edjere Evelyn Oghenetejiri Edjere Evelyn Oghenetejiri Follow Dec 17 '25 How I Use AI to Build Full-Stack Apps (The Pipeline Nobody Talks About) # webdev # ai # programming # nextjs 1 reaction Comments Add Comment 3 min read I Built a Deterministic Life Tool (and Intentionally Removed “AI” From the Loop) FlameAI Studio FlameAI Studio FlameAI Studio Follow Dec 17 '25 I Built a Deterministic Life Tool (and Intentionally Removed “AI” From the Loop) # webdev # programming # productivity # beginners Comments Add Comment 2 min read loading... 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV DEV Community — A space to discuss and keep up software development and manage your software career Home DEV++ Podcasts Videos DEV Education Tracks DEV Challenges DEV Help Advertise on DEV DEV Showcase About Contact Free Postgres Database Software comparisons Forem Shop Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . DEV Community © 2016 - 2026. We're a place where coders share, stay up-to-date and grow their careers. Log in Create account | 2026-01-13T08:48:28 |
https://stackoverflow.blog/community/ | Community - Stack Overflow Blog Loading… Everything Productivity AI/ML Open Source Business Hub Company Releases Podcast Newsletter Stack Overflow Business Stack Internal : the knowledge intelligence layer that powers enterprise AI. Stack Data Licensing : decades of verified, technical knowledge to boost AI performance and trust. Stack Ads : engage developers where it matters — in their daily workflow. Community Related Tags Releases new features AI community update Company Subscribe to the podcast Get The Stack Overflow Podcast at your favorite listening service. Apple Podcasts Overcast Overcast Pocket Casts Spotify RSS feed January 12, 2026 Now everyone can chat on Stack Overflow Registered users can now join public chat rooms from day one, making it easier to connect, learn, and participate in the community Kate Smith 0 comment s Community January 5, 2026 What’s new at Stack Overflow: January 2026 For this first edition of the new year, we’re taking a step back to highlight some of the most impactful features shipped over the last year and how they can help you start 2026 strong. Zach Rutta 0 comment s December 30, 2025 How AI is helping us build better communities MIT and Stanford professor Alex “Sandy” Pentland joins the show to explore the power of communities for shared knowledge and how AI could hurt or help the growth of these communities. Phoebe Sajor 0 comment s The Stack Overflow Podcast Community AI knowledge sharing December 17, 2025 The 2025 Stack Overflow and Stack Exchange wrap—our top ten questions of the year! As 2025 comes to a close, we're sharing some of the top questions from across our entire Stack Exchange Network. Phoebe Sajor 2 comment s Community questions December 2, 2025 Introducing Stack Overflow AI Assist—a tool for the modern developer The way that developers interact with knowledge has changed in the age of AI. That's why we created AI Assist—a new way for users to access our 17 years of expert knowledge, and how Stack Overflow is remaining the always-open-tab of programmers around the world. Phoebe Sajor 9 comment s community update Community generative AI AI ai assistant Company December 1, 2025 What’s new at Stack Overflow: December 2025 Including a new MCP server, expanded access to a new question type, a long requested community ask to make copying code easier, and more! Zach Rutta 0 comment s November 20, 2025 Community Products roadmap update, November 2025 An update on recent launches and the upcoming roadmap. Des Darilek 0 comment s Community roadmap November 3, 2025 What’s new at Stack Overflow: November 2025 From a new kind of vote to a preview of the upcoming redesign, check out what’s been happening at Stack Overflow over the past month. Zach Rutta 1 comment October 8, 2025 A new look for comments Learn about what’s new with comments on Stack Overflow. Kate Smith 1 comment September 18, 2025 Stack Overflow is helping you learn to code with new resources See what we’ve been doing to make Stack Overflow even more helpful for students this year. Zach Rutta 1 comment Back to school Community learning to code September 9, 2025 We built stackoverflow.ai with the community and for the community Ryan is joined by our very own Ash Zade, Staff Product Manager, and Alex Warren, Staff Software Engineer, to discuss our newly released stackoverflow.ai, how it’s enhancing user experience by combining human-validated answers with AI, and our future plans for deeper personalization and community integration. Phoebe Sajor 3 comment s The Stack Overflow Podcast AI ai assistant Community learning to code August 21, 2025 Research roadmap update, August 2025 User research for the next era of Stack Overflow. Piper Lawson 0 comment s user research Community August 11, 2025 Renewing Chat on Stack Overflow Improving the place where developers have real conversations and real collaboration. Kate Smith 0 comment s coding community Community community update July 21, 2025 Community Products roadmap update, July 2025 An update on recent launches and the upcoming roadmap. Des Darilek 1 comment roadmap Community July 7, 2025 Getting creative with Coding Challenges An experiment to level up your coding skills on Stack Overflow, while learning in a space that welcomes creative problem-solving. Discover how we built it. Phoebe Sajor , Caroline Thomas 0 comment s coding creative coding creative code learning coding community Community July 1, 2025 Programming problems that seem easy, but aren't, featuring Jon Skeet Jon Skeet, the first Stack Overflow user with a million reputation, sits down with Ryan to share his wealth of knowledge on all things development: the deceptively simple but actually complicated problem of timezones, the importance of clear documentation for programmers, handling breaking changes and upgrading legacy systems, and the need for improved communication skills among developers. Phoebe Sajor 3 comment s Community dev life developer relations developer experience code quality soft skills The Stack Overflow Podcast June 20, 2025 Defending the realm: Trust and safety at Stack Overflow In this special episode, Ryan is joined by our Senior VP of Communities, Philippe Beaudette, and the Trust and Safety team at Stack Overflow to discuss maintaining platform integrity and managing user safety, handling complex issues like harassment, and how their team balances transparency and privacy online. Phoebe Sajor 0 comment s Community The Stack Overflow Podcast security privacy May 29, 2025 Not just a vibe, the Stack Overflow Developer Survey is really here This year, we're not just collecting data; we're reflecting on the last year of questions, answers, hallucinations, job changes, tech stacks, memory allocations, models, systems and agents—together. Erin Yepis 6 comment s dev survey Community May 19, 2025 Research roadmap update, May 2025 An update to the research that the User Experience team is running over the next quarter. Piper Lawson 2 comment s user research Company Community May 7, 2025 Behind the scenes: Community “management” at Stack Overflow Community “management” at its core is supporting and enabling communities to manage themselves. Rosie 0 comment s Community April 23, 2025 Community Products roadmap update, April 2025 An update on recent launches and the upcoming roadmap Des Darilek 0 comment s roadmap Community February 27, 2025 Our next phase—Q&A was just the beginning For those that missed our February AMA, let’s discuss the future of Stack Overflow Prashanth Chandrasekar , Philippe Beaudette 16 comment s Community Company February 6, 2025 Investing in the Stack Exchange Network and the future of Stack Overflow Mark your calendars to learn more about Stack’s Future—Feb 26th. Prashanth Chandrasekar 6 comment s Community February 3, 2025 Community Products Roadmap Update, January 2025 An update on recent launches and the upcoming roadmap. Des Darilek 0 comment s Community community update Knowledge as a service staging ground Show more Our Stack Stack Internal Features Customers Security Pricing Stack Data Licensing Stack Ads Partnerships Services Stack Overflow Company Leadership Press Careers Social Impact Support Contact Stack Overflow help Stack Internal help Terms Privacy policy Cookie policy Your Privacy Choices Elsewhere Blog Dev Newsletter Podcast Releases Dev Survey Site design / logo © 2026 Stack Exchange Inc. Light Dark Auto | 2026-01-13T08:48:28 |
https://stackoverflow.blog/2025/11/03/what-s-new-at-stack-overflow-november-2025/ | What’s new at Stack Overflow: November 2025 - Stack Overflow Blog Loading… Everything Productivity AI/ML Open Source Business Hub Company Releases Podcast Newsletter Stack Overflow Business Stack Internal : the knowledge intelligence layer that powers enterprise AI. Stack Data Licensing : decades of verified, technical knowledge to boost AI performance and trust. Stack Ads : engage developers where it matters — in their daily workflow. November 3, 2025 What’s new at Stack Overflow: November 2025 From a new kind of vote to a preview of the upcoming redesign, check out what’s been happening at Stack Overflow over the past month. Welcome to the new monthly blog series (this is our first one!!) designed to keep you in the loop on the latest launches and features on stackoverflow.com . Catch up on what’s new, what’s launching, and what’s happening behind the scenes all in one place. Here’s what’s new from the past month: Expanded voting access to all users Voting is an integral part of the Stack Overflow experience, as it helps indicate questions and answers that the community values. However, historically, we have gated voting based on reputation points —15 for upvotes and 125 for downvotes. We introduced “free votes” to help new users engage in curation early and we believe this is one of the most effective ways to encourage new users to come back. Free votes are a new kind of vote, originally introduced as part of an experiment , to help educate users on how to use votes on the platform, before they have earned enough reputation to vote normally. Learn more about this voting update. Open-ended questions on Stack Overflow We’ve heard feedback that some of the most valuable discussions involve developer preferences, personal experiences, and topics with more than one "right" answer. Historically, the platform has closed these questions for being subjective or not having a single accepted solution. We’re exploring how Stack Overflow can host these valuable, inclusive questions and answers on the platform while still maintaining our standards for quality. Sign up to get early access and provide your feedback to these types of open-ended questions. Early look into the Stack Overflow redesign We shared on Meta Stack Exchange a look behind the scenes on what’s happening with the upcoming Stack Overflow redesign. These series of posts included: Part 1: Introduction and background Part 2: Color and Typography Part 3: Navigation and Homepage Part 4: Questions Part 5: User Profiles Check out the first look at the design changes we’re considering, learn about the key areas we’re focusing on, and provide your feedback and suggestions on the posts above. New anti-spam tool on Stack Overflow and Stack Exchange sites We launched a new tool (designed to complement existing anti-spam tooling) to enhance the network's defense against spam and increase the total amount of spam caught by automation. These tools support and enhance existing community work, such as anti-spam projects like those created by the Charcoal team . By automatically and immediately catching a significant portion of repetitive spam, we can free up time for moderators and other community members. Learn more about the new anti-spam tool here. Coding challenges: New collaboration with Kaggle Challenges have been around for a few months and have gotten some great response, but now we’re going bigger. Stack Overflow teamed up with Kaggle to create a special two-part challenge . Kaggle is a platform for machine learning and data science folks to explore data and complete challenges. Their October Playground challenge was about predicting roadway accidents based on data about road design, weather conditions, signage etc. As part of the challenge, participants were tasked with building a web application to explore the data. The challenge just closed, and we’re excited to see the results! New onboarding emails We launched a new email series to educate new users about Stack Overflow and its features, how to be involved, and how to contribute after signing up for an account. The email series highlights features, privileges, and actions available to new users. We want to do everything we can to set up new users for success, whether they are here to get help with a coding problem, to connect with the community, or to learn about a new technical topic. It's often intimidating or frustrating to understand how to contribute to Stack Overflow without any knowledge of what reputation is or the guidelines that often discourage participation. Getting started with Stack Overflow hasn’t always been a great user experience. Creating a more robust onboarding experience will hopefully ease that pain point and encourage continued engagement from new users. Author s Zach Rutta Associate Director, Product Marketing, Community Products Staff Releases Community new features Latest releases January 5, 2026 What’s new at Stack Overflow: January 2026 December 16, 2025 Your 2025 Stacked: A year of knowledge, community, and impact December 1, 2025 What’s new at Stack Overflow: December 2025 November 12, 2025 2025.8 release introduces Stack Overflow Internal: The next generation of enterprise knowledge intelligence Add to the discussion Login with your stackoverflow.com account to take part in the discussion. Our Stack Stack Internal Features Customers Security Pricing Stack Data Licensing Stack Ads Partnerships Services Stack Overflow Company Leadership Press Careers Social Impact Support Contact Stack Overflow help Stack Internal help Terms Privacy policy Cookie policy Your Privacy Choices Elsewhere Blog Dev Newsletter Podcast Releases Dev Survey Site design / logo © 2026 Stack Exchange Inc. Light Dark Auto | 2026-01-13T08:48:28 |
https://developer.x.com/developer-terms/policy#3-b | Developer Policy – X Developers | X Developer Platform <g> <g> <defs> <rect id="SVGID_1_" x="-468" y="-1360" width="1440" height="3027" /> </defs> <clippath id="SVGID_2_"> <use xlink:href="#SVGID_1_" style="overflow:visible;" /> </clippath> </g> </g> <rect x="-468" y="-1360" class="st0" width="1440" height="3027" style="fill:rgb(0,0,0,0);stroke-width:3;stroke:rgb(0,0,0)" /> <path d="M13.4,12l5.8-5.8c0.4-0.4,0.4-1,0-1.4c-0.4-0.4-1-0.4-1.4,0L12,10.6L6.2,4.8c-0.4-0.4-1-0.4-1.4,0c-0.4,0.4-0.4,1,0,1.4 l5.8,5.8l-5.8,5.8c-0.4,0.4-0.4,1,0,1.4c0.2,0.2,0.4,0.3,0.7,0.3s0.5-0.1,0.7-0.3l5.8-5.8l5.8,5.8c0.2,0.2,0.5,0.3,0.7,0.3 s0.5-0.1,0.7-0.3c0.4-0.4,0.4-1,0-1.4L13.4,12z" /> </svg>" data-icon-chevron-right="<svg xmlns="http://www.w3.org/2000/svg" width="24" height="24" viewbox="0 0 24 24" aria-hidden="true" focusable="false" role="none" class="twtr-icon"> <path opacity="0" d="M0 0h24v24H0z" /> <path d="M17.207 11.293l-7.5-7.5c-.39-.39-1.023-.39-1.414 0s-.39 1.023 0 1.414L15.086 12l-6.793 6.793c-.39.39-.39 1.023 0 1.414.195.195.45.293.707.293s.512-.098.707-.293l7.5-7.5c.39-.39.39-1.023 0-1.414z" /> </svg>" data-icon-chevron-down="<svg xmlns="http://www.w3.org/2000/svg" width="24" height="24" viewbox="0 0 24 24" aria-hidden="true" focusable="false" role="none" class="twtr-icon"> <path opacity="0" d="M0 0h24v24H0z" /> <path d="M20.207 7.043c-.39-.39-1.023-.39-1.414 0L12 13.836 5.207 7.043c-.39-.39-1.023-.39-1.414 0s-.39 1.023 0 1.414l7.5 7.5c.195.195.45.293.707.293s.512-.098.707-.293l7.5-7.5c.39-.39.39-1.023 0-1.414z" /> </svg>" data-icon-arrow-left="<svg width="28px" height="28px" viewbox="0 0 28 28" version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" aria-hidden="true" focusable="false" role="none" class="twtr-icon u01-meganav__icon-arrow-left"> <g stroke="none" stroke-width="1" fill="none" fill-rule="evenodd" stroke-linecap="round"> <g transform="translate(-1216.000000, -298.000000)" stroke-width="2.25"> <g transform="translate(1200.000000, 282.000000)"> <g transform="translate(17.000000, 17.000000)"> <path d="M0.756410256,12.8589744 L25.7179487,12.8589744"></path> <path d="M13.2371795,25.3397436 L25.7179487,12.8589744"></path> <path d="M13.2371795,12.4807692 L25.3397436,0.378205128" transform="translate(19.288462, 6.429487) rotate(-90.000000) translate(-19.288462, -6.429487) "></path> </g> </g> </g> </g> </svg>" data-left-nav-items="[{"isActive":false,"hasActiveChild":false,"children":[{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"X API","linkDisabled":false,"title":"X API","path":"https://developer.x.com/en/products/twitter-api"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"X Ads API","linkDisabled":false,"title":"X Ads API","path":"https://developer.x.com/en/products/x-ads-api"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"X for websites","linkDisabled":false,"title":"X for websites","path":"https://developer.x.com/en/products/x-for-websites"}],"overviewTitle":"Products","linkDisabled":true,"title":"Products","path":"https://developer.x.com/en/products"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Docs","linkDisabled":false,"title":"Docs","path":"https://docs.x.com/"},{"isActive":false,"hasActiveChild":false,"children":[{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Build for business","linkDisabled":false,"title":"Build for business","path":"https://developer.x.com/en/use-cases/build-for-businesses"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Build for the public","linkDisabled":false,"title":"Build for the public","path":"https://developer.x.com/en/use-cases/build-for-consumers"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Do research","linkDisabled":false,"title":"Do research","path":"https://developer.x.com/en/use-cases/do-research"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Teach \u0026 learn","linkDisabled":false,"title":"Teach \u0026 learn","path":"https://developer.x.com/en/use-cases/teach-and-learn"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Build for good","linkDisabled":false,"title":"Build for good","path":"https://developer.x.com/en/use-cases/build-for-good"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Build for fun","linkDisabled":false,"title":"Build for fun","path":"https://developer.x.com/en/use-cases/build-for-fun"}],"overviewTitle":"Use Cases","linkDisabled":true,"title":"Use Cases","path":"https://developer.x.com/en/navigation/left-nav-items/use-cases"},{"isActive":false,"hasActiveChild":false,"children":[{"isActive":false,"hasActiveChild":false,"children":[{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Changelog","linkDisabled":false,"title":"Changelog","path":"https://docs.x.com/updates/changelog"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Blog","linkDisabled":false,"title":"Blog","path":"https://developer.x.com/en/blog"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Newsletter","linkDisabled":false,"title":"Newsletter","path":"https://developer.x.com/en/updates/stay-informed"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"YouTube","linkDisabled":false,"title":"YouTube","path":"https://www.youtube.com/c/twitterdev"}],"linkDisabled":true,"title":"Stay informed","path":"https://developer.x.com/"},{"isActive":false,"hasActiveChild":false,"children":[{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Forums","linkDisabled":false,"title":"Forums","path":"https://twittercommunity.com/"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Events","linkDisabled":false,"title":"Events","path":"https://twitterdev.bevylabs.com/"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Insiders","linkDisabled":false,"title":"Insiders","path":"https://developer.twitter.com/en/community/insiders"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Community leaders","linkDisabled":false,"title":"Community leaders","path":"https://developer.x.com/en/community/leaders"}],"linkDisabled":true,"title":"Connect","path":"https://developer.x.com/"}],"overviewTitle":"Community","linkDisabled":false,"menuType":"multiCategory","title":"Community","path":"https://developer.x.com/en/community"}]" data-right-nav-items="[{"isActive":false,"hasActiveChild":false,"children":[{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Policies","linkDisabled":false,"title":"Policies","path":"https://developer.x.com/en/developer-terms"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Developer agreement","linkDisabled":false,"title":"Developer agreement","path":"https://developer.x.com/en/developer-terms/agreement-and-policy/source"}],"overviewTitle":"Support","linkDisabled":false,"title":"Support","path":"https://developer.x.com/en/support"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Developer Portal","linkDisabled":false,"title":"Developer Portal","path":"https://developer.twitter.com/en/portal/petition/essential/basic-info"}]" data-cta-enabled="true" data-profile-enabled="true" data-cta-link-new-tab="false" data-root-page-title="Developer Platform"> Developer terms Developer Policy Let's get started X + Developers Using this policy X + Developers Using this policy X + Developers X loves developers. We’re delighted and amazed by the tools and services this community creates by harnessing the power of X data. As part of our commitment to this community, we aim to provide data access that is open and fair for developers, safe for people on X, and beneficial for the X platform as a whole. To further these goals we’ve crafted the Developer Policy as a guide to help people understand our rules and expectations about appropriate API and X Content usage. This Developer Policy (“ Policy ”) provides rules and guidelines for developers who interact with X’s ecosystem of applications, services, website, web pages and content. It is part of your contract with X governing access to and use of the X API and X Content (either as part of the Developer Agreement or other written agreement with X). Policy violations are considered violations of your agreement. This Policy may be changed from time to time without notice. Capitalized terms used in this Policy, which are not defined in this Policy, will have the respective meanings ascribed to them in the Developer Agreement or the Master License Agreement. Using this policy We’ve structured this policy to make it as easy to follow as possible. Please keep information from the following policy sections top of mind as you use the X API and X Content: 1. Set Yourself Up for Success - You are responsible for complying with all X policies. It’s important that you review and understand this Policy, as well as the policies we link to in this document, before you access the X API and X Content. The time spent reviewing our policies may save you hours of rework down the road. 2. Privacy and Control are Essential - Protecting and defending the privacy of people on X is built into the core DNA of our company. As such, we prohibit the use of X data in any way that would be inconsistent with people’s reasonable expectations of privacy. By building on the X API or accessing X Content, you have a special role to play in safeguarding this commitment, most importantly by respecting people’s privacy and providing them with transparency and control over how their data is used. 3. Follow the Platform Usage Guidelines - Getting approved to access the X API and X Content is just the first step. Our Platform Usage Guidelines should be your first stop anytime you have questions about how to ensure policy compliance for your planned use of the X platform. We’ve provided a lot more detail on what each of these three key sections mean below. Please review them carefully to ensure that your usage of the X API and X Content is consistent with our policies. If we believe you are in violation of this Policy (or any other X policy), we may suspend or permanently revoke your access to the X API and X Content. Finally, please note that X may monitor your use of the X API to improve the X Applications, to examine any commercial use, and to ensure your compliance with your approved use case and this Policy. Thanks for reading, and thank you for building with us! We look forward to seeing what you create! Chapter 1 Set yourself up for success Set yourself up for success Set yourself up for success Set yourself up for success You can avoid many potential pitfalls while using the X API by ensuring that your service has been built the right way from day 1. This section of the Developer Policy contains rules that all developers must follow before using the X API or X Content. The Free, Basic, and Pro plans (as described at developer.x.com/en ) are designed for hobbyists, commercial prototyping, early-stage X product integrations, and supporting applications with limited end-users. If you use the X API and X Content beyond this scope, then you must apply (or already subscribe to) an Enterprise plan (as described at developer.x.com/en ). We review all proposed uses of the X developer platform to verify policy compliance — so you’re required to disclose (and update, as applicable) your planned use of the X API and X Content in order to be granted and to maintain access. All new developers must apply for a developer account to access the X API. Current developers without an approved developer account must apply for one as directed to do so by X. As part of this process, you’ll need to provide us with a written description of your intended uses of the X API and X Content. Your use case description is binding on you, and any substantive deviation from it may constitute a violation of our rules and result in enforcement action. You must notify us of any substantive modification to your use case and receive approval before you may begin using X Content for that new purpose. Failure to do so may result in suspension and termination of your API and data access. By building on the X API or accessing X Content, you must comply with ALL X policies. These include this Developer Policy , the Automation Rules , the Display Requirements , the API Restricted Uses Rules , the X Rules , and the X Brand Resources , as well as any other agreements you enter into with X relating to your use of the X API or X Content, including but not limited to the Developer Agreement or a Master Licensing Agreement or Order (as applicable). You must also comply with any modifications to these policies and any new policies launched by X. It is your responsibility to monitor the use of your service and to design your service to prevent violations of X policy by people who use it. Failure to do so may result in suspension or termination of your API and X Content access. You may not register multiple applications for a single use case or substantially similar or overlapping use cases. In this context, a “use case” is a consistent set of analyses, displays, or actions performed via an application. "White label" versions of a tool or service are not permissible. If you plan to “white label” versions of your application, you must notify and receive separate approval from us. As a single exception to these rules, you may create and use a maximum of 3 applications for development, staging, and production instances of the same service. These apps must be registered to a single account, and should be clearly identified (in the name and description) as dev, staging, and prod instances of a single service. You may not use development or staging applications for production purposes. You must keep all API keys or other access credentials private. You may not use, and may not encourage or facilitate others to use, API keys or other access credentials owned by others. Your license agreement with X limits your use of the X API and X Content. Among other things, the X API has rate limits which help to ensure fair data usage and to combat spam on the platform. You may not exceed or circumvent rate limits, or any other limitations or restrictions described in this Policy or your agreement with X, listed on the Developer Site , or communicated to you by X. You may not remove or alter any proprietary notices or marks on X Content received via the X API. This helps to make sure that people know where X Content is coming from, and who it belongs to. For data integrity and platform health reasons, you may not interfere with, intercept, disrupt, or disable any features of the X API or the X service. In other words, use the APIs as intended and documented on developer.x.com . Refer to our HackerOne guidelines for more details about acceptable use. Chapter 2 Privacy and control are essential Privacy and control are essential Consent & permissions Content compliance Off-X matching Your privacy policy Using geo-data X passwords Privacy and control are essential Consent & permissions Content compliance Off-X matching Your privacy policy Using geo-data X passwords Privacy and control are essential X takes privacy seriously, and we expect everyone using X Content and the X API to do the same. Any use of the X developer platform, X API, or X Content in a manner that is inconsistent with peoples’ reasonable expectations of privacy may be subject to enforcement action, which can include suspension and termination of API and X Content access. Your commitment to privacy and control must extend to all uses of X Content and all aspects of the service that you build using our API. To that end, the people using your service must understand and consent to how you use their data, and how you access X on their behalf. This can be accomplished through providing people with a clear, comprehensive, and transparent privacy policy, as well as ensuring that you get express and informed consent from each person using your service before taking any action on their behalf. Please note that a person authenticating into your service does not by itself constitute consent. Consent & permissions In particular, you must get express and informed consent from people before doing any of the following: Taking any actions on their behalf. This includes (but is not limited to): Posting content to X Following/unfollowing accounts Modifying profile or account information Adding hashtags or any other content to Posts Republishing content accessed by means other than via the X API or other X tools Using someone’s X Content to promote a product or service Storing non-public content such as Direct Messages (DMs), or any other private or confidential information Sharing or publishing protected content, or any other private or confidential information If your service allows people to post content to X you must do the following before publishing: Show exactly what will be published Make it clear to people using your service what geo information (if any) will be added to the content If your service allows people to post content to both your service and X, you must do the following before publishing: Obtain permission to post the content Explain where you will post the content You must respect the protected and blocked status of all X Content. You may not serve content obtained using one person’s authentication token to a different person who is not authorized to view that content. Protected accounts: A protected account ’s content is only available to people who have been approved by the owner to follow that account. So, if you run a service that accesses protected accounts, you may only do so to serve such content to the specific people with permission to view that content. Blocked accounts: People on X are able to block access to their accounts for any reason they choose. Commingling information obtained from tokens (or any other API-based action) to bypass this choice is not permitted. As Direct Messages (DMs) are non-public in nature, services that provide DM features must take extra steps to safeguard personal privacy. You may not serve DM content to people who are not authorized to view that content. If your service provides DM functionality you must also: Notify people if you send read receipt events for DMs. You can do this by providing a notice directly in your service, or by displaying read receipts from other participants in a conversation. Get consent before configuring media to be sent in a DM as "shared" (i.e. reusable across multiple DMs). If you do allow media in a DM to be “shared,” you must provide a clear notice that this content will be accessible to anyone with the media’s URL. Content compliance If you store X Content offline, you must keep it up to date with the current state of that content on X. Specifically, you must delete or modify any content you have if it is deleted or modified on X. This must be done as soon as reasonably possible, or within 24 hours after receiving a request to do so by X or the applicable X account owner, or as otherwise required by your agreement with X or applicable law. This must be done unless otherwise prohibited by law, and only then with the express written permission of X. Modified content can take various forms. This includes (but is not limited to): Content that has been made private or gained protected status Content that has been suspended from the platform Content that has had geotags removed from it Content that has been withheld or removed from X Off-X matching We limit the circumstances under which you may match a person on X to information obtained or stored off-X. Off-X matching involves associating X Content, including a X @handle or user ID, with a person, household, device, browser, or other off-X identifier. You may only do this if you have express opt-in consent from the person before making the association, or as described below. In situations in which you don’t have a person’s express, opt-in consent to link their Xidentity to an off-X identifier, we require that any connection you draw be based only on information that someone would reasonably expect to be used for that purpose. In addition, absent a person’s express opt-in consent you may only attempt to match your records about someone to a X identity based on: Information provided directly to you by the person. Note that records about individuals with whom you have no prior relationship, including data about individuals obtained from third parties, do not meet this standard; and/or Public data. “Public data” in this context refers to: Information about a person that you obtained from a public, generally-available resource (such as a directory of members of a professional association) Information on X about a person that is publicly available, including: Posts Profile information, including an account bio and publicly-stated location Display name and @handle Your privacy policy You must display your service’s privacy policy to people before they are permitted to download, install, or sign up to your service. It must disclose at least the following information: The information that you collect from people who use your service How you use and share that information (including with X) How people can contact you with inquiries and requests regarding their information Your privacy policy must be consistent with all applicable laws, and be no less protective of people than X’s Privacy Policy and the privacy policy of our other services and corporate affiliates . You must cease your access to the X API and the use of all X Content if you are unable to comply with your and/or X’s Privacy Policy. Using geo-data Use of geo data comes with additional restrictions due to the sensitive nature of this information. If your service adds location information to Posts, you must disclose to people: When you add location information Whether you add location information as a geotag or annotations data Whether your location information is listed as a place, or as geographic coordinates If your application allows people to post with their location you must comply with X’s geo guidelines in full. Any use of location data or geographic information on a standalone basis is prohibited. You may not (and may not permit others to) store, aggregate, or cache location data and other geographic information contained in X Content, except as part of a Post. For example, you may not separate location data or geographic information out from Posts to show where individuals have been over time. Heat maps and related tools that show aggregated geo activity (e.g., the number of people in a city using a hashtag) are permitted. X passwords You may not store X passwords, or request that people provide their X password, account credentials, or developer application information (including consumer key) to you directly. We suggest the use of Sign-in with X as the authentication tool to link your service and people on X. Chapter 3 Platform usage guidelines Platform usage guidelines Spam, bots, and automation X performance benchmarking Public display of Posts Content redistribution Pay to engage Service authenticy X name, logo, and likeness Advertising on X Platform usage guidelines Spam, bots, and automation X performance benchmarking Public display of Posts Content redistribution Pay to engage Service authenticy X name, logo, and likeness Advertising on X Platform usage guidelines Have you taken care to review X’s policies and set up your API access the right way? Does your service follow X’s privacy and control guidelines? If you can answer yes to these two questions, then you are ready to start using the X API and X Content. X’s Platform Usage Guidelines provide the assistance needed to ensure that your use of X Content is compliant from day 1 throughout the lifecycle of your service. We suggest reviewing these rules on a regular basis to make sure that your integration is operating in a way that is safe and beneficial to people on X and the X platform as a whole. Spam, bots, and automation The use of the X API and developer products to create spam, or engage in any form of platform manipulation, is prohibited. You should review the X Rules on platform manipulation and spam , and ensure that your service does not, and does not enable people to, violate our policies. Services that perform write actions, including posting Posts, following accounts, or sending Direct Messages, must follow the Automation Rules . In particular, you should: Always get explicit consent before sending people automated replies or Direct Messages Immediately respect requests to opt-out of being contacted by you Never perform bulk, aggressive, or spammy actions, including bulk following Never post identical or substantially similar content across multiple accounts If you’re operating an API-based bot account you must clearly indicate what the account is and who is responsible for it. You should never mislead or confuse people about whether your account is or is not a bot. A good way to do this is by including a statement that the account is a bot in the profile bio. X performance benchmarking You may not use the X API to measure the availability, performance, functionality, or usage of X for benchmarking, competitive, or commercial purposes. For example, you should never use the X API to: Calculate aggregate X metrics, such as the total number of Monthly Actives (MAs) or Daily Actives (DAs) Calculate aggregate X Post metrics, such as the total number of Posts posted per day, or the number of account engagements Measure or analyze the responsiveness of X Measure or analyze spam or security on X, except as permitted below We support research that helps improve conversational health on X. You may not publicly disclose any research or findings concerning, or develop, create, or offer services using, the X API or X Content that measure, analyze, or attempt to identify behaviors or content which violate X policies without express written permission from X. DSA Researchers: If you need to contact X relating to access under Art. 40 of the Digital Services Act, please contact EU-Questions@X.com . If you wish to apply for researcher access, please submit an application . Public display of Posts You must maintain the integrity of all X Content that you display publicly or to people who use your service. If you don’t use X for Websites to display content, then you must use the X API to retrieve the most current version available for display. If displayed content ceases to be available through the X API, then you must remove it from your service as soon as reasonably possible, or within 24 hours after the receipt of a removal request from X, or the applicable X account owner, or as otherwise required by applicable law. There are specific rules you must follow if you display X Content offline. Follow the guidelines for using Posts in broadcast if you display Posts offline. If you embed or display Posts, you must contact us about your X API access if your site exceeds 10 million daily impressions. X reserves the right to require additional terms as a condition to your use of the X API. Additional restrictions on X for Websites developer use include: Embedded Posts and/or embedded timelines You must provide people with legally sufficient notice that fully discloses X’s collection and use of data about browsing activities on your website, including for interest-based advertising and personalization. You must also obtain legally sufficient consent from people for such collection and use You must provide legally sufficient instructions on how people can opt out of X’s interest-based advertising and personalization as described here X for Websites widgets You must ensure that people are provided with clear and comprehensive information about, and consent to, the storing and accessing of cookies or other information on their devices as described in X’s cookie use , where providing such information and obtaining such consent is required by law Services targeted to children under 13 Services targeted to children under 13 must opt out of tailoring X in any embedded Post and/or embedded timelines by setting the opt-out parameter to be ‘true’ as described here Content redistribution The best place to get X Content is directly from X. Consequently, we restrict the redistribution of X Content to third parties. If you provide X Content to third parties, including downloadable datasets or via an API, you may only distribute Post IDs, Direct Message IDs, and/or User IDs (except as described below). In total, you may not distribute more than 1,500,000 Post IDs to any entity (inclusive of multiple individuals associated with a single entity) within any 30 day period unless you have received written permission from X. In addition, developers may provide up to 500 public Posts Objects and/or User Objects to each person who uses your service on a daily basis if this is done via non-automated means (e.g., download of spreadsheets or PDFs). Academic researchers are permitted to distribute Post IDs and/or User IDs solely for the purposes of non-commercial research on behalf of an academic institution, and that has been approved by X in writing, or peer review or validation of such research. Only as many Post IDs or User IDs that is necessary for such research, and has been approved by X may be used. Any X Content provided to third parties remains subject to this Policy, and those third parties must agree to the X Terms of Service , Privacy Policy , Developer Agreement , and Developer Policy before receiving such downloads. You may not enable any entity to circumvent any other limitations or restrictions on the distribution of X Content as contained in this Policy , the Developer Agreement , or any other agreement with X. Note: This Section does not apply to researchers with X API access via Art. 40 of the EU Digital Services Act (2022) (“ DSA ”), who are instead subject to the procedures and restrictions set forth in the DSA and the Developer Agreement. Pay to engage Your service shouldn’t compensate people to take actions on X, as that results in inauthentic engagement that degrades the health of the platform. As you use the X API you may not sell or receive monetary or virtual compensation for any X actions. This includes, but is not limited to, Posts, follows, unfollows, reposts, likes, comments, and replies. Service authenticity You must clearly identify your service so that people can understand its source and purpose. Don’t use names, logos, or URLs that mask your service’s identity and features, or that falsely imply an affiliation with X or third parties. Note that creating applications for the purpose of selling names, or to prevent others from using names, is prohibited. You may not use any URL (including shortened URLs) for your service that directs people to: A site that is unrelated to your service A spam or malware site A site that encourages people to violate X policy X name, logo, and likeness You may only use and display the X name and logo to identify X as the source of X Content. You should never use the X name and logo, the X Official Partner Program badge, or any other similar marks or names in a manner that creates a false sense of endorsement, sponsorship, or association with X. The X Brand Resources contain detailed information to help you use the X brand in the right way. You may only use the X Verified Account badge and any other enhanced account categorization as it is reported to you by X through the API. This helps people know that the content your service displays is equivalent to that shown on X. Advertising on X There are restrictions regarding how and where you are allowed to advertise around X Content. To start, your advertisements can’t resemble or reasonably be confused by people as a Post. Other rules on advertising include: There must be a clear separation between X Content and your advertisements. You may not place any advertisements within the X timeline other than X Ads. X reserves the right to serve advertising via the X API. If you decide to serve X Ads once we start delivering them via the API, we will share a portion of advertising revenue with you in accordance with the relevant terms and conditions. You may not use X Content, or information obtained from the X API to target people with advertising outside of the X platform. Chapter 4 Rules for specific X services or features X login X Cards Definitions X login X Cards Definitions The following additional rules apply for any use of the X services or features listed below: X login You must present people with easy to find options to log into and out of X, for example via the OAuth protocol. The Sign in with X option must be displayed at least as prominently as any other sign-up or sign-in feature on your service. You must also provide people without a X account the opportunity to create one via X. Once someone on your service authenticates via Sign in with X you must clearly display their X identity. X identity includes the person’s current X @handle, avatar, and X logo. Any display of someone’s X followers on your service must clearly show that the relationship is associated with X. X Cards To ensure a quality experience you must develop your Card to render across all platforms where Cards are displayed. Additional rules that you must follow when using Cards include: You must mark your Post as ‘true’ for sensitive media if you plan to display such media within a Card You must use HTTPS for hosting all assets within your Card. Your Card should never generate active mixed content browser warnings Audio and video content should include stop or pause controls, and default to ‘sound off’ for videos that automatically play content You may not exceed or circumvent X’s limitations placed on any Cards, including the Card’s intended use. Additional restrictions on Cards use include: You may not place third-party sponsored content within Cards without X’s approval You may not attach monetary incentives (including virtual currency) within your Card or on X from your Card You may not include content or actions within your Card that are misleading or not contextually relevant, such as URLs and media You may only attach an App Card to a Post when someone is explicitly promoting or referring to the app in the Post Definitions X Content ‒ Posts, Post IDs, X end user profile information, and any other data and information made available to you through the X API or by any other means authorized by X, and any copies and derivative works thereof. Developer Site ‒ X’s developer site located at https://developer.x.com . Services ‒ Your websites, applications and other offerings that display X Content or otherwise use the Licensed Material as explicitly approved by X. Post ID ‒ A unique identification number generated for each Post. Post ‒ A posting made on X Applications. “X” ‒ Means (a) X Corp. (865 FM 1209, Building 2, Bastrop, TX 78602, USA) if your principal place of business is outside the European Union, EFTA States, and the United Kingdom; or (b) X Internet Unlimited Company (One Cumberland Place, Fenian Street, Dublin 2, D02 AX07, Ireland) if your principal place of business is in the European Union, EFTA States, or the United Kingdom. Direct Message - A message that is privately sent on X Applications by one end user to one or more specific end user(s) using X’s Direct Message function. X API ‒ The X Application Programming Interface (“API”), Software Development Kit (“SDK”) and/or the related documentation, data, code, and other materials provided by X with the API, as updated from time to time, including without limitation through the Developer Site. X Applications ‒ X’s consumer facing products, services, applications, websites, web pages, platforms, and other offerings, including without limitation, those offered via https://x.com and X's mobile applications. Developer policy and terms Follow @XDevelopers Subscribe to developer news X platform X.com Status Accessibility Embed a post Privacy Center Transparency Center Download the X app Try Grok.com X Corp. About the company Company news Brand toolkit Jobs and internships Investors Help Help Center Using X X for creators Ads Help Center Managing your account Email Preference Center Rules and policies Contact us Developer resources Developer home Documentation Forums Communities Developer blog Engineering blog Developer terms Business resources Advertise X for business Resources and guides X for marketers Marketing insights Brand inspiration X Ads Academy © 2026 X Corp. Cookies Privacy Terms and conditions Did someone say … cookies? X and its partners use cookies to provide you with a better, safer and faster service and to support our business. Some cookies are necessary to use our services, improve our services, and make sure they work properly. Show more about your choices . Accept all cookies Refuse non-essential cookies | 2026-01-13T08:48:28 |
https://www.coursera.org/account/accomplishments/verify/KQJ2WW3A4X2F?trk=public_profile_certification-title | Coursera | Online Courses & Credentials From Top Educators. Join for Free | Coursera For Individuals For Businesses For Universities For Governments Explore Degrees ​ Log In Join for Free Join for Free Course Certificate Introduction to Data Science in Python Completed by Daniel Bourke November 10, 2018 30 hours (approximately) Daniel Bourke's account is verified. Coursera certifies their successful completion of Introduction to Data Science in Python Introduction to Data Science in Python University of Michigan Filled Star Filled Star Filled Star Filled Star Half-Filled Star 4.5 (27,251 ratings) | 850,782 already enrolled Enroll for Free What you will learn Understand techniques such as lambdas and manipulating csv files Describe common Python functionality and features used for data science Query DataFrame structures for cleaning and processing Explain distributions, sampling, and t-tests Skills you will gain Pandas (Python Package) Python Programming Data Cleansing Pivot Tables And Charts Data Science Statistical Analysis Data Manipulation Data Import/Export NumPy Data Analysis Programming Principles Coursera Footer Skills Artificial Intelligence (AI) Cybersecurity Data Analytics Digital Marketing English Speaking Generative AI (GenAI) Microsoft Excel Microsoft Power BI Project Management Python Certificates & Programs Google Cybersecurity Certificate Google Data Analytics Certificate Google IT Support Certificate Google Project Management Certificate Google UX Design Certificate IBM Data Analyst Certificate IBM Data Science Certificate Machine Learning Certificate Microsoft Power BI Data Analyst Certificate UI / UX Design Certificate Industries & Careers Business Computer Science Data Science Education & Teaching Engineering Finance Healthcare Human Resources (HR) Information Technology (IT) Marketing Career Resources Career Aptitude Test Examples of Strengths and Weaknesses for Job Interviews High-Income Skills to Learn How Does Cryptocurrency Work? How to Highlight Duplicates in Google Sheets How to Learn Artificial Intelligence Popular Cybersecurity Certifications Preparing for the PMP Certification Signs You Will Get the Job After an Interview What Is Artificial Intelligence? Coursera About What We Offer Leadership Careers Catalog Coursera Plus Professional Certificates MasterTrack® Certificates Degrees For Enterprise For Government For Campus Become a Partner Social Impact Free Courses Share your Coursera learning story Community Learners Partners Beta Testers Blog The Coursera Podcast Tech Blog More Press Investors Terms Privacy Help Accessibility Contact Articles Directory Affiliates Modern Slavery Statement Cookies Preference Center Learn Anywhere © 2026 Coursera Inc. All rights reserved. | 2026-01-13T08:48:28 |
https://www.linkedin.com/help/linkedin/answer/710?trk=registration-frontend_join-form-page-help-link | Create a LinkedIn Page | LinkedIn Help Attention screen reader users, you are in a mobile optimized view and content may not appear where you expect it to be. To return the screen to its desktop view, please maximize your browser. Skip to content Skip to search Close jump menu Help LinkedIn Help Dropdown menu, expand to explore help for other LinkedIn products Close menu Get help with: LinkedIn Corporate Billing Learning Marketing Solutions Recruiter Sales Navigator Talent Insights Go to LinkedIn Sign in Sign in Create a LinkedIn Page Last updated: 6 months ago Create a LinkedIn Page Connect with clients, employees, and the LinkedIn community. Create You can create a LinkedIn Page for free, helping you represent and build your organization’s brand on LinkedIn. Pages can help LinkedIn members learn about your business, brand, products and services, and job opportunities. You must have a LinkedIn account to create a Page. Before you create one, we recommend reviewing our best practices. Important to know You can create a LinkedIn Page either using the desktop version or using the LinkedIn mobile app on an iOS device. Creating a LinkedIn Page is not supported on Android mobile devices. Desktop iOS To create a Page: Click the For Business icon in the upper-right corner of your LinkedIn homepage. Scroll down and click Create a Company Page . Select the Page type: Company Showcase page Educational institution Enter your Page identity, Company or Institution details , and Profile details information. Select the verification box to confirm that you have the right to act on behalf of the company or school. Click the Create page button. If you receive an error message, try our troubleshooting tips for creating your Page. Click Start building your page! to complete your LinkedIn Page. To create a Page: Go to any LinkedIn Page. Tap the More icon on the right and select Create a LinkedIn Page . Select the Page type: Company Educational institution Enter your Company name , LinkedIn public URL , Website , Industry , Company size , Company type , and Tagline (optional). Tap the verification box to confirm that you have the right to act on behalf of the company or school. Tap Create in the upper-right corner. Here's a tip As an admin, you can also convert your Page. Learn more about the different types of LinkedIn Pages . Results Once you’ve created a Page, you become the super admin of the Page and can assign others to be admins of your Page. Related tasks Troubleshoot creating a LinkedIn Page Complete Your LinkedIn Page Edit your LinkedIn Page or Showcase Page Claim a LinkedIn Listing Page Add admins on your LinkedIn Page LinkedIn Page admin roles permissions Convert your LinkedIn Page type Learn more LinkedIn Pages Create a LinkedIn Page best practices Differences between a LinkedIn profile and a LinkedIn Page Differences between LinkedIn Pages and Listing Pages Differences between a LinkedIn Page for a school and a company Tagged in Create Pages LinkedIn Contact us Select a language. The page will automatically refresh after a language has been selected. العربية (Arabic) বাংলা (Bangla) Čeština (Czech) Dansk (Danish) Deutsch (German) Ελληνικά (Greek) English (English) Español (Spanish) فارسی (Persian) Suomi (Finnish) Français (French) हिंदी (Hindi) Magyar (Hungarian) Bahasa Indonesia (Indonesian) Italiano (Italian) עברית (Hebrew) 日本語 (Japanese) 한국어 (Korean) मराठी (Marathi) Bahasa Malaysia (Malay) Nederlands (Dutch) Norsk (Norwegian) ਪੰਜਾਬੀ (Punjabi) Polski (Polish) Português (Portuguese) Română (Romanian) Русский (Russian) Svenska (Swedish) తెలుగు (Telugu) ภาษาไทย (Thai) Türkçe (Turkish) Українська (Ukrainian) Tiếng Việt (Vietnamese) 简体中文 (Chinese (Simplified)) 正體中文 (Chinese (Traditional)) LinkedIn Corporation © 2026 About Transparency Center Privacy and Terms Cookies Copyright Terms Privacy Guest controls Dismiss Privacy and Terms menu LinkedIn Corporation © 2026 | 2026-01-13T08:48:28 |
https://developer.x.com/developer-terms/policy#5-b | Developer Policy – X Developers | X Developer Platform <g> <g> <defs> <rect id="SVGID_1_" x="-468" y="-1360" width="1440" height="3027" /> </defs> <clippath id="SVGID_2_"> <use xlink:href="#SVGID_1_" style="overflow:visible;" /> </clippath> </g> </g> <rect x="-468" y="-1360" class="st0" width="1440" height="3027" style="fill:rgb(0,0,0,0);stroke-width:3;stroke:rgb(0,0,0)" /> <path d="M13.4,12l5.8-5.8c0.4-0.4,0.4-1,0-1.4c-0.4-0.4-1-0.4-1.4,0L12,10.6L6.2,4.8c-0.4-0.4-1-0.4-1.4,0c-0.4,0.4-0.4,1,0,1.4 l5.8,5.8l-5.8,5.8c-0.4,0.4-0.4,1,0,1.4c0.2,0.2,0.4,0.3,0.7,0.3s0.5-0.1,0.7-0.3l5.8-5.8l5.8,5.8c0.2,0.2,0.5,0.3,0.7,0.3 s0.5-0.1,0.7-0.3c0.4-0.4,0.4-1,0-1.4L13.4,12z" /> </svg>" data-icon-chevron-right="<svg xmlns="http://www.w3.org/2000/svg" width="24" height="24" viewbox="0 0 24 24" aria-hidden="true" focusable="false" role="none" class="twtr-icon"> <path opacity="0" d="M0 0h24v24H0z" /> <path d="M17.207 11.293l-7.5-7.5c-.39-.39-1.023-.39-1.414 0s-.39 1.023 0 1.414L15.086 12l-6.793 6.793c-.39.39-.39 1.023 0 1.414.195.195.45.293.707.293s.512-.098.707-.293l7.5-7.5c.39-.39.39-1.023 0-1.414z" /> </svg>" data-icon-chevron-down="<svg xmlns="http://www.w3.org/2000/svg" width="24" height="24" viewbox="0 0 24 24" aria-hidden="true" focusable="false" role="none" class="twtr-icon"> <path opacity="0" d="M0 0h24v24H0z" /> <path d="M20.207 7.043c-.39-.39-1.023-.39-1.414 0L12 13.836 5.207 7.043c-.39-.39-1.023-.39-1.414 0s-.39 1.023 0 1.414l7.5 7.5c.195.195.45.293.707.293s.512-.098.707-.293l7.5-7.5c.39-.39.39-1.023 0-1.414z" /> </svg>" data-icon-arrow-left="<svg width="28px" height="28px" viewbox="0 0 28 28" version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" aria-hidden="true" focusable="false" role="none" class="twtr-icon u01-meganav__icon-arrow-left"> <g stroke="none" stroke-width="1" fill="none" fill-rule="evenodd" stroke-linecap="round"> <g transform="translate(-1216.000000, -298.000000)" stroke-width="2.25"> <g transform="translate(1200.000000, 282.000000)"> <g transform="translate(17.000000, 17.000000)"> <path d="M0.756410256,12.8589744 L25.7179487,12.8589744"></path> <path d="M13.2371795,25.3397436 L25.7179487,12.8589744"></path> <path d="M13.2371795,12.4807692 L25.3397436,0.378205128" transform="translate(19.288462, 6.429487) rotate(-90.000000) translate(-19.288462, -6.429487) "></path> </g> </g> </g> </g> </svg>" data-left-nav-items="[{"isActive":false,"hasActiveChild":false,"children":[{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"X API","linkDisabled":false,"title":"X API","path":"https://developer.x.com/en/products/twitter-api"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"X Ads API","linkDisabled":false,"title":"X Ads API","path":"https://developer.x.com/en/products/x-ads-api"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"X for websites","linkDisabled":false,"title":"X for websites","path":"https://developer.x.com/en/products/x-for-websites"}],"overviewTitle":"Products","linkDisabled":true,"title":"Products","path":"https://developer.x.com/en/products"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Docs","linkDisabled":false,"title":"Docs","path":"https://docs.x.com/"},{"isActive":false,"hasActiveChild":false,"children":[{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Build for business","linkDisabled":false,"title":"Build for business","path":"https://developer.x.com/en/use-cases/build-for-businesses"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Build for the public","linkDisabled":false,"title":"Build for the public","path":"https://developer.x.com/en/use-cases/build-for-consumers"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Do research","linkDisabled":false,"title":"Do research","path":"https://developer.x.com/en/use-cases/do-research"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Teach \u0026 learn","linkDisabled":false,"title":"Teach \u0026 learn","path":"https://developer.x.com/en/use-cases/teach-and-learn"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Build for good","linkDisabled":false,"title":"Build for good","path":"https://developer.x.com/en/use-cases/build-for-good"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Build for fun","linkDisabled":false,"title":"Build for fun","path":"https://developer.x.com/en/use-cases/build-for-fun"}],"overviewTitle":"Use Cases","linkDisabled":true,"title":"Use Cases","path":"https://developer.x.com/en/navigation/left-nav-items/use-cases"},{"isActive":false,"hasActiveChild":false,"children":[{"isActive":false,"hasActiveChild":false,"children":[{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Changelog","linkDisabled":false,"title":"Changelog","path":"https://docs.x.com/updates/changelog"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Blog","linkDisabled":false,"title":"Blog","path":"https://developer.x.com/en/blog"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Newsletter","linkDisabled":false,"title":"Newsletter","path":"https://developer.x.com/en/updates/stay-informed"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"YouTube","linkDisabled":false,"title":"YouTube","path":"https://www.youtube.com/c/twitterdev"}],"linkDisabled":true,"title":"Stay informed","path":"https://developer.x.com/"},{"isActive":false,"hasActiveChild":false,"children":[{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Forums","linkDisabled":false,"title":"Forums","path":"https://twittercommunity.com/"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Events","linkDisabled":false,"title":"Events","path":"https://twitterdev.bevylabs.com/"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Insiders","linkDisabled":false,"title":"Insiders","path":"https://developer.twitter.com/en/community/insiders"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Community leaders","linkDisabled":false,"title":"Community leaders","path":"https://developer.x.com/en/community/leaders"}],"linkDisabled":true,"title":"Connect","path":"https://developer.x.com/"}],"overviewTitle":"Community","linkDisabled":false,"menuType":"multiCategory","title":"Community","path":"https://developer.x.com/en/community"}]" data-right-nav-items="[{"isActive":false,"hasActiveChild":false,"children":[{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Policies","linkDisabled":false,"title":"Policies","path":"https://developer.x.com/en/developer-terms"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Developer agreement","linkDisabled":false,"title":"Developer agreement","path":"https://developer.x.com/en/developer-terms/agreement-and-policy/source"}],"overviewTitle":"Support","linkDisabled":false,"title":"Support","path":"https://developer.x.com/en/support"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Developer Portal","linkDisabled":false,"title":"Developer Portal","path":"https://developer.twitter.com/en/portal/petition/essential/basic-info"}]" data-cta-enabled="true" data-profile-enabled="true" data-cta-link-new-tab="false" data-root-page-title="Developer Platform"> Developer terms Developer Policy Let's get started X + Developers Using this policy X + Developers Using this policy X + Developers X loves developers. We’re delighted and amazed by the tools and services this community creates by harnessing the power of X data. As part of our commitment to this community, we aim to provide data access that is open and fair for developers, safe for people on X, and beneficial for the X platform as a whole. To further these goals we’ve crafted the Developer Policy as a guide to help people understand our rules and expectations about appropriate API and X Content usage. This Developer Policy (“ Policy ”) provides rules and guidelines for developers who interact with X’s ecosystem of applications, services, website, web pages and content. It is part of your contract with X governing access to and use of the X API and X Content (either as part of the Developer Agreement or other written agreement with X). Policy violations are considered violations of your agreement. This Policy may be changed from time to time without notice. Capitalized terms used in this Policy, which are not defined in this Policy, will have the respective meanings ascribed to them in the Developer Agreement or the Master License Agreement. Using this policy We’ve structured this policy to make it as easy to follow as possible. Please keep information from the following policy sections top of mind as you use the X API and X Content: 1. Set Yourself Up for Success - You are responsible for complying with all X policies. It’s important that you review and understand this Policy, as well as the policies we link to in this document, before you access the X API and X Content. The time spent reviewing our policies may save you hours of rework down the road. 2. Privacy and Control are Essential - Protecting and defending the privacy of people on X is built into the core DNA of our company. As such, we prohibit the use of X data in any way that would be inconsistent with people’s reasonable expectations of privacy. By building on the X API or accessing X Content, you have a special role to play in safeguarding this commitment, most importantly by respecting people’s privacy and providing them with transparency and control over how their data is used. 3. Follow the Platform Usage Guidelines - Getting approved to access the X API and X Content is just the first step. Our Platform Usage Guidelines should be your first stop anytime you have questions about how to ensure policy compliance for your planned use of the X platform. We’ve provided a lot more detail on what each of these three key sections mean below. Please review them carefully to ensure that your usage of the X API and X Content is consistent with our policies. If we believe you are in violation of this Policy (or any other X policy), we may suspend or permanently revoke your access to the X API and X Content. Finally, please note that X may monitor your use of the X API to improve the X Applications, to examine any commercial use, and to ensure your compliance with your approved use case and this Policy. Thanks for reading, and thank you for building with us! We look forward to seeing what you create! Chapter 1 Set yourself up for success Set yourself up for success Set yourself up for success Set yourself up for success You can avoid many potential pitfalls while using the X API by ensuring that your service has been built the right way from day 1. This section of the Developer Policy contains rules that all developers must follow before using the X API or X Content. The Free, Basic, and Pro plans (as described at developer.x.com/en ) are designed for hobbyists, commercial prototyping, early-stage X product integrations, and supporting applications with limited end-users. If you use the X API and X Content beyond this scope, then you must apply (or already subscribe to) an Enterprise plan (as described at developer.x.com/en ). We review all proposed uses of the X developer platform to verify policy compliance — so you’re required to disclose (and update, as applicable) your planned use of the X API and X Content in order to be granted and to maintain access. All new developers must apply for a developer account to access the X API. Current developers without an approved developer account must apply for one as directed to do so by X. As part of this process, you’ll need to provide us with a written description of your intended uses of the X API and X Content. Your use case description is binding on you, and any substantive deviation from it may constitute a violation of our rules and result in enforcement action. You must notify us of any substantive modification to your use case and receive approval before you may begin using X Content for that new purpose. Failure to do so may result in suspension and termination of your API and data access. By building on the X API or accessing X Content, you must comply with ALL X policies. These include this Developer Policy , the Automation Rules , the Display Requirements , the API Restricted Uses Rules , the X Rules , and the X Brand Resources , as well as any other agreements you enter into with X relating to your use of the X API or X Content, including but not limited to the Developer Agreement or a Master Licensing Agreement or Order (as applicable). You must also comply with any modifications to these policies and any new policies launched by X. It is your responsibility to monitor the use of your service and to design your service to prevent violations of X policy by people who use it. Failure to do so may result in suspension or termination of your API and X Content access. You may not register multiple applications for a single use case or substantially similar or overlapping use cases. In this context, a “use case” is a consistent set of analyses, displays, or actions performed via an application. "White label" versions of a tool or service are not permissible. If you plan to “white label” versions of your application, you must notify and receive separate approval from us. As a single exception to these rules, you may create and use a maximum of 3 applications for development, staging, and production instances of the same service. These apps must be registered to a single account, and should be clearly identified (in the name and description) as dev, staging, and prod instances of a single service. You may not use development or staging applications for production purposes. You must keep all API keys or other access credentials private. You may not use, and may not encourage or facilitate others to use, API keys or other access credentials owned by others. Your license agreement with X limits your use of the X API and X Content. Among other things, the X API has rate limits which help to ensure fair data usage and to combat spam on the platform. You may not exceed or circumvent rate limits, or any other limitations or restrictions described in this Policy or your agreement with X, listed on the Developer Site , or communicated to you by X. You may not remove or alter any proprietary notices or marks on X Content received via the X API. This helps to make sure that people know where X Content is coming from, and who it belongs to. For data integrity and platform health reasons, you may not interfere with, intercept, disrupt, or disable any features of the X API or the X service. In other words, use the APIs as intended and documented on developer.x.com . Refer to our HackerOne guidelines for more details about acceptable use. Chapter 2 Privacy and control are essential Privacy and control are essential Consent & permissions Content compliance Off-X matching Your privacy policy Using geo-data X passwords Privacy and control are essential Consent & permissions Content compliance Off-X matching Your privacy policy Using geo-data X passwords Privacy and control are essential X takes privacy seriously, and we expect everyone using X Content and the X API to do the same. Any use of the X developer platform, X API, or X Content in a manner that is inconsistent with peoples’ reasonable expectations of privacy may be subject to enforcement action, which can include suspension and termination of API and X Content access. Your commitment to privacy and control must extend to all uses of X Content and all aspects of the service that you build using our API. To that end, the people using your service must understand and consent to how you use their data, and how you access X on their behalf. This can be accomplished through providing people with a clear, comprehensive, and transparent privacy policy, as well as ensuring that you get express and informed consent from each person using your service before taking any action on their behalf. Please note that a person authenticating into your service does not by itself constitute consent. Consent & permissions In particular, you must get express and informed consent from people before doing any of the following: Taking any actions on their behalf. This includes (but is not limited to): Posting content to X Following/unfollowing accounts Modifying profile or account information Adding hashtags or any other content to Posts Republishing content accessed by means other than via the X API or other X tools Using someone’s X Content to promote a product or service Storing non-public content such as Direct Messages (DMs), or any other private or confidential information Sharing or publishing protected content, or any other private or confidential information If your service allows people to post content to X you must do the following before publishing: Show exactly what will be published Make it clear to people using your service what geo information (if any) will be added to the content If your service allows people to post content to both your service and X, you must do the following before publishing: Obtain permission to post the content Explain where you will post the content You must respect the protected and blocked status of all X Content. You may not serve content obtained using one person’s authentication token to a different person who is not authorized to view that content. Protected accounts: A protected account ’s content is only available to people who have been approved by the owner to follow that account. So, if you run a service that accesses protected accounts, you may only do so to serve such content to the specific people with permission to view that content. Blocked accounts: People on X are able to block access to their accounts for any reason they choose. Commingling information obtained from tokens (or any other API-based action) to bypass this choice is not permitted. As Direct Messages (DMs) are non-public in nature, services that provide DM features must take extra steps to safeguard personal privacy. You may not serve DM content to people who are not authorized to view that content. If your service provides DM functionality you must also: Notify people if you send read receipt events for DMs. You can do this by providing a notice directly in your service, or by displaying read receipts from other participants in a conversation. Get consent before configuring media to be sent in a DM as "shared" (i.e. reusable across multiple DMs). If you do allow media in a DM to be “shared,” you must provide a clear notice that this content will be accessible to anyone with the media’s URL. Content compliance If you store X Content offline, you must keep it up to date with the current state of that content on X. Specifically, you must delete or modify any content you have if it is deleted or modified on X. This must be done as soon as reasonably possible, or within 24 hours after receiving a request to do so by X or the applicable X account owner, or as otherwise required by your agreement with X or applicable law. This must be done unless otherwise prohibited by law, and only then with the express written permission of X. Modified content can take various forms. This includes (but is not limited to): Content that has been made private or gained protected status Content that has been suspended from the platform Content that has had geotags removed from it Content that has been withheld or removed from X Off-X matching We limit the circumstances under which you may match a person on X to information obtained or stored off-X. Off-X matching involves associating X Content, including a X @handle or user ID, with a person, household, device, browser, or other off-X identifier. You may only do this if you have express opt-in consent from the person before making the association, or as described below. In situations in which you don’t have a person’s express, opt-in consent to link their Xidentity to an off-X identifier, we require that any connection you draw be based only on information that someone would reasonably expect to be used for that purpose. In addition, absent a person’s express opt-in consent you may only attempt to match your records about someone to a X identity based on: Information provided directly to you by the person. Note that records about individuals with whom you have no prior relationship, including data about individuals obtained from third parties, do not meet this standard; and/or Public data. “Public data” in this context refers to: Information about a person that you obtained from a public, generally-available resource (such as a directory of members of a professional association) Information on X about a person that is publicly available, including: Posts Profile information, including an account bio and publicly-stated location Display name and @handle Your privacy policy You must display your service’s privacy policy to people before they are permitted to download, install, or sign up to your service. It must disclose at least the following information: The information that you collect from people who use your service How you use and share that information (including with X) How people can contact you with inquiries and requests regarding their information Your privacy policy must be consistent with all applicable laws, and be no less protective of people than X’s Privacy Policy and the privacy policy of our other services and corporate affiliates . You must cease your access to the X API and the use of all X Content if you are unable to comply with your and/or X’s Privacy Policy. Using geo-data Use of geo data comes with additional restrictions due to the sensitive nature of this information. If your service adds location information to Posts, you must disclose to people: When you add location information Whether you add location information as a geotag or annotations data Whether your location information is listed as a place, or as geographic coordinates If your application allows people to post with their location you must comply with X’s geo guidelines in full. Any use of location data or geographic information on a standalone basis is prohibited. You may not (and may not permit others to) store, aggregate, or cache location data and other geographic information contained in X Content, except as part of a Post. For example, you may not separate location data or geographic information out from Posts to show where individuals have been over time. Heat maps and related tools that show aggregated geo activity (e.g., the number of people in a city using a hashtag) are permitted. X passwords You may not store X passwords, or request that people provide their X password, account credentials, or developer application information (including consumer key) to you directly. We suggest the use of Sign-in with X as the authentication tool to link your service and people on X. Chapter 3 Platform usage guidelines Platform usage guidelines Spam, bots, and automation X performance benchmarking Public display of Posts Content redistribution Pay to engage Service authenticy X name, logo, and likeness Advertising on X Platform usage guidelines Spam, bots, and automation X performance benchmarking Public display of Posts Content redistribution Pay to engage Service authenticy X name, logo, and likeness Advertising on X Platform usage guidelines Have you taken care to review X’s policies and set up your API access the right way? Does your service follow X’s privacy and control guidelines? If you can answer yes to these two questions, then you are ready to start using the X API and X Content. X’s Platform Usage Guidelines provide the assistance needed to ensure that your use of X Content is compliant from day 1 throughout the lifecycle of your service. We suggest reviewing these rules on a regular basis to make sure that your integration is operating in a way that is safe and beneficial to people on X and the X platform as a whole. Spam, bots, and automation The use of the X API and developer products to create spam, or engage in any form of platform manipulation, is prohibited. You should review the X Rules on platform manipulation and spam , and ensure that your service does not, and does not enable people to, violate our policies. Services that perform write actions, including posting Posts, following accounts, or sending Direct Messages, must follow the Automation Rules . In particular, you should: Always get explicit consent before sending people automated replies or Direct Messages Immediately respect requests to opt-out of being contacted by you Never perform bulk, aggressive, or spammy actions, including bulk following Never post identical or substantially similar content across multiple accounts If you’re operating an API-based bot account you must clearly indicate what the account is and who is responsible for it. You should never mislead or confuse people about whether your account is or is not a bot. A good way to do this is by including a statement that the account is a bot in the profile bio. X performance benchmarking You may not use the X API to measure the availability, performance, functionality, or usage of X for benchmarking, competitive, or commercial purposes. For example, you should never use the X API to: Calculate aggregate X metrics, such as the total number of Monthly Actives (MAs) or Daily Actives (DAs) Calculate aggregate X Post metrics, such as the total number of Posts posted per day, or the number of account engagements Measure or analyze the responsiveness of X Measure or analyze spam or security on X, except as permitted below We support research that helps improve conversational health on X. You may not publicly disclose any research or findings concerning, or develop, create, or offer services using, the X API or X Content that measure, analyze, or attempt to identify behaviors or content which violate X policies without express written permission from X. DSA Researchers: If you need to contact X relating to access under Art. 40 of the Digital Services Act, please contact EU-Questions@X.com . If you wish to apply for researcher access, please submit an application . Public display of Posts You must maintain the integrity of all X Content that you display publicly or to people who use your service. If you don’t use X for Websites to display content, then you must use the X API to retrieve the most current version available for display. If displayed content ceases to be available through the X API, then you must remove it from your service as soon as reasonably possible, or within 24 hours after the receipt of a removal request from X, or the applicable X account owner, or as otherwise required by applicable law. There are specific rules you must follow if you display X Content offline. Follow the guidelines for using Posts in broadcast if you display Posts offline. If you embed or display Posts, you must contact us about your X API access if your site exceeds 10 million daily impressions. X reserves the right to require additional terms as a condition to your use of the X API. Additional restrictions on X for Websites developer use include: Embedded Posts and/or embedded timelines You must provide people with legally sufficient notice that fully discloses X’s collection and use of data about browsing activities on your website, including for interest-based advertising and personalization. You must also obtain legally sufficient consent from people for such collection and use You must provide legally sufficient instructions on how people can opt out of X’s interest-based advertising and personalization as described here X for Websites widgets You must ensure that people are provided with clear and comprehensive information about, and consent to, the storing and accessing of cookies or other information on their devices as described in X’s cookie use , where providing such information and obtaining such consent is required by law Services targeted to children under 13 Services targeted to children under 13 must opt out of tailoring X in any embedded Post and/or embedded timelines by setting the opt-out parameter to be ‘true’ as described here Content redistribution The best place to get X Content is directly from X. Consequently, we restrict the redistribution of X Content to third parties. If you provide X Content to third parties, including downloadable datasets or via an API, you may only distribute Post IDs, Direct Message IDs, and/or User IDs (except as described below). In total, you may not distribute more than 1,500,000 Post IDs to any entity (inclusive of multiple individuals associated with a single entity) within any 30 day period unless you have received written permission from X. In addition, developers may provide up to 500 public Posts Objects and/or User Objects to each person who uses your service on a daily basis if this is done via non-automated means (e.g., download of spreadsheets or PDFs). Academic researchers are permitted to distribute Post IDs and/or User IDs solely for the purposes of non-commercial research on behalf of an academic institution, and that has been approved by X in writing, or peer review or validation of such research. Only as many Post IDs or User IDs that is necessary for such research, and has been approved by X may be used. Any X Content provided to third parties remains subject to this Policy, and those third parties must agree to the X Terms of Service , Privacy Policy , Developer Agreement , and Developer Policy before receiving such downloads. You may not enable any entity to circumvent any other limitations or restrictions on the distribution of X Content as contained in this Policy , the Developer Agreement , or any other agreement with X. Note: This Section does not apply to researchers with X API access via Art. 40 of the EU Digital Services Act (2022) (“ DSA ”), who are instead subject to the procedures and restrictions set forth in the DSA and the Developer Agreement. Pay to engage Your service shouldn’t compensate people to take actions on X, as that results in inauthentic engagement that degrades the health of the platform. As you use the X API you may not sell or receive monetary or virtual compensation for any X actions. This includes, but is not limited to, Posts, follows, unfollows, reposts, likes, comments, and replies. Service authenticity You must clearly identify your service so that people can understand its source and purpose. Don’t use names, logos, or URLs that mask your service’s identity and features, or that falsely imply an affiliation with X or third parties. Note that creating applications for the purpose of selling names, or to prevent others from using names, is prohibited. You may not use any URL (including shortened URLs) for your service that directs people to: A site that is unrelated to your service A spam or malware site A site that encourages people to violate X policy X name, logo, and likeness You may only use and display the X name and logo to identify X as the source of X Content. You should never use the X name and logo, the X Official Partner Program badge, or any other similar marks or names in a manner that creates a false sense of endorsement, sponsorship, or association with X. The X Brand Resources contain detailed information to help you use the X brand in the right way. You may only use the X Verified Account badge and any other enhanced account categorization as it is reported to you by X through the API. This helps people know that the content your service displays is equivalent to that shown on X. Advertising on X There are restrictions regarding how and where you are allowed to advertise around X Content. To start, your advertisements can’t resemble or reasonably be confused by people as a Post. Other rules on advertising include: There must be a clear separation between X Content and your advertisements. You may not place any advertisements within the X timeline other than X Ads. X reserves the right to serve advertising via the X API. If you decide to serve X Ads once we start delivering them via the API, we will share a portion of advertising revenue with you in accordance with the relevant terms and conditions. You may not use X Content, or information obtained from the X API to target people with advertising outside of the X platform. Chapter 4 Rules for specific X services or features X login X Cards Definitions X login X Cards Definitions The following additional rules apply for any use of the X services or features listed below: X login You must present people with easy to find options to log into and out of X, for example via the OAuth protocol. The Sign in with X option must be displayed at least as prominently as any other sign-up or sign-in feature on your service. You must also provide people without a X account the opportunity to create one via X. Once someone on your service authenticates via Sign in with X you must clearly display their X identity. X identity includes the person’s current X @handle, avatar, and X logo. Any display of someone’s X followers on your service must clearly show that the relationship is associated with X. X Cards To ensure a quality experience you must develop your Card to render across all platforms where Cards are displayed. Additional rules that you must follow when using Cards include: You must mark your Post as ‘true’ for sensitive media if you plan to display such media within a Card You must use HTTPS for hosting all assets within your Card. Your Card should never generate active mixed content browser warnings Audio and video content should include stop or pause controls, and default to ‘sound off’ for videos that automatically play content You may not exceed or circumvent X’s limitations placed on any Cards, including the Card’s intended use. Additional restrictions on Cards use include: You may not place third-party sponsored content within Cards without X’s approval You may not attach monetary incentives (including virtual currency) within your Card or on X from your Card You may not include content or actions within your Card that are misleading or not contextually relevant, such as URLs and media You may only attach an App Card to a Post when someone is explicitly promoting or referring to the app in the Post Definitions X Content ‒ Posts, Post IDs, X end user profile information, and any other data and information made available to you through the X API or by any other means authorized by X, and any copies and derivative works thereof. Developer Site ‒ X’s developer site located at https://developer.x.com . Services ‒ Your websites, applications and other offerings that display X Content or otherwise use the Licensed Material as explicitly approved by X. Post ID ‒ A unique identification number generated for each Post. Post ‒ A posting made on X Applications. “X” ‒ Means (a) X Corp. (865 FM 1209, Building 2, Bastrop, TX 78602, USA) if your principal place of business is outside the European Union, EFTA States, and the United Kingdom; or (b) X Internet Unlimited Company (One Cumberland Place, Fenian Street, Dublin 2, D02 AX07, Ireland) if your principal place of business is in the European Union, EFTA States, or the United Kingdom. Direct Message - A message that is privately sent on X Applications by one end user to one or more specific end user(s) using X’s Direct Message function. X API ‒ The X Application Programming Interface (“API”), Software Development Kit (“SDK”) and/or the related documentation, data, code, and other materials provided by X with the API, as updated from time to time, including without limitation through the Developer Site. X Applications ‒ X’s consumer facing products, services, applications, websites, web pages, platforms, and other offerings, including without limitation, those offered via https://x.com and X's mobile applications. Developer policy and terms Follow @XDevelopers Subscribe to developer news X platform X.com Status Accessibility Embed a post Privacy Center Transparency Center Download the X app Try Grok.com X Corp. About the company Company news Brand toolkit Jobs and internships Investors Help Help Center Using X X for creators Ads Help Center Managing your account Email Preference Center Rules and policies Contact us Developer resources Developer home Documentation Forums Communities Developer blog Engineering blog Developer terms Business resources Advertise X for business Resources and guides X for marketers Marketing insights Brand inspiration X Ads Academy © 2026 X Corp. Cookies Privacy Terms and conditions Did someone say … cookies? X and its partners use cookies to provide you with a better, safer and faster service and to support our business. Some cookies are necessary to use our services, improve our services, and make sure they work properly. Show more about your choices . Accept all cookies Refuse non-essential cookies | 2026-01-13T08:48:28 |
https://dev.to/beck_moulton/stop-sending-sensitive-data-to-the-cloud-build-a-local-first-mental-health-ai-with-webllm-5100#comments | Stop Sending Sensitive Data to the Cloud: Build a Local-First Mental Health AI with WebLLM - DEV Community Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account DEV Community Close Add reaction Like Unicorn Exploding Head Raised Hands Fire Jump to Comments Save Boost More... Copy link Copy link Copied to Clipboard Share to X Share to LinkedIn Share to Facebook Share to Mastodon Share Post via... Report Abuse Beck_Moulton Posted on Jan 13 Stop Sending Sensitive Data to the Cloud: Build a Local-First Mental Health AI with WebLLM # privacy # typescript # webgpu # webllm In an era where data breaches are common, privacy in Edge AI has moved from a "nice-to-have" to a "must-have," especially in sensitive fields like healthcare. If you've ever worried about your private conversations being used to train a massive corporate model, you're not alone. Today, we are exploring the frontier of Privacy-preserving AI by building a medical Q&A bot that runs entirely on the client side. By leveraging WebLLM , WebGPU , and TVM Unity , we can now execute large language models directly in the browser. This means the dialogue never leaves the user's device, providing a truly decentralized and secure experience. For those looking to scale these types of high-performance implementations, I highly recommend checking out the WellAlly Tech Blog for more production-ready patterns on enterprise-grade AI deployment. The Architecture: Why WebGPU? Traditional AI apps send a request to a server (Python/FastAPI), which queries a GPU (NVIDIA A100), and sends a JSON response back. This "Client-Server" model is the privacy killer. Our "Local-First" approach uses WebGPU , the next-gen graphics API for the web, to tap into the user's hardware directly. graph TD subgraph User_Device [User Browser / Device] A[React UI Layer] -->|Dispatch| B[WebLLM Worker] B -->|Request Execution| C[TVM Unity Runtime] C -->|Compute Kernels| D[WebGPU API] D -->|Inference| E[VRAM / GPU Hardware] E -->|Streaming Text| B B -->|State Update| A end F((Public Internet)) -.->|Static Assets & Model Weights| A F -.->|NO PRIVATE DATA SENT| A Enter fullscreen mode Exit fullscreen mode Prerequisites Before we dive in, ensure you have a browser that supports WebGPU (Chrome 113+ or Edge). Framework : React (Vite template) Language : TypeScript AI Engine : @mlc-ai/web-llm Core Tech : WebGPU & TVM Unity Step 1: Initializing the Engine Running an LLM in a browser requires significant memory management. We use a Web Worker to ensure the UI doesn't freeze while the model is "thinking." // engine.ts import { CreateMLCEngine , MLCEngineConfig } from " @mlc-ai/web-llm " ; const modelId = " Llama-3-8B-Instruct-v0.1-q4f16_1-MLC " ; // Lightweight quantized model export async function initializeEngine ( onProgress : ( p : number ) => void ) { const engine = await CreateMLCEngine ( modelId , { initProgressCallback : ( report ) => { onProgress ( Math . round ( report . progress * 100 )); console . log ( report . text ); }, }); return engine ; } Enter fullscreen mode Exit fullscreen mode Step 2: Creating the Privacy-First Chat Hook In a medical context, the system prompt is critical. We need to instruct the model to behave as a supportive assistant while maintaining strict safety boundaries. // useChat.ts import { useState } from ' react ' ; import { initializeEngine } from ' ./engine ' ; export const useChat = () => { const [ engine , setEngine ] = useState < any > ( null ); const [ messages , setMessages ] = useState < { role : string , content : string }[] > ([]); const startConsultation = async () => { const instance = await initializeEngine (( p ) => console . log ( `Loading: ${ p } %` )); setEngine ( instance ); // Set the System Identity for Mental Health await instance . chat . completions . create ({ messages : [{ role : " system " , content : " You are a private, empathetic mental health assistant. Your goal is to listen and provide support. You do not store data. If a user is in danger, provide emergency resources immediately. " }], }); }; const sendMessage = async ( input : string ) => { const newMessages = [... messages , { role : " user " , content : input }]; setMessages ( newMessages ); const reply = await engine . chat . completions . create ({ messages : newMessages , }); setMessages ([... newMessages , reply . choices [ 0 ]. message ]); }; return { messages , sendMessage , startConsultation }; }; Enter fullscreen mode Exit fullscreen mode Step 3: Optimizing for Performance (TVM Unity) The magic behind WebLLM is TVM Unity , which compiles models into highly optimized WebGPU kernels. This allows us to run models like Llama-3 or Mistral at impressive tokens-per-second on a standard Macbook or high-end Windows laptop. If you are dealing with advanced production scenarios—such as model sharding or custom quantization for specific medical datasets—the team at WellAlly Tech has documented extensive guides on optimizing WebAssembly runtimes for maximum throughput. Step 4: Building the React UI A simple, clean interface is best for mental health applications. We want the user to feel calm and secure. // ChatComponent.tsx import React , { useState } from ' react ' ; import { useChat } from ' ./useChat ' ; export const MentalHealthBot = () => { const { messages , sendMessage , startConsultation } = useChat (); const [ input , setInput ] = useState ( "" ); return ( < div className = "p-6 max-w-2xl mx-auto border rounded-xl shadow-lg bg-white" > < h2 className = "text-2xl font-bold mb-4" > Shielded Mind AI 🛡️ </ h2 > < p className = "text-sm text-gray-500 mb-4" > Status: < span className = "text-green-500" > Local Only (Encrypted by Hardware) </ span ></ p > < div className = "h-96 overflow-y-auto mb-4 p-4 bg-gray-50 rounded" > { messages . map (( m , i ) => ( < div key = { i } className = { `mb-2 ${ m . role === ' user ' ? ' text-blue-600 ' : ' text-gray-800 ' } ` } > < strong > { m . role === ' user ' ? ' You: ' : ' AI: ' } </ strong > { m . content } </ div > )) } </ div > < div className = "flex gap-2" > < input className = "flex-1 border p-2 rounded" value = { input } onChange = { ( e ) => setInput ( e . target . value ) } placeholder = "How are you feeling today?" /> < button onClick = { () => { sendMessage ( input ); setInput ( "" ); } } className = "bg-purple-600 text-white px-4 py-2 rounded hover:bg-purple-700" > Send </ button > </ div > < button onClick = { startConsultation } className = "mt-4 text-xs text-gray-400 underline" > Initialize Secure WebGPU Engine </ button > </ div > ); }; Enter fullscreen mode Exit fullscreen mode Challenges & Solutions Model Size : Downloading a 4GB-8GB model to a browser is the biggest hurdle. Solution : Use IndexedDB caching so the user only downloads the model once. VRAM Limits : Mobile devices may struggle with large context windows. Solution : Implement sliding window attention and aggressive 4-bit quantization. Cold Start : The initial "Loading" phase can take time. Solution : Use a skeleton screen and explain that this process ensures their privacy. Conclusion By moving the "brain" of our AI from the cloud to the user's browser, we've created a psychological safe space that is literally impossible for hackers to intercept at the server level. WebLLM and WebGPU are turning browsers into powerful AI engines. Want to dive deeper into Edge AI security , LLM Quantization , or WebGPU performance tuning ? Head over to the WellAlly Tech Blog where we break down the latest advancements in local-first software architecture. What do you think? Would you trust a local-only AI more than ChatGPT for sensitive topics? Let me know in the comments below! 👇 Top comments (0) Subscribe Personal Trusted User Create template Templates let you quickly answer FAQs or store snippets for re-use. Submit Preview Dismiss Code of Conduct • Report abuse Are you sure you want to hide this comment? It will become hidden in your post, but will still be visible via the comment's permalink . Hide child comments as well Confirm For further actions, you may consider blocking this person and/or reporting abuse Beck_Moulton Follow Joined Aug 22, 2022 More from Beck_Moulton Private & Fast: Building a Browser-Based Dermatology Screener with WebLLM and WebGPU # privacy # ai # web # webdev Federated Learning or Bust: Architecting Privacy-First Health AI # machinelearning # architecture # privacy # devops Why Your Health Data Belongs on Your Device (Not the Cloud): A Local-First Manifesto # architecture # privacy # offlinefirst # database 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV DEV Community — A space to discuss and keep up software development and manage your software career Home DEV++ Podcasts Videos DEV Education Tracks DEV Challenges DEV Help Advertise on DEV DEV Showcase About Contact Free Postgres Database Software comparisons Forem Shop Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . DEV Community © 2016 - 2026. We're a place where coders share, stay up-to-date and grow their careers. Log in Create account | 2026-01-13T08:48:28 |
https://docs.suprsend.com/docs/workspace | Page Not Found Skip to main content SuprSend, Notification infrastructure for Product teams home page Search... ⌘ K Community Trust Center Platform Status Postman Collection GETTING STARTED What is SuprSend? Quick Start Guide Best Practices Plan Your Integration Go-live checklist CORE CONCEPTS Templates Users Events Workflow Notification Categories Preferences Tenants Lists Broadcast Objects Translations DLT Guidelines Whatsapp Template Guidelines WORKFLOW BUILDER Design Workflow Node List Workflow Settings Trigger Workflow Validate Trigger Payload Tenant Workflows Notification Inbox Overview Multi Tabs React Javascript (Angular, Vuejs etc) React Native Flutter (Headless) PREFERENCE CENTRE Embedded Preference Centre Javascript Angular React VENDOR INTEGRATION GUIDE Overview Email Integrations SMS Integrations Android Push Whatsapp Integrations iOS Push Chat Integrations Vendor Fallback Tenant Vendor INTEGRATIONS Webhook Connectors MONITORING & DEBUGGING Logs Audit Logs Error Guides MANAGE YOUR ACCOUNT Authentication Methods Contact Us Get Started SuprSend, Notification infrastructure for Product teams home page Search... ⌘ K Ask AI Contact Us Get Started Get Started Search... Navigation Page Not Found Documentation API Reference Management API CLI Reference Developer Resources Changelog Documentation API Reference Management API CLI Reference Developer Resources Changelog 404 Page Not Found We couldn't find the page. Maybe you were looking for one of these pages below? List Workflows Pull Workflows Email ⌘ I | 2026-01-13T08:48:28 |
https://developer.x.com/developer-terms/policy#3-e | Developer Policy – X Developers | X Developer Platform <g> <g> <defs> <rect id="SVGID_1_" x="-468" y="-1360" width="1440" height="3027" /> </defs> <clippath id="SVGID_2_"> <use xlink:href="#SVGID_1_" style="overflow:visible;" /> </clippath> </g> </g> <rect x="-468" y="-1360" class="st0" width="1440" height="3027" style="fill:rgb(0,0,0,0);stroke-width:3;stroke:rgb(0,0,0)" /> <path d="M13.4,12l5.8-5.8c0.4-0.4,0.4-1,0-1.4c-0.4-0.4-1-0.4-1.4,0L12,10.6L6.2,4.8c-0.4-0.4-1-0.4-1.4,0c-0.4,0.4-0.4,1,0,1.4 l5.8,5.8l-5.8,5.8c-0.4,0.4-0.4,1,0,1.4c0.2,0.2,0.4,0.3,0.7,0.3s0.5-0.1,0.7-0.3l5.8-5.8l5.8,5.8c0.2,0.2,0.5,0.3,0.7,0.3 s0.5-0.1,0.7-0.3c0.4-0.4,0.4-1,0-1.4L13.4,12z" /> </svg>" data-icon-chevron-right="<svg xmlns="http://www.w3.org/2000/svg" width="24" height="24" viewbox="0 0 24 24" aria-hidden="true" focusable="false" role="none" class="twtr-icon"> <path opacity="0" d="M0 0h24v24H0z" /> <path d="M17.207 11.293l-7.5-7.5c-.39-.39-1.023-.39-1.414 0s-.39 1.023 0 1.414L15.086 12l-6.793 6.793c-.39.39-.39 1.023 0 1.414.195.195.45.293.707.293s.512-.098.707-.293l7.5-7.5c.39-.39.39-1.023 0-1.414z" /> </svg>" data-icon-chevron-down="<svg xmlns="http://www.w3.org/2000/svg" width="24" height="24" viewbox="0 0 24 24" aria-hidden="true" focusable="false" role="none" class="twtr-icon"> <path opacity="0" d="M0 0h24v24H0z" /> <path d="M20.207 7.043c-.39-.39-1.023-.39-1.414 0L12 13.836 5.207 7.043c-.39-.39-1.023-.39-1.414 0s-.39 1.023 0 1.414l7.5 7.5c.195.195.45.293.707.293s.512-.098.707-.293l7.5-7.5c.39-.39.39-1.023 0-1.414z" /> </svg>" data-icon-arrow-left="<svg width="28px" height="28px" viewbox="0 0 28 28" version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" aria-hidden="true" focusable="false" role="none" class="twtr-icon u01-meganav__icon-arrow-left"> <g stroke="none" stroke-width="1" fill="none" fill-rule="evenodd" stroke-linecap="round"> <g transform="translate(-1216.000000, -298.000000)" stroke-width="2.25"> <g transform="translate(1200.000000, 282.000000)"> <g transform="translate(17.000000, 17.000000)"> <path d="M0.756410256,12.8589744 L25.7179487,12.8589744"></path> <path d="M13.2371795,25.3397436 L25.7179487,12.8589744"></path> <path d="M13.2371795,12.4807692 L25.3397436,0.378205128" transform="translate(19.288462, 6.429487) rotate(-90.000000) translate(-19.288462, -6.429487) "></path> </g> </g> </g> </g> </svg>" data-left-nav-items="[{"isActive":false,"hasActiveChild":false,"children":[{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"X API","linkDisabled":false,"title":"X API","path":"https://developer.x.com/en/products/twitter-api"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"X Ads API","linkDisabled":false,"title":"X Ads API","path":"https://developer.x.com/en/products/x-ads-api"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"X for websites","linkDisabled":false,"title":"X for websites","path":"https://developer.x.com/en/products/x-for-websites"}],"overviewTitle":"Products","linkDisabled":true,"title":"Products","path":"https://developer.x.com/en/products"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Docs","linkDisabled":false,"title":"Docs","path":"https://docs.x.com/"},{"isActive":false,"hasActiveChild":false,"children":[{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Build for business","linkDisabled":false,"title":"Build for business","path":"https://developer.x.com/en/use-cases/build-for-businesses"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Build for the public","linkDisabled":false,"title":"Build for the public","path":"https://developer.x.com/en/use-cases/build-for-consumers"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Do research","linkDisabled":false,"title":"Do research","path":"https://developer.x.com/en/use-cases/do-research"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Teach \u0026 learn","linkDisabled":false,"title":"Teach \u0026 learn","path":"https://developer.x.com/en/use-cases/teach-and-learn"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Build for good","linkDisabled":false,"title":"Build for good","path":"https://developer.x.com/en/use-cases/build-for-good"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Build for fun","linkDisabled":false,"title":"Build for fun","path":"https://developer.x.com/en/use-cases/build-for-fun"}],"overviewTitle":"Use Cases","linkDisabled":true,"title":"Use Cases","path":"https://developer.x.com/en/navigation/left-nav-items/use-cases"},{"isActive":false,"hasActiveChild":false,"children":[{"isActive":false,"hasActiveChild":false,"children":[{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Changelog","linkDisabled":false,"title":"Changelog","path":"https://docs.x.com/updates/changelog"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Blog","linkDisabled":false,"title":"Blog","path":"https://developer.x.com/en/blog"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Newsletter","linkDisabled":false,"title":"Newsletter","path":"https://developer.x.com/en/updates/stay-informed"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"YouTube","linkDisabled":false,"title":"YouTube","path":"https://www.youtube.com/c/twitterdev"}],"linkDisabled":true,"title":"Stay informed","path":"https://developer.x.com/"},{"isActive":false,"hasActiveChild":false,"children":[{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Forums","linkDisabled":false,"title":"Forums","path":"https://twittercommunity.com/"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Events","linkDisabled":false,"title":"Events","path":"https://twitterdev.bevylabs.com/"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Insiders","linkDisabled":false,"title":"Insiders","path":"https://developer.twitter.com/en/community/insiders"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Community leaders","linkDisabled":false,"title":"Community leaders","path":"https://developer.x.com/en/community/leaders"}],"linkDisabled":true,"title":"Connect","path":"https://developer.x.com/"}],"overviewTitle":"Community","linkDisabled":false,"menuType":"multiCategory","title":"Community","path":"https://developer.x.com/en/community"}]" data-right-nav-items="[{"isActive":false,"hasActiveChild":false,"children":[{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Policies","linkDisabled":false,"title":"Policies","path":"https://developer.x.com/en/developer-terms"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Developer agreement","linkDisabled":false,"title":"Developer agreement","path":"https://developer.x.com/en/developer-terms/agreement-and-policy/source"}],"overviewTitle":"Support","linkDisabled":false,"title":"Support","path":"https://developer.x.com/en/support"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Developer Portal","linkDisabled":false,"title":"Developer Portal","path":"https://developer.twitter.com/en/portal/petition/essential/basic-info"}]" data-cta-enabled="true" data-profile-enabled="true" data-cta-link-new-tab="false" data-root-page-title="Developer Platform"> Developer terms Developer Policy Let's get started X + Developers Using this policy X + Developers Using this policy X + Developers X loves developers. We’re delighted and amazed by the tools and services this community creates by harnessing the power of X data. As part of our commitment to this community, we aim to provide data access that is open and fair for developers, safe for people on X, and beneficial for the X platform as a whole. To further these goals we’ve crafted the Developer Policy as a guide to help people understand our rules and expectations about appropriate API and X Content usage. This Developer Policy (“ Policy ”) provides rules and guidelines for developers who interact with X’s ecosystem of applications, services, website, web pages and content. It is part of your contract with X governing access to and use of the X API and X Content (either as part of the Developer Agreement or other written agreement with X). Policy violations are considered violations of your agreement. This Policy may be changed from time to time without notice. Capitalized terms used in this Policy, which are not defined in this Policy, will have the respective meanings ascribed to them in the Developer Agreement or the Master License Agreement. Using this policy We’ve structured this policy to make it as easy to follow as possible. Please keep information from the following policy sections top of mind as you use the X API and X Content: 1. Set Yourself Up for Success - You are responsible for complying with all X policies. It’s important that you review and understand this Policy, as well as the policies we link to in this document, before you access the X API and X Content. The time spent reviewing our policies may save you hours of rework down the road. 2. Privacy and Control are Essential - Protecting and defending the privacy of people on X is built into the core DNA of our company. As such, we prohibit the use of X data in any way that would be inconsistent with people’s reasonable expectations of privacy. By building on the X API or accessing X Content, you have a special role to play in safeguarding this commitment, most importantly by respecting people’s privacy and providing them with transparency and control over how their data is used. 3. Follow the Platform Usage Guidelines - Getting approved to access the X API and X Content is just the first step. Our Platform Usage Guidelines should be your first stop anytime you have questions about how to ensure policy compliance for your planned use of the X platform. We’ve provided a lot more detail on what each of these three key sections mean below. Please review them carefully to ensure that your usage of the X API and X Content is consistent with our policies. If we believe you are in violation of this Policy (or any other X policy), we may suspend or permanently revoke your access to the X API and X Content. Finally, please note that X may monitor your use of the X API to improve the X Applications, to examine any commercial use, and to ensure your compliance with your approved use case and this Policy. Thanks for reading, and thank you for building with us! We look forward to seeing what you create! Chapter 1 Set yourself up for success Set yourself up for success Set yourself up for success Set yourself up for success You can avoid many potential pitfalls while using the X API by ensuring that your service has been built the right way from day 1. This section of the Developer Policy contains rules that all developers must follow before using the X API or X Content. The Free, Basic, and Pro plans (as described at developer.x.com/en ) are designed for hobbyists, commercial prototyping, early-stage X product integrations, and supporting applications with limited end-users. If you use the X API and X Content beyond this scope, then you must apply (or already subscribe to) an Enterprise plan (as described at developer.x.com/en ). We review all proposed uses of the X developer platform to verify policy compliance — so you’re required to disclose (and update, as applicable) your planned use of the X API and X Content in order to be granted and to maintain access. All new developers must apply for a developer account to access the X API. Current developers without an approved developer account must apply for one as directed to do so by X. As part of this process, you’ll need to provide us with a written description of your intended uses of the X API and X Content. Your use case description is binding on you, and any substantive deviation from it may constitute a violation of our rules and result in enforcement action. You must notify us of any substantive modification to your use case and receive approval before you may begin using X Content for that new purpose. Failure to do so may result in suspension and termination of your API and data access. By building on the X API or accessing X Content, you must comply with ALL X policies. These include this Developer Policy , the Automation Rules , the Display Requirements , the API Restricted Uses Rules , the X Rules , and the X Brand Resources , as well as any other agreements you enter into with X relating to your use of the X API or X Content, including but not limited to the Developer Agreement or a Master Licensing Agreement or Order (as applicable). You must also comply with any modifications to these policies and any new policies launched by X. It is your responsibility to monitor the use of your service and to design your service to prevent violations of X policy by people who use it. Failure to do so may result in suspension or termination of your API and X Content access. You may not register multiple applications for a single use case or substantially similar or overlapping use cases. In this context, a “use case” is a consistent set of analyses, displays, or actions performed via an application. "White label" versions of a tool or service are not permissible. If you plan to “white label” versions of your application, you must notify and receive separate approval from us. As a single exception to these rules, you may create and use a maximum of 3 applications for development, staging, and production instances of the same service. These apps must be registered to a single account, and should be clearly identified (in the name and description) as dev, staging, and prod instances of a single service. You may not use development or staging applications for production purposes. You must keep all API keys or other access credentials private. You may not use, and may not encourage or facilitate others to use, API keys or other access credentials owned by others. Your license agreement with X limits your use of the X API and X Content. Among other things, the X API has rate limits which help to ensure fair data usage and to combat spam on the platform. You may not exceed or circumvent rate limits, or any other limitations or restrictions described in this Policy or your agreement with X, listed on the Developer Site , or communicated to you by X. You may not remove or alter any proprietary notices or marks on X Content received via the X API. This helps to make sure that people know where X Content is coming from, and who it belongs to. For data integrity and platform health reasons, you may not interfere with, intercept, disrupt, or disable any features of the X API or the X service. In other words, use the APIs as intended and documented on developer.x.com . Refer to our HackerOne guidelines for more details about acceptable use. Chapter 2 Privacy and control are essential Privacy and control are essential Consent & permissions Content compliance Off-X matching Your privacy policy Using geo-data X passwords Privacy and control are essential Consent & permissions Content compliance Off-X matching Your privacy policy Using geo-data X passwords Privacy and control are essential X takes privacy seriously, and we expect everyone using X Content and the X API to do the same. Any use of the X developer platform, X API, or X Content in a manner that is inconsistent with peoples’ reasonable expectations of privacy may be subject to enforcement action, which can include suspension and termination of API and X Content access. Your commitment to privacy and control must extend to all uses of X Content and all aspects of the service that you build using our API. To that end, the people using your service must understand and consent to how you use their data, and how you access X on their behalf. This can be accomplished through providing people with a clear, comprehensive, and transparent privacy policy, as well as ensuring that you get express and informed consent from each person using your service before taking any action on their behalf. Please note that a person authenticating into your service does not by itself constitute consent. Consent & permissions In particular, you must get express and informed consent from people before doing any of the following: Taking any actions on their behalf. This includes (but is not limited to): Posting content to X Following/unfollowing accounts Modifying profile or account information Adding hashtags or any other content to Posts Republishing content accessed by means other than via the X API or other X tools Using someone’s X Content to promote a product or service Storing non-public content such as Direct Messages (DMs), or any other private or confidential information Sharing or publishing protected content, or any other private or confidential information If your service allows people to post content to X you must do the following before publishing: Show exactly what will be published Make it clear to people using your service what geo information (if any) will be added to the content If your service allows people to post content to both your service and X, you must do the following before publishing: Obtain permission to post the content Explain where you will post the content You must respect the protected and blocked status of all X Content. You may not serve content obtained using one person’s authentication token to a different person who is not authorized to view that content. Protected accounts: A protected account ’s content is only available to people who have been approved by the owner to follow that account. So, if you run a service that accesses protected accounts, you may only do so to serve such content to the specific people with permission to view that content. Blocked accounts: People on X are able to block access to their accounts for any reason they choose. Commingling information obtained from tokens (or any other API-based action) to bypass this choice is not permitted. As Direct Messages (DMs) are non-public in nature, services that provide DM features must take extra steps to safeguard personal privacy. You may not serve DM content to people who are not authorized to view that content. If your service provides DM functionality you must also: Notify people if you send read receipt events for DMs. You can do this by providing a notice directly in your service, or by displaying read receipts from other participants in a conversation. Get consent before configuring media to be sent in a DM as "shared" (i.e. reusable across multiple DMs). If you do allow media in a DM to be “shared,” you must provide a clear notice that this content will be accessible to anyone with the media’s URL. Content compliance If you store X Content offline, you must keep it up to date with the current state of that content on X. Specifically, you must delete or modify any content you have if it is deleted or modified on X. This must be done as soon as reasonably possible, or within 24 hours after receiving a request to do so by X or the applicable X account owner, or as otherwise required by your agreement with X or applicable law. This must be done unless otherwise prohibited by law, and only then with the express written permission of X. Modified content can take various forms. This includes (but is not limited to): Content that has been made private or gained protected status Content that has been suspended from the platform Content that has had geotags removed from it Content that has been withheld or removed from X Off-X matching We limit the circumstances under which you may match a person on X to information obtained or stored off-X. Off-X matching involves associating X Content, including a X @handle or user ID, with a person, household, device, browser, or other off-X identifier. You may only do this if you have express opt-in consent from the person before making the association, or as described below. In situations in which you don’t have a person’s express, opt-in consent to link their Xidentity to an off-X identifier, we require that any connection you draw be based only on information that someone would reasonably expect to be used for that purpose. In addition, absent a person’s express opt-in consent you may only attempt to match your records about someone to a X identity based on: Information provided directly to you by the person. Note that records about individuals with whom you have no prior relationship, including data about individuals obtained from third parties, do not meet this standard; and/or Public data. “Public data” in this context refers to: Information about a person that you obtained from a public, generally-available resource (such as a directory of members of a professional association) Information on X about a person that is publicly available, including: Posts Profile information, including an account bio and publicly-stated location Display name and @handle Your privacy policy You must display your service’s privacy policy to people before they are permitted to download, install, or sign up to your service. It must disclose at least the following information: The information that you collect from people who use your service How you use and share that information (including with X) How people can contact you with inquiries and requests regarding their information Your privacy policy must be consistent with all applicable laws, and be no less protective of people than X’s Privacy Policy and the privacy policy of our other services and corporate affiliates . You must cease your access to the X API and the use of all X Content if you are unable to comply with your and/or X’s Privacy Policy. Using geo-data Use of geo data comes with additional restrictions due to the sensitive nature of this information. If your service adds location information to Posts, you must disclose to people: When you add location information Whether you add location information as a geotag or annotations data Whether your location information is listed as a place, or as geographic coordinates If your application allows people to post with their location you must comply with X’s geo guidelines in full. Any use of location data or geographic information on a standalone basis is prohibited. You may not (and may not permit others to) store, aggregate, or cache location data and other geographic information contained in X Content, except as part of a Post. For example, you may not separate location data or geographic information out from Posts to show where individuals have been over time. Heat maps and related tools that show aggregated geo activity (e.g., the number of people in a city using a hashtag) are permitted. X passwords You may not store X passwords, or request that people provide their X password, account credentials, or developer application information (including consumer key) to you directly. We suggest the use of Sign-in with X as the authentication tool to link your service and people on X. Chapter 3 Platform usage guidelines Platform usage guidelines Spam, bots, and automation X performance benchmarking Public display of Posts Content redistribution Pay to engage Service authenticy X name, logo, and likeness Advertising on X Platform usage guidelines Spam, bots, and automation X performance benchmarking Public display of Posts Content redistribution Pay to engage Service authenticy X name, logo, and likeness Advertising on X Platform usage guidelines Have you taken care to review X’s policies and set up your API access the right way? Does your service follow X’s privacy and control guidelines? If you can answer yes to these two questions, then you are ready to start using the X API and X Content. X’s Platform Usage Guidelines provide the assistance needed to ensure that your use of X Content is compliant from day 1 throughout the lifecycle of your service. We suggest reviewing these rules on a regular basis to make sure that your integration is operating in a way that is safe and beneficial to people on X and the X platform as a whole. Spam, bots, and automation The use of the X API and developer products to create spam, or engage in any form of platform manipulation, is prohibited. You should review the X Rules on platform manipulation and spam , and ensure that your service does not, and does not enable people to, violate our policies. Services that perform write actions, including posting Posts, following accounts, or sending Direct Messages, must follow the Automation Rules . In particular, you should: Always get explicit consent before sending people automated replies or Direct Messages Immediately respect requests to opt-out of being contacted by you Never perform bulk, aggressive, or spammy actions, including bulk following Never post identical or substantially similar content across multiple accounts If you’re operating an API-based bot account you must clearly indicate what the account is and who is responsible for it. You should never mislead or confuse people about whether your account is or is not a bot. A good way to do this is by including a statement that the account is a bot in the profile bio. X performance benchmarking You may not use the X API to measure the availability, performance, functionality, or usage of X for benchmarking, competitive, or commercial purposes. For example, you should never use the X API to: Calculate aggregate X metrics, such as the total number of Monthly Actives (MAs) or Daily Actives (DAs) Calculate aggregate X Post metrics, such as the total number of Posts posted per day, or the number of account engagements Measure or analyze the responsiveness of X Measure or analyze spam or security on X, except as permitted below We support research that helps improve conversational health on X. You may not publicly disclose any research or findings concerning, or develop, create, or offer services using, the X API or X Content that measure, analyze, or attempt to identify behaviors or content which violate X policies without express written permission from X. DSA Researchers: If you need to contact X relating to access under Art. 40 of the Digital Services Act, please contact EU-Questions@X.com . If you wish to apply for researcher access, please submit an application . Public display of Posts You must maintain the integrity of all X Content that you display publicly or to people who use your service. If you don’t use X for Websites to display content, then you must use the X API to retrieve the most current version available for display. If displayed content ceases to be available through the X API, then you must remove it from your service as soon as reasonably possible, or within 24 hours after the receipt of a removal request from X, or the applicable X account owner, or as otherwise required by applicable law. There are specific rules you must follow if you display X Content offline. Follow the guidelines for using Posts in broadcast if you display Posts offline. If you embed or display Posts, you must contact us about your X API access if your site exceeds 10 million daily impressions. X reserves the right to require additional terms as a condition to your use of the X API. Additional restrictions on X for Websites developer use include: Embedded Posts and/or embedded timelines You must provide people with legally sufficient notice that fully discloses X’s collection and use of data about browsing activities on your website, including for interest-based advertising and personalization. You must also obtain legally sufficient consent from people for such collection and use You must provide legally sufficient instructions on how people can opt out of X’s interest-based advertising and personalization as described here X for Websites widgets You must ensure that people are provided with clear and comprehensive information about, and consent to, the storing and accessing of cookies or other information on their devices as described in X’s cookie use , where providing such information and obtaining such consent is required by law Services targeted to children under 13 Services targeted to children under 13 must opt out of tailoring X in any embedded Post and/or embedded timelines by setting the opt-out parameter to be ‘true’ as described here Content redistribution The best place to get X Content is directly from X. Consequently, we restrict the redistribution of X Content to third parties. If you provide X Content to third parties, including downloadable datasets or via an API, you may only distribute Post IDs, Direct Message IDs, and/or User IDs (except as described below). In total, you may not distribute more than 1,500,000 Post IDs to any entity (inclusive of multiple individuals associated with a single entity) within any 30 day period unless you have received written permission from X. In addition, developers may provide up to 500 public Posts Objects and/or User Objects to each person who uses your service on a daily basis if this is done via non-automated means (e.g., download of spreadsheets or PDFs). Academic researchers are permitted to distribute Post IDs and/or User IDs solely for the purposes of non-commercial research on behalf of an academic institution, and that has been approved by X in writing, or peer review or validation of such research. Only as many Post IDs or User IDs that is necessary for such research, and has been approved by X may be used. Any X Content provided to third parties remains subject to this Policy, and those third parties must agree to the X Terms of Service , Privacy Policy , Developer Agreement , and Developer Policy before receiving such downloads. You may not enable any entity to circumvent any other limitations or restrictions on the distribution of X Content as contained in this Policy , the Developer Agreement , or any other agreement with X. Note: This Section does not apply to researchers with X API access via Art. 40 of the EU Digital Services Act (2022) (“ DSA ”), who are instead subject to the procedures and restrictions set forth in the DSA and the Developer Agreement. Pay to engage Your service shouldn’t compensate people to take actions on X, as that results in inauthentic engagement that degrades the health of the platform. As you use the X API you may not sell or receive monetary or virtual compensation for any X actions. This includes, but is not limited to, Posts, follows, unfollows, reposts, likes, comments, and replies. Service authenticity You must clearly identify your service so that people can understand its source and purpose. Don’t use names, logos, or URLs that mask your service’s identity and features, or that falsely imply an affiliation with X or third parties. Note that creating applications for the purpose of selling names, or to prevent others from using names, is prohibited. You may not use any URL (including shortened URLs) for your service that directs people to: A site that is unrelated to your service A spam or malware site A site that encourages people to violate X policy X name, logo, and likeness You may only use and display the X name and logo to identify X as the source of X Content. You should never use the X name and logo, the X Official Partner Program badge, or any other similar marks or names in a manner that creates a false sense of endorsement, sponsorship, or association with X. The X Brand Resources contain detailed information to help you use the X brand in the right way. You may only use the X Verified Account badge and any other enhanced account categorization as it is reported to you by X through the API. This helps people know that the content your service displays is equivalent to that shown on X. Advertising on X There are restrictions regarding how and where you are allowed to advertise around X Content. To start, your advertisements can’t resemble or reasonably be confused by people as a Post. Other rules on advertising include: There must be a clear separation between X Content and your advertisements. You may not place any advertisements within the X timeline other than X Ads. X reserves the right to serve advertising via the X API. If you decide to serve X Ads once we start delivering them via the API, we will share a portion of advertising revenue with you in accordance with the relevant terms and conditions. You may not use X Content, or information obtained from the X API to target people with advertising outside of the X platform. Chapter 4 Rules for specific X services or features X login X Cards Definitions X login X Cards Definitions The following additional rules apply for any use of the X services or features listed below: X login You must present people with easy to find options to log into and out of X, for example via the OAuth protocol. The Sign in with X option must be displayed at least as prominently as any other sign-up or sign-in feature on your service. You must also provide people without a X account the opportunity to create one via X. Once someone on your service authenticates via Sign in with X you must clearly display their X identity. X identity includes the person’s current X @handle, avatar, and X logo. Any display of someone’s X followers on your service must clearly show that the relationship is associated with X. X Cards To ensure a quality experience you must develop your Card to render across all platforms where Cards are displayed. Additional rules that you must follow when using Cards include: You must mark your Post as ‘true’ for sensitive media if you plan to display such media within a Card You must use HTTPS for hosting all assets within your Card. Your Card should never generate active mixed content browser warnings Audio and video content should include stop or pause controls, and default to ‘sound off’ for videos that automatically play content You may not exceed or circumvent X’s limitations placed on any Cards, including the Card’s intended use. Additional restrictions on Cards use include: You may not place third-party sponsored content within Cards without X’s approval You may not attach monetary incentives (including virtual currency) within your Card or on X from your Card You may not include content or actions within your Card that are misleading or not contextually relevant, such as URLs and media You may only attach an App Card to a Post when someone is explicitly promoting or referring to the app in the Post Definitions X Content ‒ Posts, Post IDs, X end user profile information, and any other data and information made available to you through the X API or by any other means authorized by X, and any copies and derivative works thereof. Developer Site ‒ X’s developer site located at https://developer.x.com . Services ‒ Your websites, applications and other offerings that display X Content or otherwise use the Licensed Material as explicitly approved by X. Post ID ‒ A unique identification number generated for each Post. Post ‒ A posting made on X Applications. “X” ‒ Means (a) X Corp. (865 FM 1209, Building 2, Bastrop, TX 78602, USA) if your principal place of business is outside the European Union, EFTA States, and the United Kingdom; or (b) X Internet Unlimited Company (One Cumberland Place, Fenian Street, Dublin 2, D02 AX07, Ireland) if your principal place of business is in the European Union, EFTA States, or the United Kingdom. Direct Message - A message that is privately sent on X Applications by one end user to one or more specific end user(s) using X’s Direct Message function. X API ‒ The X Application Programming Interface (“API”), Software Development Kit (“SDK”) and/or the related documentation, data, code, and other materials provided by X with the API, as updated from time to time, including without limitation through the Developer Site. X Applications ‒ X’s consumer facing products, services, applications, websites, web pages, platforms, and other offerings, including without limitation, those offered via https://x.com and X's mobile applications. Developer policy and terms Follow @XDevelopers Subscribe to developer news X platform X.com Status Accessibility Embed a post Privacy Center Transparency Center Download the X app Try Grok.com X Corp. About the company Company news Brand toolkit Jobs and internships Investors Help Help Center Using X X for creators Ads Help Center Managing your account Email Preference Center Rules and policies Contact us Developer resources Developer home Documentation Forums Communities Developer blog Engineering blog Developer terms Business resources Advertise X for business Resources and guides X for marketers Marketing insights Brand inspiration X Ads Academy © 2026 X Corp. Cookies Privacy Terms and conditions Did someone say … cookies? X and its partners use cookies to provide you with a better, safer and faster service and to support our business. Some cookies are necessary to use our services, improve our services, and make sure they work properly. Show more about your choices . Accept all cookies Refuse non-essential cookies | 2026-01-13T08:48:28 |
https://www.linkedin.com/legal/user-agreement?trk=linkedin-tc_auth-button_user-agreement | User Agreement | LinkedIn Skip to main content User Agreement Summary of User Agreement Privacy Policy Professional Community Policies Cookie Policy Copyright Policy Regional Info EU Notice California Privacy Disclosure U.S. State Privacy Laws User Agreement Summary of User Agreement Privacy Policy Professional Community Policies Cookie Policy Copyright Policy Regional Info EU Notice California Privacy Disclosure U.S. State Privacy Laws User Agreement Effective on November 3, 2025 Our mission is to connect the world’s professionals to allow them to be more productive and successful. Our services are designed to promote economic opportunity for our members by enabling you and millions of other professionals to meet, exchange ideas, learn, and find opportunities or employees, work, and make decisions in a network of trusted relationships. Table of Contents: Introduction Obligations Rights and Limits Disclaimer and Limit of Liability Termination Governing Law and Dispute Resolution General Terms LinkedIn “Dos and Don’ts” Complaints Regarding Content How To Contact Us Introduction 1.1 Contract When you use our Services you agree to all of these terms. Your use of our Services is also subject to our Cookie Policy and our Privacy Policy, which covers how we collect, use, share, and store your personal information. By creating a LinkedIn account or accessing or using our Services (described below), you are agreeing to enter into a legally binding contract with LinkedIn (even if you are using third party credentials or using our Services on behalf of a company). If you do not agree to this contract (“Contract” or “User Agreement”), do not create an account or access or otherwise use any of our Services. If you wish to terminate this Contract at any time, you can do so by closing your account and no longer accessing or using our Services. As a Visitor or Member of our Services, the collection, use, and sharing of your personal data is subject to our Privacy Policy , our Cookie Policy and other documents referenced in our Privacy Policy , and updates. You acknowledge and have read our Privacy Policy . Services This Contract applies to LinkedIn.com, LinkedIn-branded apps, and other LinkedIn-related sites, apps, communications, and other services that state that they are offered under this Contract (“Services”), including the offsite collection of data for those Services, such as via our ads and the “Apply with LinkedIn” and “Share with LinkedIn” plugins. LinkedIn and other Key Terms You are entering into this Contract with LinkedIn (also referred to as “we” and “us”). Designated Countries . We use the term “Designated Countries” to refer to countries in the European Union (EU), European Economic Area (EEA), and Switzerland. If you reside in the “Designated Countries”, you are entering into this Contract with LinkedIn Ireland Unlimited Company (“LinkedIn Ireland”) and LinkedIn Ireland will be the controller of your personal data provided to, or collected by or for, or processed in connection with our Services. If you reside outside of the “Designated Countries”, you are entering into this Contract with LinkedIn Corporation (“LinkedIn Corp.”) and LinkedIn Corp. will be the controller of (or business responsible for) your personal data provided to, or collected by or for, or processed in connection with our Services. Affiliates . Affiliates are companies controlling, controlled by or under common control with us, including, for example, LinkedIn Ireland, LinkedIn Corporation, LinkedIn Singapore and Microsoft Corporation or any of its subsidiaries (e.g., Github, Inc.). Social Action . Actions that members take on our services such as likes, comments, follows, sharing content. Content . Content includes, for example, feed posts, feedback, comments, profiles, articles (and contributions), group posts, job postings, messages (including InMails), videos, photos, audio, and/or PDFs. 1.2 Members and Visitors This Contract applies to Members and Visitors. When you register and join the LinkedIn Services, you become a “Member”. If you have chosen not to register for our Services, you may access certain features as a “Visitor.” 1.3 Changes We may make changes to this Contract. We may modify this Contract, our Privacy Policy and our Cookie Policy from time to time. If we materially change these terms or if we are legally required to provide notice, we will provide you notice through our Services, or by other means, to provide you the opportunity to review the changes before they become effective. However, we may not always provide prior notice of changes to these terms (1) when those changes are legally required to be implemented with immediate effect, or (2) when those changes relate to a newly launched service or feature. We agree that changes cannot be retroactive. If you object to any of these changes, you may close your account . Your continued use of our Services after we publish or send a notice about our changes to these terms means that you are consenting to the updated terms as of their effective date. 2. Obligations 2.1 Service Eligibility Here are some promises that you make to us in this Contract: You’re eligible to enter into this Contract and you are at least our “Minimum Age.” The Services are not for use by anyone under the age of 16. To use the Services, you agree that: (1) you must be the "Minimum Age" (described below) or older; (2) you will only have one LinkedIn account, which must be in your real name; and (3) you are not already restricted by LinkedIn from using the Services. Creating an account with false information is a violation of our terms, including accounts registered on behalf of others or persons under the age of 16. “Minimum Age” means 16 years old. However, if law requires that you must be older in order for LinkedIn to lawfully provide the Services to you without parental consent (including using your personal data) then the Minimum Age is such older age. Learn More 2.2 Your Account You will keep your password a secret You will not share your account with anyone else and will follow our policies and the law. Members are account holders. You agree to: (1) protect against wrongful access to your account (e.g., use a strong password and keep it confidential); (2) not share or transfer your account or any part of it (e.g., sell or transfer the personal data of others by transferring your connections); and (3) follow the law, our list of Dos and Don’ts (below), and our Professional Community Policies . Learn More You are responsible for anything that happens through your account unless you close it or report misuse. As between you and others (including your employer), your account belongs to you. However, if the Services were purchased by another party for you to use in connection with your work for them (e.g., Recruiter seat or LinkedIn Learning subscription bought by your employer), the party paying for such Service has the right to control access to and get reports on your use of such paid Service; however, they do not have rights to your personal account. 2.3 Payment You’ll honor your payment obligations and you are okay with us storing your payment information. You understand that there may be fees and taxes that are added to our prices. Refunds are subject to our policy, and we may modify our prices and those modified prices will apply prospectively. If you buy any of our paid Services, you agree to pay us the applicable fees and taxes and you agree to the additional terms specific to the paid Services. Failure to pay these fees will result in the termination of your paid Services. Also, you agree that: Your purchase may be subject to foreign exchange fees or differences in prices based on location (e.g., exchange rates). We may store and continue billing your payment method (e.g., credit card), even after it has expired, to avoid interruptions in your paid Services and to use it to pay for other Services you may buy. If your primary payment method fails, we may automatically charge a secondary payment method, if you have provided one. You may update or change your payment method. Learn more If you purchase a subscription, your payment method automatically will be charged at the start of each subscription period for the fees and taxes applicable to that period. To avoid future charges, cancel before the renewal date. Learn how to cancel or suspend your paid subscription Services. We may modify our prices effective prospectively upon reasonable notice to the extent allowed under the law. All of your paid Services are subject to LinkedIn’s refund policy . We may calculate taxes payable by you based on the billing information that you provide us. You can get a copy of your invoice through your LinkedIn account settings under “ Purchase History ”. 2.4 Notices and Messages You’re okay with us providing notices and messages to you through our websites, apps, and contact information. If your contact information is out of date, you may miss out on important notices. You agree that we will provide notices and messages to you in the following ways: (1) within the Services or (2) sent to the contact information you provided us (e.g., email, mobile number, physical address). You agree to keep your contact information up to date. Please review your settings to control and limit the types of messages you receive from us. 2.5 Sharing When you share information on our Services, others can see, copy and use that information. Our Services allow sharing of information (including content) in many ways, such as through your profile, posts, articles, group posts, links to news articles, job postings, messages, and InMails. Depending on the feature and choices you make, information that you share may be seen by other Members, Visitors, or others (on or off of the Services). Where we have made settings available, we will honor the choices you make about who can see content or other information (e.g., message content to your addressees, sharing content only to LinkedIn connections, restricting your profile visibility from search tools, or opting not to notify others of your LinkedIn profile update). For job searching activities, we default to not notifying your connections or the public. So, if you apply for a job through our Services or opt to signal that you are interested in a job, our default is to share it only with the job poster. To the extent that laws allow this, we are not obligated to publish any content or other information on our Services and can remove it with or without notice. 3. Rights and Limits 3.1. Your License to LinkedIn You own all of your original content that you provide to us, but you also grant us a non-exclusive license to it. We’ll honor the choices you make about who gets to see your content, including how it can be used for ads. As between you and LinkedIn, you own your original content that you submit or post to the Services. You grant LinkedIn and our Affiliates the following non-exclusive license to the content and other information you provide (e.g., share, post, upload, and/or otherwise submit) to our Services: A worldwide, transferable and sublicensable right to use, copy, modify, distribute, publicly perform and display, host, and process your content and other information without any further consent, notice and/or compensation to you or others. These rights are limited in the following ways: You can end this license for specific content by deleting such content from the Services, or generally by closing your account, except (a) to the extent you (1) shared it with others as part of the Services and they copied, re-shared it or stored it, (2) we had already sublicensed others prior to your content removal or closing of your account, or (3) we are required by law to retain or share it with others, and (b) for the reasonable time it takes to remove the content you delete from backup and other systems. We will not include your content in advertisements for the products and services of third parties to others without your separate consent (including sponsored content). However, without compensation to you or others, ads may be served near your content and other information, and your social actions may be visible and included with ads, as noted in the Privacy Policy. If you use a Service feature, we may mention that with your name or photo to promote that feature within our Services, subject to your settings. We will honor the audience choices for shared content (e.g., “Connections only”). For example, if you choose to share your post to "Anyone on or off LinkedIn” (or similar): (a) we may make it available off LinkedIn; (b) we may enable others to publicly share onto third-party services (e.g., a Member embedding your post on a third party service); and/or (c) we may enable search tools to make that public content findable though their services. Learn More While we may edit and make format changes to your content (such as translating or transcribing it, modifying the size, layout or file type, and removing or adding labels or metadata), we will take steps to avoid materially modifying the meaning of your expression in content you share with others. Because you own your original content and we only have non-exclusive rights to it, you may choose to make it available to others, including under the terms of a Creative Commons license . You and LinkedIn agree that if content includes personal data, it is subject to our Privacy Policy. You and LinkedIn agree that we may access, store, process, and use any information (including content and/or personal data) that you provide in accordance with the terms of the Privacy Policy and your choices (including settings). By submitting suggestions or other feedback regarding our Services to LinkedIn, you agree that LinkedIn can use and share (but does not have to) such feedback for any purpose without compensation to you. You promise to only provide content and other information that you have the right to share and that your LinkedIn profile will be truthful. You agree to only provide content and other information that does not violate the law or anyone’s rights (including intellectual property rights). You have choices about how much information to provide on your profile but also agree that the profile information you provide will be truthful. LinkedIn may be required by law to remove certain content and other information in certain countries. 3.2 Service Availability We may change or limit the availability of some features, or end any Service. We may change, suspend or discontinue any of our Services. We may also limit the availability of features, content and other information so that they are not available to all Visitors or Members (e.g., by country or by subscription access). We don’t promise to store or show (or keep showing) any information (including content) that you’ve shared. LinkedIn is not a storage service. You agree that we have no obligation to store, maintain or provide you a copy of any content or other information that you or others provide, except to the extent required by applicable law and as noted in our Privacy Policy. 3.3 Other Content, Sites and Apps Your use of others’ content and information posted on our Services, is at your own risk. Others may offer their own products and services through our Services, and we aren’t responsible for those third-party activities. Others’ Content: By using the Services, you may encounter content or other information that might be inaccurate, incomplete, delayed, misleading, illegal, offensive, or otherwise harmful. You agree that we are not responsible for content or other information made available through or within the Services by others, including Members. While we apply automated tools to review much of the content and other information presented in the Services, we cannot always prevent misuse of our Services, and you agree that we are not responsible for any such misuse. You also acknowledge the risk that others may share inaccurate or misleading information about you or your organization, and that you or your organization may be mistakenly associated with content about others, for example, when we let connections and followers know you or your organization were mentioned in the news. Members have choices about this feature . Others’ Products and Services: LinkedIn may help connect you to other Members (e.g., Members using Services Marketplace or our enterprise recruiting, jobs, sales, or marketing products) who offer you opportunities (on behalf of themselves, their organizations, or others) such as offers to become a candidate for employment or other work or offers to purchase products or services. You acknowledge that LinkedIn does not perform these offered services, employ those who perform these services, or provide these offered products. You further acknowledge that LinkedIn does not supervise, direct, control, or monitor Members in the making of these offers, or in their providing you with work, delivering products or performing services, and you agree that (1) LinkedIn is not responsible for these offers, or performance or procurement of them, (2) LinkedIn does not endorse any particular Member’s offers, and (3) LinkedIn is not an agent or employment agency on behalf of any Member offering employment or other work, products or services. With respect to employment or other work, LinkedIn does not make employment or hiring decisions on behalf of Members offering opportunities and does not have such authority from Members or organizations using our products. For Services Marketplace , (a) you must be at least 18 years of age to procure, offer, or perform services, and (b) you represent and warrant that you have all the required licenses and will provide services consistent with the relevant industry standards and our Professional Community Policies . Others’ Events: Similarly, LinkedIn may help you register for and/or attend events organized by Members and connect with other Members who are attendees at such events. You agree that (1) LinkedIn is not responsible for the conduct of any of the Members or other attendees at such events, (2) LinkedIn does not endorse any particular event listed on our Services, (3) LinkedIn does not review and/or vet any of these events or speakers, and (4) you will adhere to the terms and conditions that apply to such events. 3.4 Limits We have the right to limit how you connect and interact on our Services. LinkedIn reserves the right to limit your use of the Services, including the number of your connections and your ability to contact other Members. LinkedIn reserves the right to restrict, suspend, or terminate your account if you breach this Contract or the law or are misusing the Services (e.g., violating any of the Dos and Don’ts or Professional Community Policies ). We can also remove any content or other information you shared if we believe it violates our Professional Community Policies or Dos and Don’ts or otherwise violates this Contract. Learn more about how we moderate content. 3.5 Intellectual Property Rights We’re providing you notice about our intellectual property rights. LinkedIn reserves all of its intellectual property rights in the Services. Trademarks and logos used in connection with the Services are the trademarks of their respective owners. LinkedIn, and “in” logos and other LinkedIn trademarks, service marks, graphics and logos used for our Services are trademarks or registered trademarks of LinkedIn. 3.6 Recommendations and Automated Processing We use data and other information about you to make and order relevant suggestions and to generate content for you and others. Recommendations: We use the data and other information that you provide and that we have about Members and content on the Services to make recommendations for connections, content, ads, and features that may be useful to you. We use that data and other information to recommend and to present information to you in an order that may be more relevant for you. For example, that data and information may be used to recommend jobs to you and you to recruiters and to organize content in your feed in order to optimize your experience and use of the Services. Keeping your profile accurate and up to date helps us to make these recommendations more accurate and relevant. Learn More Generative AI Features: By using the Services, you may interact with features we offer that automate content generation for you. The content that is generated might be inaccurate, incomplete, delayed, misleading or not suitable for your purposes. Please review and edit such content before sharing with others. Like all content you share on our Services, you are responsible for ensuring it complies with our Professional Community Policies , including not sharing misleading information. The Services may include content automatically generated and shared using tools offered by LinkedIn or others off LinkedIn. Like all content and other information on our Services, regardless of whether it's labeled as created by “AI”, be sure to carefully review before relying on it. 4. Disclaimer and Limit of Liability 4.1 No Warranty This is our disclaimer of legal liability for the quality, safety, or reliability of our Services. LINKEDIN AND ITS AFFILIATES MAKE NO REPRESENTATION OR WARRANTY ABOUT THE SERVICES, INCLUDING ANY REPRESENTATION THAT THE SERVICES WILL BE UNINTERRUPTED OR ERROR-FREE, AND PROVIDE THE SERVICES (INCLUDING CONTENT, OUTPUT AND INFORMATION) ON AN “AS IS” AND “AS AVAILABLE” BASIS. TO THE FULLEST EXTENT PERMITTED UNDER APPLICABLE LAW, LINKEDIN AND ITS AFFILIATES DISCLAIM ANY IMPLIED OR STATUTORY WARRANTY, INCLUDING ANY IMPLIED WARRANTY OF TITLE, ACCURACY, NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. If you plan to use content, output and information for any reason, it is your responsibility to verify its accuracy and fitness for your purposes, because any content, output and information on the service may not reflect accurate, complete, or current information. 4.2 Exclusion of Liability These are the limits of legal liability we may have to you. TO THE FULLEST EXTENT PERMITTED BY LAW (AND UNLESS LINKEDIN HAS ENTERED INTO A SEPARATE WRITTEN AGREEMENT THAT OVERRIDES THIS CONTRACT), LINKEDIN AND ITS AFFILIATES, WILL NOT BE LIABLE IN CONNECTION WITH THIS CONTRACT FOR LOST PROFITS OR LOST BUSINESS OPPORTUNITIES, REPUTATION (E.G., OFFENSIVE OR DEFAMATORY STATEMENTS), LOSS OF DATA (E.G., DOWN TIME OR LOSS, USE OF, OR CHANGES TO, YOUR INFORMATION OR CONTENT) OR ANY INDIRECT, INCIDENTAL, CONSEQUENTIAL, SPECIAL OR PUNITIVE DAMAGES. LINKEDIN AND ITS AFFILIATES WILL NOT BE LIABLE TO YOU IN CONNECTION WITH THIS CONTRACT FOR ANY AMOUNT THAT EXCEEDS (A) THE TOTAL FEES PAID OR PAYABLE BY YOU TO LINKEDIN FOR THE SERVICES DURING THE TERM OF THIS CONTRACT, IF ANY, OR (B) US $1000. 4.3 Basis of the Bargain; Exclusions The limitations of liability in this Section 4 are part of the basis of the bargain between you and LinkedIn and shall apply to all claims of liability (e.g., warranty, tort, negligence, contract and law) even if LinkedIn or its affiliates has been told of the possibility of any such damage, and even if these remedies fail their essential purpose. THESE LIMITATIONS OF LIABILITY DO NOT APPLY TO LIABILITY FOR DEATH OR PERSONAL INJURY OR FOR FRAUD, GROSS NEGLIGENCE OR INTENTIONAL MISCONDUCT, OR IN CASES OF NEGLIGENCE, WHERE A MATERIAL OBLIGATION HAS BEEN BREACHED. A MATERIAL OBLIGATION BEING AN OBLIGATION WHICH FORMS A PREREQUISITE TO OUR DELIVERY OF SERVICES AND ON WHICH YOU MAY REASONABLY RELY, BUT ONLY TO THE EXTENT THAT THE DAMAGES WERE DIRECTLY CAUSED BY THE BREACH AND WERE FORESEEABLE UPON CONCLUSION OF THIS CONTRACT AND TO THE EXTENT THAT THEY ARE TYPICAL IN THE CONTEXT OF THIS CONTRACT. 5. Termination We can each end this Contract, but some rights and obligations survive. Both you and LinkedIn may terminate this Contract at any time with notice to the other. On termination, you lose the right to access or use the Services. The following shall survive termination: Our rights to use and disclose your feedback; Section 3 (subject to 3.1.1); Sections 4, 6, 7, and 8.2 of this Contract; and Any amounts owed by either party prior to termination remain owed after termination. You can visit our Help Center to learn about how to close your account 6. Governing Law and Dispute Resolution In the unlikely event we end up in a legal dispute, depending on where you live, you and LinkedIn agree to resolve it in California courts using California law, Dublin, Ireland courts using Irish law, or as otherwise provided in this section. If you live in the Designated Countries, the laws of Ireland govern all claims related to LinkedIn's provision of the Services, but this shall not deprive you of the mandatory consumer protections under the law of the country to which we direct your Services where you have habitual residence. With respect to jurisdiction, you and LinkedIn agree to choose the courts of the country to which we direct your Services where you have habitual residence for all disputes arising out of or relating to this User Agreement, or in the alternative, you may choose the responsible court in Ireland. If you are a business user within the scope of Article 6(12) of the EU Digital Markets Act (“DMA”) and have a dispute arising out of or in connection with Article 6(12) of the DMA, you may also utilize the alternative dispute resolution mechanism available in the Help Center . For others outside of Designated Countries, including those who live outside of the United States: You and LinkedIn agree that the laws of the State of California, U.S.A., excluding its conflict of laws rules, shall exclusively govern any dispute relating to this Contract and/or the Services. You and LinkedIn both agree that all claims and disputes can be litigated only in the federal or state courts in Santa Clara County, California, USA, and you and LinkedIn each agree to personal jurisdiction in those courts. You may have additional rights of redress and appeal for some decisions made by LinkedIn that impact you. 7. General Terms Here are some important details about the Contract. If a court with authority over this Contract finds any part of it unenforceable, you and we agree that the court should modify the terms to make that part enforceable while still achieving its intent. If the court cannot do that, you and we agree to ask the court to remove that unenforceable part and still enforce the rest of this Contract. This Contract (including additional terms that may be provided by us when you engage with a feature of the Services) is the only agreement between us regarding the Services and supersedes all prior agreements for the Services. If we don't act to enforce a breach of this Contract, that does not mean that LinkedIn has waived its right to enforce this Contract. You may not assign or transfer this Contract (or your membership or use of Services) to anyone without our consent. However, you agree that LinkedIn may assign this Contract to its affiliates or a party that buys it without your consent. There are no third-party beneficiaries to this Contract. You agree that the only way to provide us legal notice is at the addresses provided in Section 10. 8. LinkedIn “Dos and Don’ts” LinkedIn is a community of professionals. This list of “Dos and Don’ts” along with our Professional Community Policies limits what you can and cannot do on our Services, unless otherwise explicitly permitted by LinkedIn in a separate writing (e.g., through a research agreement). 8.1. Dos You agree that you will: Comply with all applicable laws, including, without limitation, privacy laws, intellectual property laws, anti-spam laws, export control laws, laws governing the content shared, and other applicable laws and regulatory requirements; Provide accurate contact and identity information to us and keep it updated; Use your real name on your profile; and Use the Services in a professional manner. 8.2. Don’ts You agree that you will not : Create a false identity on LinkedIn, misrepresent your identity, create a Member profile for anyone other than yourself (a real person), or use or attempt to use another’s account (such as sharing log-in credentials or copying cookies); Develop, support or use software, devices, scripts, robots or any other means or processes (such as crawlers, browser plugins and add-ons or any other technology) to scrape or copy the Services, including profiles and other data from the Services; Override any security feature or bypass or circumvent any access controls or use limits of the Services (such as search results, profiles, or videos); Copy, use, display or distribute any information (including content) obtained from the Services, whether directly or through third parties (such as search tools or data aggregators or brokers), without the consent of the content owner (such as LinkedIn for content it owns); Disclose information that you do not have the consent to disclose (such as confidential information of others (including your employer); Violate the intellectual property rights of others, including copyrights, patents, trademarks, trade secrets or other proprietary rights. For example, do not copy or distribute (except through the available sharing functionality) the posts or other content of others without their permission, which they may give by posting under a Creative Commons license; Violate the intellectual property or other rights of LinkedIn, including, without limitation, (i) copying or distributing our learning videos or other materials, (ii) copying or distributing our technology, unless it is released under open source licenses; or (iii) using the word “LinkedIn” or our logos in any business name, email, or URL except as provided in the Brand Guidelines ; Post (or otherwise share) anything that contains software viruses, worms, or any other harmful code; Reverse engineer, decompile, disassemble, decipher or otherwise attempt to derive the source code for the Services or any related technology that is not open source; Imply or state that you are affiliated with or endorsed by LinkedIn without our express consent (e.g., representing yourself as an accredited LinkedIn trainer); Rent, lease, loan, trade, sell/re-sell or otherwise monetize the Services or related data or access to the same, without LinkedIn’s consent; Deep-link to our Services for any purpose other than to promote your profile or a Group on our Services, without LinkedIn’s consent; Use bots or other unauthorized automated methods to access the Services, add or download contacts, send or redirect messages, create, comment on, like, share, or re-share posts, or otherwise drive inauthentic engagement; Engage in “framing”, “mirroring”, or otherwise simulating the appearance or function of the Services; Overlay or otherwise modify the Services or their appearance (such as by inserting elements into the Services or removing, covering, or obscuring an advertisement included on the Services); Interfere with the operation of, or place an unreasonable load on, the Services (e.g., spam, denial of service attack, viruses, manipulating algorithms); Violate the Professional Community Policies , certain third party terms where applicable, or any additional terms concerning a specific Service that are provided when you sign up for or start using such Service; Use our Services to do anything that is unlawful, misleading, discriminatory, fraudulent or deceitful (e.g. manipulated media that wrongfully depicts a person saying or doing something they did not say or do); and/or Misuse our reporting or appeals process, including by submitting duplicative, fraudulent or unfounded reports, complaints or appeals. 9. Complaints Regarding Content Contact information for complaints about content provided by our Members. We ask that you report content and other information that you believe violates your rights (including intellectual property rights), our Professional Community Policies or otherwise violates this Contract or the law. To the extent we can under law, we may remove or restrict access to content, features, services, or information, including if we believe that it’s reasonably necessary to avoid harm to LinkedIn or others, violates the law or is reasonably necessary to prevent misuse of our Services. We reserve the right to take action against serious violations of this Contract, including by implementing account restrictions for significant violations. We respect the intellectual property rights of others. We require that information shared by Members be accurate and not in violation of the intellectual property rights or other rights of third parties. We provide a policy and process for complaints concerning content shared, and/or trademarks used, by our Members. 10. How To Contact Us Our Contact information. Our Help Center also provides information about our Services. For general inquiries, you may contact us online . For legal notices or service of process, you may write us at these addresses . LinkedIn © 2026 About Accessibility User Agreement Privacy Policy Cookie Policy Copyright Policy Brand Policy Guest Controls Community Guidelines العربية (Arabic) বাংলা (Bangla) Čeština (Czech) Dansk (Danish) Deutsch (German) Ελληνικά (Greek) English (English) Español (Spanish) فارسی (Persian) Suomi (Finnish) Français (French) हिंदी (Hindi) Magyar (Hungarian) Bahasa Indonesia (Indonesian) Italiano (Italian) עברית (Hebrew) 日本語 (Japanese) 한국어 (Korean) मराठी (Marathi) Bahasa Malaysia (Malay) Nederlands (Dutch) Norsk (Norwegian) ਪੰਜਾਬੀ (Punjabi) Polski (Polish) Português (Portuguese) Română (Romanian) Русский (Russian) Svenska (Swedish) తెలుగు (Telugu) ภาษาไทย (Thai) Tagalog (Tagalog) Türkçe (Turkish) Українська (Ukrainian) Tiếng Việt (Vietnamese) 简体中文 (Chinese (Simplified)) 正體中文 (Chinese (Traditional)) Language | 2026-01-13T08:48:28 |
https://stackoverflow.blog/releases/internal/ | Stack Overflow Internal - Stack Overflow Blog Loading… Everything Productivity AI/ML Open Source Business Hub Company Releases Podcast Newsletter Stack Overflow Business Stack Internal : the knowledge intelligence layer that powers enterprise AI. Stack Data Licensing : decades of verified, technical knowledge to boost AI performance and trust. Stack Ads : engage developers where it matters — in their daily workflow. Stack Overflow Internal December 16, 2025 Your 2025 Stacked: A year of knowledge, community, and impact From tough questions to standout answers, your team built a lot in 2025. Your 2025 Stacked brings those contributions together in one shareable snapshot—celebrating the people, posts, and topics that defined your year in Stack Internal. Carrie Koos 0 comment s November 12, 2025 2025.8 release introduces Stack Overflow Internal: The next generation of enterprise knowledge intelligence Today, we’re excited to introduce Stack Overflow Internal—the next evolution of our enterprise platform and the future of Stack Overflow for Teams. Carrie Koos 1 comment September 30, 2025 Turning investments into impact: Stack Overflow for Teams 2025.7 Over the past few releases, we’ve been investing in the foundation of Stack Overflow for Teams—strengthening infrastructure, modernizing integrations, and preparing for bigger shifts to come. Carrie Koos 1 comment August 19, 2025 Strengthening the core: Stack Overflow for Teams 2025.6 Our August release, Stack Overflow for Teams 2025.6, focuses on critical back-end improvements that enhance stability, data integrity, and identity management. Carrie Koos 0 comment s July 8, 2025 Better performance, smarter workflows: What’s new in Stack Overflow for Teams Our July 2025 release focuses on stability, integration, and actionable insight—designed to help your teams stay informed, secure, and efficient as they scale. Carrie Koos 0 comment s June 18, 2025 Smarter teams, brighter insights: Stack Overflow for Teams Business summer bundle Read on to see the latest features coming to Stack Overflow for Teams Business users! Carrie Koos 0 comment s May 27, 2025 Strengthening integrations, reliability, and trust: New features for Stack Overflow for Teams The 2025.4 Stack Overflow for Teams Enterprise (SOE) release is all about helping teams work more seamlessly across tools, departments, and knowledge silos. Carrie Koos 0 comment s April 15, 2025 Smarter insights, stronger teams: New features for Stack Overflow for Teams 2025.3 | Teams Enterprise Release Carrie Koos 0 comment s March 4, 2025 Boosting collaboration and control: New features for Stack Overflow for Teams Our latest Enterprise release brings exciting new features designed to enhance collaboration, streamline user management, and expand API capabilities. Carrie Koos 2 comment s January 29, 2025 New year, new features: Level up your Stack Overflow for Teams in 2025 The first release of the year is packed with features to make your knowledge-sharing community better. 3 comment s December 10, 2024 Enterprise 2024.8 release: Maintain a healthy roster of SMEs This release introduces the ability to automatically and programmatically demote an inactive Subject Matter Expert (SME) to ensure a healthy roster of contributing experts. Carrie Koos 0 comment s October 23, 2024 Enterprise 2024.7: Empower your subject matter experts to contribute This release introduces Subject Matter Expert (SME) Auto-Assign to the Stack Overflow for Teams experience so expert knowledge is automatically captured, verified, and distributed to users. Carrie Koos , Natalie Rotnov 1 comment September 19, 2024 Elevating your search experience: Stack Overflow for Teams ML-powered reranking experiment Today, we're excited to share details about our latest experiment that aims to make your search results in Stack Overflow for Teams Enterprise even more relevant and useful. Adrian Brunetto 1 comment September 11, 2024 Enterprise 2024.6: Identify and engage your subject matter experts This release includes updates that improve subject matter expert (SME) visibility and engagement in Stack Overflow for Teams. It's also now easier to capture and discover SME knowledge in Microsoft Teams and Slack with the Auto-Answer App. Carrie Koos , Natalie Rotnov 0 comment s July 31, 2024 Enterprise 2024.5: Encouraging and growing community contributions The latest Stack Overflow for Teams release makes it easier to encourage and grow contributions to your community through the use of flexible bounties, more user search options, Slack thread summarization, and more. Carrie Koos , Natalie Rotnov 0 comment s June 20, 2024 Enterprise 2024.4: Demonstrating and improving community impact In the latest Stack Overflow for Teams Enterprise release, you'll see reporting capabilities and insights that help demonstrate community impact. Microsoft customers can also rejoice: OverflowAI now includes an Auto-Answer App for Microsoft Teams. Carrie Koos , Natalie Rotnov 0 comment s April 30, 2024 Enterprise 2024.3: Collaborating smarter, not harder In the latest Stack Overflow for Teams Enterprise release, you'll see updates that make collaboration smarter and knowledge discovery easier. This release also includes OverflowAI, a GenAI-powered paid add-on to Enterprise subscriptions. Carrie Koos , Natalie Rotnov 0 comment s March 7, 2024 Enterprise 2024.2: Making collaboration intuitive and meaningful In the latest Stack Overflow for Teams Enterprise release, you'll see updates that make collaboration more intuitive and meaningful at several different touch points in the user journey, including a reimagined homepage. Carrie Koos , Natalie Rotnov 0 comment s February 5, 2024 Enterprise 2024.1: Celebrating and improving your community’s knowledge Let’s take a look at the first Stack Overflow for Teams Enterprise release of the year, focusing on how your teams can celebrate your community’s contributions and how search improvements will make these contributions more discoverable. Carrie Koos 0 comment s December 7, 2023 Enterprise 2023.3: Enriching the Stack Overflow for Teams Essentials After launching major features like Communities and Connectivity and a completely new API in 2023, we’re returning to some of the fundamentals of Stack Overflow for Teams to enrich the core experience and help connect users to knowledge faster. Carrie Koos 0 comment s August 10, 2023 Visualize knowledge flows with Connectivity Measure whether your organization is successfully breaking down knowledge silos. Carrie Koos 0 comment s May 17, 2023 Stack Overflow for Teams API v3 The latest version of the Stack Overflow for Teams API introduces a modern design with improved functionality. April 18, 2023 Introducing Communities on Teams: where domain, practice, and community come together with purpose Communities on Teams is a new way to bring people and knowledge together within a specific topic or focus to share valuable resources and collaborate in meaningful ways. Vasudha Swaminathan 1 comment January 18, 2023 “Your 2022 Stacked” year in review report A new feature to help celebrate your team’s contributions and community impact. Show more Our Stack Stack Internal Features Customers Security Pricing Stack Data Licensing Stack Ads Partnerships Services Stack Overflow Company Leadership Press Careers Social Impact Support Contact Stack Overflow help Stack Internal help Terms Privacy policy Cookie policy Your Privacy Choices Elsewhere Blog Dev Newsletter Podcast Releases Dev Survey Site design / logo © 2026 Stack Exchange Inc. Light Dark Auto | 2026-01-13T08:48:28 |
https://dev.to/help/organizations/maximizing-your-dev-organization | Maximizing Your DEV Organization's Reach - DEV Help - DEV Community Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account DEV Community Close DEV Help The latest help documentation, tips and tricks from the DEV Community. Help > Organizations > Maximizing Your DEV Organization's Reach Maximizing Your DEV Organization's Reach In this article Engagement & Community Interaction Team Engagement Content Visibility Reach Expansion Community Engagement Enhanced Visibility Content Strategy Top Tips Now that you've set up your DEV organization account, here are some tips to leverage it to its fullest potential. Engagement & Community Interaction Team Engagement Encourage all team members to join your DEV organization and complete their profiles. Humanize your team and attract readers with complete profiles including photos and bios. Content Visibility Maximize content visibility by using relevant popular tags . Choose tags strategically to ensure maximum exposure for your posts. It's a good strategy to select relevant popular tags and add all four tags to each post to maximize the number of folks who see your content. Reach Expansion Enable a call-to-action in your organization settings (bottom of the page) to include a link in the sidebar of your posts. This is a great way to generate leads or raise awareness about free courses. After publishing an article, share it on your organization's Twitter / X account. This gives DEV something to consider retweeting and extends your reach. Also, whenever posting articles, make sure to credit the correct author who wrote it; if you have a single person on your team reposting your org's blog on behalf of team members, ensure you follow the steps to credit articles appropriately and make use of our canonical link. Community Engagement Engage with the DEV Community by interacting with members. Comment on posts, follow other users, and maintain genuine interactions to increase visibility and engagement with your organization. Enhanced Visibility Utilize cover images on your posts to enhance visibility in the main feed. Content Strategy There's no one-size-fits-all approach to content, but here are some strategies that tend to resonate with the DEV Community: Round-ups and tool lists Technical deep-dives and tutorials Fair comparisons of technologies Casual walkthroughs over formal documentation Authentic, straightforward writing Remember to share your full posts on DEV and avoid overly promotional content. If you're looking to advertise, consider DEV Advertising as a natural way to promote your product or service to the Community. Top Tips Engage with the DEV Community regularly by commenting and liking posts. Genuine interactions boost visibility for your organization. Participate in the weekly DEV welcome thread and leave comments on relevant #discuss posts to welcome new members and join discussions. Create #discuss posts for open-ended questions and encourage participation from your community. By implementing these strategies and tips, you can make the most of your DEV Organization account and engage effectively with the Community. 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV DEV Community — A space to discuss and keep up software development and manage your software career Home DEV++ Podcasts Videos DEV Education Tracks DEV Challenges DEV Help Advertise on DEV DEV Showcase About Contact Free Postgres Database Software comparisons Forem Shop Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . DEV Community © 2016 - 2026. We're a place where coders share, stay up-to-date and grow their careers. Log in Create account | 2026-01-13T08:48:28 |
https://www.linkedin.com/psettings/guest-controls?trk=content_footer-guest-controls | {"remindersToPost":"reminders_to_post","adsEducation":"ads_education","unfollowed":"unfollowed","adsInferredLocation":"ip_personalization","whoCanMessageMe":"who_can_message_me","userSessions":"user_sessions","enterpriseProductsOnLinkedin":"enterprise_products_on_linkedin","trendingConversations":"trending_conversations","candidateInterviews":"candidate_interviews","jobsOnLinkedin":"jobs_on_linkedin","liveVideos":"live_videos","jobApplicationAccounts":"job_application_accounts","dataSharingForJobs":"data_sharing_for_jobs","eventAttendeeUpdates":"event_attendee_updates","researchInvitations":"research_invites","marketingSolutions":"marketing_solutions","demographicInfoCopy":"demographic_info","wechat":"wechat","breakingNews":"breaking_news","workAnniversaryUpdates":"work_anniversary_updates","profileUpdatesViaPush":"profile_updates_via_push","profileUpdatesOnLinkedin":"profile_updates_on_linkedin","wechatNotification":"wechat","manageEmailAddresses":"manage_email_addresses","manageBlockedPages":"manage_blocked_pages","showProfilePhotos":"show_profile_photos","detectHarmfulContent":"scanning_messages","directMessages":"direct_messages","enterpriseProductsViaEmail":"enterprise_products_via_email","profileViews":"profile_views","searchAppearances":"search_appearances","groupInvitations":"group_invitations","interestCategories":"interest_categories","messagesFromCandidates":"messages_from_candidates","changePassword":"change_password","jobReferrals":"job_referrals","savedJobs":"saved_jobs","networkCatchUpUpdates":"network_catch_up_updates","hiringSomeoneJobPosts":"hiring_someone_job_posts","pageMessaging":"page_messaging","ADS":"advertising_data","networkUpdatesOnLinkedin":"network_updates_on_linkedin","onLinkedin":"channel_on_linkedin","adsBasedOnGroups":"ads_groups","careerAdvice":"career_advice","conversationsOnLinkedin":"conversations_on_linkedin","passkey":"passkey","pageInvitations":"page_invitations","inmail":"inmail","SERVICES":"services","notifyNetworkForUpdates":"notify_network_for_updates","enableSoundsIos":"ux_system_sounds","hibernateAccount":"hibernate_account","networkUpdatesViaEmail":"network_updates_via_email","premiumNotifications":"premium_notifications","adsExperienceWithinMessagingInbox":"ads_experience","SIGN_IN_AND_SECURITY":"sign_in_and_security","messaging":"messaging","updatesFromConnections":"updates_from_connections","editorsChoice":"editors_choice","jobRecommendations":"job_recommendations","readReceipts":"read_receipts","lastNameVisibility":"last_name_visibility","premiumBillingInfo":"premium_billing_info","profileRecommendations":"profile_recommendations","adsPersonalization":"ads_personalization","networkUpdatesViaPushMessages":"network_updates_via_push_messages","jobAlerts":"job_alerts","followerInsightVisibility":"follower_insight_visibility","workplaceInsights":"workplace_insights","dataExportByPageAdmins":"data_export_by_page_admins","groupUpdates":"group_updates","notifyNetworkAboutMyMentions":"notify_network_about_my_mentions","tipsForUsingLinkedin":"tips_for_using_linkedin","adsCompaniesFollowed":"ads_companies_followed","newFollowers":"new_followers","adsByAge":"ads_age","hiringUpdates":"hiring_updates","adsLocation":"ads_location","newsUpdatesViaEmail":"news_updates_via_email","newsUpdatesViaPush":"news_updates_via_push","searchingForAJob":"searching_for_a_job","darkModeDesktop":"dark_mode","jobChangeUpdates":"job_change_updates","discoverMeByPhoneNumber":"discover_me_by_phone_number","push":"channel_push","suggestedConversations":"suggested_conversations","jobApplicationUpdates":"job_application_updates","demographicInfo":"demographic_info","guestCookies":"guest_cookies","adsDemographics":"ads_demographics","linkedInActivityData":"linkedin-activity-data","projectUpdates":"project_updates","jobPostUpdates":"job_post_updates","dailyDigests":"daily_digests","specialReports":"special_reports","managePhoneNumbers":"manage_phone_numbers","contentRecommendations":"content_recommendations","suggestReplies":"suggest_replies","emailAddressVisibility":"email_address_visibility","newsUpdatesOnLinkedin":"news_updates_on_linkedin","closeAccounts":"close_accounts","chooseInvitationsTypes":"choose_invitations_types","adsEmployer":"ads_employer","verifications":"trusted_verifications","sponsoredRequests":"sponsored_requests","allowPersonalizedJobRecommendations":"allow_personalized_job_recommendations","languageForTranslation":"language_for_translation","remindersToClaimJobs":"reminders_to_claim_jobs","preferredView":"preferred_view","adsJobInformation":"ads_job_information","eventOrganizerUpdates":"event_organizer_updates","helpCenterOnLinkedin":"help_center_on_linkedin","adsRelatedActions":"ads_related_actions","enableSoundsAndroid":"ux_system_sounds","policyAndAcademicResearch":"policy_and_academic_research","notifyMeWhenMentioned":"notify_me_when_mentioned","reminders":"reminders","newConnectionRecommendations":"new_connection_recommendations","organizationAndInterests":"organization_and_interests","groupAdminUpdates":"group_admin_updates","weeklyCatchUpSummary":"weekly_catch_up_summary","twoFactorAuthentication":"two_factor_authentication","pageVisitVisibility":"page_visit_visibility","reviewsForYourServices":"reviews_for_your_services","profileUpdatesViaEmail":"profile_updates_via_email","sms":"sms","premiumTipsForUsingLinkedin":"premium_tips_for_using_linkedin","focusedInbox":"focused_inbox","updatingYourProfile":"updating_your_profile","premiumManageAccount":"premium_manage_account","birthdayUpdates":"birthday_updates","attendingEvents":"attending_events","updatesFromPeopleYouFollow":"updates_from_people_you_follow","searchHistory":"search_history","darkModeiOS":"dark_mode","NOTIFICATIONS":"notifications","whatsapp":"whatsapp","shareDataWithSelectPartners":"share_data_with_trusted_partners","pages":"pages","connectionsVisibility":"connection_visibility","rememberMe":"remember_me","feedPreferences":"feed_preferences","groups":"groups","profileVisibilityForPartners":"profile_visibility_for_partners","educationAndBestPractices":"education_and_best_practices","getVerified":"get_verified","adsBeyondLinkedin":"ads_beyond_linkedin","language":"language","adsByGender":"ads_gender","linkedinPromotions":"linkedin_promotions","shareLeadUpdatesWithSalesNavigatorsUser":"sn_share_lead_updates","downloadMyData":"download_my_data","recommendations":"recommendations","advertisingNotifications":"advertising_notifications","premiumCareerAdvice":"premium_career_advice","directMessageReminders":"direct_message_reminders","email":"channel_email","PROFILE_VISIBILITY":"visibility_profile","connectingWithOthers":"connecting_with_others","shareDataWithTrustedPartners":"share_data_with_trusted_partners","gamePlay":"game_play","receiveInvitations":"receive_invitations","eventSpeakerInvitations":"event_speaker_invitations","billingReminders":"billing_reminders","commentsAndReactions":"comments_and_reactions","newSkillEndorsements":"new_skill_endorsements","shares":"shares","dataSharingForPermittedServices":"data_sharing_for_permitted_services","serviceProjectUpdates":"service_project_updates","SETTINGS":"home","manageByBlockedList":"manage_by_blocked_list","conversationsViaPushMessages":"conversations_via_push_messages","smsControls":"sms","enterpriseCookies":"enterprise_cookies","aiTrainerProjectAlerts":"ai_trainer_project_alerts","profileVisibilityForMicrosoftApps":"profile_visibility_for_microsoft_apps_users","dataForAiImprovement":"data_for_ai_improvement","collaborativeArticles":"collaborative_articles","darkMode":"dark_mode","newsletters":"newsletters","dataSharingForLearning":"data_sharing_for_learning","highlightsFromFollowedCompanies":"highlights_from_followed_companies","groupRecommendations":"group_recommendations","conversationsViaEmail":"conversations_via_email","postingAndCommenting":"posting_and_commenting","useLinkedinDataInMicrosoftWord":"use_linkedin_data_in_microsoft_word","PRIVACY":"data_privacy","connectedMicrosoftAccounts":"connected_microsoft_accounts","enableSoundsDesktop":"ux_system_sounds","activityOnYourPages":"activity_on_your_pages","profileViewingOptions":"profile_viewing_options","newProposals":"new_proposals","recruiterCalls":"recruiter_calls","autoplayVideos":"auto_play_videos","connectionAnniversaryUpdates":"connection_anniversary_updates","adsInteractionsWithBusiness":"ads_interactions_with_business","videoRecommendations":"video_recommendations","ACCOUNT":"account_preferences","yearInReview":"year_in_review","newFollowRecommendations":"new_follow_recommendations","invitations":"invitations","pageUpdates":"page_updates","memberCookies":"member_cookies","recentInteractionUpdates":"recent_interaction_updates","discoverMeByEmailAddress":"discover_me_by_email_address","messageNudging":"message_nudging","careerAndProfessionalInsights":"career_and_professional_insights","educationUpdates":"education_updates","skillsPathUpdates":"skills_path_updates","signalRecruiterForJobAlerts":"signal_recruiter_for_job_alerts","manageDataAndActivity":"manage_data_and_activity","premiumTipsOnLinkedin":"premium_tips_on_linkedin","candidateRecommendations":"candidate_recommendations","shareProfileWithJobApplications":"share_profile_with_job_applications","reportsAndInsights":"reports_and_insights","verificationsNotifications":"verifications_notifications","adsConnections":"ads_connections","darkModeAndroid":"dark_mode","mentions":"mentions","safetyAndReportingOnLinkedin":"safety_and_reporting_on_linkedin","skillAssessmentRecommendations":"skill_assessment_recommendations","invitationsToConnect":"invitations_to_connect","manageMyActiveStatus":"manage_my_active_status","viewYourReportsNotifications":"view_your_reports_notification","followed":"followed","inmailReminders":"inmail_reminders","hiringSomeoneProjectWork":"hiring_someone_project_work","customNews":"custom_news","safetyAndReportingViaEmail":"safety_and_reporting_via_email","requestsForReviews":"requests_for_reviews","jobUpdatesViaEmail":"job_updates_via_email","gamesNotifications":"games_notifications","insightsOnYourPages":"insights_on_your_pages","jobsUpdatesViaPush":"jobs_updates_via_push"} LinkedIn Settings Help Center Unsubscribe Unsubscribe from LinkedIn Email Communications LinkedIn uses email addresses uploaded by members to make suggestions in features like People You May Know. Use this link to unsubscribe, you will stop receiving LinkedIn invitations and your email will stop being processed by LinkedIn. Unsubscribe from LinkedIn SMS Communications LinkedIn uses phone numbers uploaded by members to make suggestions in features like People You May Know. If you are a LinkedIn member, you may also receive select notifications via SMS, such as PIN verification codes. Use this link to unsubscribe. You will stop receiving LinkedIn SMS and your phone number will stop being processed by LinkedIn. urn:li:page:d_flagship3_settings_guest_controls;dff43ac7-ced2-454e-86b4-50ec41800a67 false | 2026-01-13T08:48:28 |
https://developer.x.com/developer-terms/policy#4-g | Developer Policy – X Developers | X Developer Platform <g> <g> <defs> <rect id="SVGID_1_" x="-468" y="-1360" width="1440" height="3027" /> </defs> <clippath id="SVGID_2_"> <use xlink:href="#SVGID_1_" style="overflow:visible;" /> </clippath> </g> </g> <rect x="-468" y="-1360" class="st0" width="1440" height="3027" style="fill:rgb(0,0,0,0);stroke-width:3;stroke:rgb(0,0,0)" /> <path d="M13.4,12l5.8-5.8c0.4-0.4,0.4-1,0-1.4c-0.4-0.4-1-0.4-1.4,0L12,10.6L6.2,4.8c-0.4-0.4-1-0.4-1.4,0c-0.4,0.4-0.4,1,0,1.4 l5.8,5.8l-5.8,5.8c-0.4,0.4-0.4,1,0,1.4c0.2,0.2,0.4,0.3,0.7,0.3s0.5-0.1,0.7-0.3l5.8-5.8l5.8,5.8c0.2,0.2,0.5,0.3,0.7,0.3 s0.5-0.1,0.7-0.3c0.4-0.4,0.4-1,0-1.4L13.4,12z" /> </svg>" data-icon-chevron-right="<svg xmlns="http://www.w3.org/2000/svg" width="24" height="24" viewbox="0 0 24 24" aria-hidden="true" focusable="false" role="none" class="twtr-icon"> <path opacity="0" d="M0 0h24v24H0z" /> <path d="M17.207 11.293l-7.5-7.5c-.39-.39-1.023-.39-1.414 0s-.39 1.023 0 1.414L15.086 12l-6.793 6.793c-.39.39-.39 1.023 0 1.414.195.195.45.293.707.293s.512-.098.707-.293l7.5-7.5c.39-.39.39-1.023 0-1.414z" /> </svg>" data-icon-chevron-down="<svg xmlns="http://www.w3.org/2000/svg" width="24" height="24" viewbox="0 0 24 24" aria-hidden="true" focusable="false" role="none" class="twtr-icon"> <path opacity="0" d="M0 0h24v24H0z" /> <path d="M20.207 7.043c-.39-.39-1.023-.39-1.414 0L12 13.836 5.207 7.043c-.39-.39-1.023-.39-1.414 0s-.39 1.023 0 1.414l7.5 7.5c.195.195.45.293.707.293s.512-.098.707-.293l7.5-7.5c.39-.39.39-1.023 0-1.414z" /> </svg>" data-icon-arrow-left="<svg width="28px" height="28px" viewbox="0 0 28 28" version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" aria-hidden="true" focusable="false" role="none" class="twtr-icon u01-meganav__icon-arrow-left"> <g stroke="none" stroke-width="1" fill="none" fill-rule="evenodd" stroke-linecap="round"> <g transform="translate(-1216.000000, -298.000000)" stroke-width="2.25"> <g transform="translate(1200.000000, 282.000000)"> <g transform="translate(17.000000, 17.000000)"> <path d="M0.756410256,12.8589744 L25.7179487,12.8589744"></path> <path d="M13.2371795,25.3397436 L25.7179487,12.8589744"></path> <path d="M13.2371795,12.4807692 L25.3397436,0.378205128" transform="translate(19.288462, 6.429487) rotate(-90.000000) translate(-19.288462, -6.429487) "></path> </g> </g> </g> </g> </svg>" data-left-nav-items="[{"isActive":false,"hasActiveChild":false,"children":[{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"X API","linkDisabled":false,"title":"X API","path":"https://developer.x.com/en/products/twitter-api"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"X Ads API","linkDisabled":false,"title":"X Ads API","path":"https://developer.x.com/en/products/x-ads-api"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"X for websites","linkDisabled":false,"title":"X for websites","path":"https://developer.x.com/en/products/x-for-websites"}],"overviewTitle":"Products","linkDisabled":true,"title":"Products","path":"https://developer.x.com/en/products"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Docs","linkDisabled":false,"title":"Docs","path":"https://docs.x.com/"},{"isActive":false,"hasActiveChild":false,"children":[{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Build for business","linkDisabled":false,"title":"Build for business","path":"https://developer.x.com/en/use-cases/build-for-businesses"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Build for the public","linkDisabled":false,"title":"Build for the public","path":"https://developer.x.com/en/use-cases/build-for-consumers"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Do research","linkDisabled":false,"title":"Do research","path":"https://developer.x.com/en/use-cases/do-research"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Teach \u0026 learn","linkDisabled":false,"title":"Teach \u0026 learn","path":"https://developer.x.com/en/use-cases/teach-and-learn"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Build for good","linkDisabled":false,"title":"Build for good","path":"https://developer.x.com/en/use-cases/build-for-good"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Build for fun","linkDisabled":false,"title":"Build for fun","path":"https://developer.x.com/en/use-cases/build-for-fun"}],"overviewTitle":"Use Cases","linkDisabled":true,"title":"Use Cases","path":"https://developer.x.com/en/navigation/left-nav-items/use-cases"},{"isActive":false,"hasActiveChild":false,"children":[{"isActive":false,"hasActiveChild":false,"children":[{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Changelog","linkDisabled":false,"title":"Changelog","path":"https://docs.x.com/updates/changelog"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Blog","linkDisabled":false,"title":"Blog","path":"https://developer.x.com/en/blog"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Newsletter","linkDisabled":false,"title":"Newsletter","path":"https://developer.x.com/en/updates/stay-informed"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"YouTube","linkDisabled":false,"title":"YouTube","path":"https://www.youtube.com/c/twitterdev"}],"linkDisabled":true,"title":"Stay informed","path":"https://developer.x.com/"},{"isActive":false,"hasActiveChild":false,"children":[{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Forums","linkDisabled":false,"title":"Forums","path":"https://twittercommunity.com/"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Events","linkDisabled":false,"title":"Events","path":"https://twitterdev.bevylabs.com/"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Insiders","linkDisabled":false,"title":"Insiders","path":"https://developer.twitter.com/en/community/insiders"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Community leaders","linkDisabled":false,"title":"Community leaders","path":"https://developer.x.com/en/community/leaders"}],"linkDisabled":true,"title":"Connect","path":"https://developer.x.com/"}],"overviewTitle":"Community","linkDisabled":false,"menuType":"multiCategory","title":"Community","path":"https://developer.x.com/en/community"}]" data-right-nav-items="[{"isActive":false,"hasActiveChild":false,"children":[{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Policies","linkDisabled":false,"title":"Policies","path":"https://developer.x.com/en/developer-terms"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Developer agreement","linkDisabled":false,"title":"Developer agreement","path":"https://developer.x.com/en/developer-terms/agreement-and-policy/source"}],"overviewTitle":"Support","linkDisabled":false,"title":"Support","path":"https://developer.x.com/en/support"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Developer Portal","linkDisabled":false,"title":"Developer Portal","path":"https://developer.twitter.com/en/portal/petition/essential/basic-info"}]" data-cta-enabled="true" data-profile-enabled="true" data-cta-link-new-tab="false" data-root-page-title="Developer Platform"> Developer terms Developer Policy Let's get started X + Developers Using this policy X + Developers Using this policy X + Developers X loves developers. We’re delighted and amazed by the tools and services this community creates by harnessing the power of X data. As part of our commitment to this community, we aim to provide data access that is open and fair for developers, safe for people on X, and beneficial for the X platform as a whole. To further these goals we’ve crafted the Developer Policy as a guide to help people understand our rules and expectations about appropriate API and X Content usage. This Developer Policy (“ Policy ”) provides rules and guidelines for developers who interact with X’s ecosystem of applications, services, website, web pages and content. It is part of your contract with X governing access to and use of the X API and X Content (either as part of the Developer Agreement or other written agreement with X). Policy violations are considered violations of your agreement. This Policy may be changed from time to time without notice. Capitalized terms used in this Policy, which are not defined in this Policy, will have the respective meanings ascribed to them in the Developer Agreement or the Master License Agreement. Using this policy We’ve structured this policy to make it as easy to follow as possible. Please keep information from the following policy sections top of mind as you use the X API and X Content: 1. Set Yourself Up for Success - You are responsible for complying with all X policies. It’s important that you review and understand this Policy, as well as the policies we link to in this document, before you access the X API and X Content. The time spent reviewing our policies may save you hours of rework down the road. 2. Privacy and Control are Essential - Protecting and defending the privacy of people on X is built into the core DNA of our company. As such, we prohibit the use of X data in any way that would be inconsistent with people’s reasonable expectations of privacy. By building on the X API or accessing X Content, you have a special role to play in safeguarding this commitment, most importantly by respecting people’s privacy and providing them with transparency and control over how their data is used. 3. Follow the Platform Usage Guidelines - Getting approved to access the X API and X Content is just the first step. Our Platform Usage Guidelines should be your first stop anytime you have questions about how to ensure policy compliance for your planned use of the X platform. We’ve provided a lot more detail on what each of these three key sections mean below. Please review them carefully to ensure that your usage of the X API and X Content is consistent with our policies. If we believe you are in violation of this Policy (or any other X policy), we may suspend or permanently revoke your access to the X API and X Content. Finally, please note that X may monitor your use of the X API to improve the X Applications, to examine any commercial use, and to ensure your compliance with your approved use case and this Policy. Thanks for reading, and thank you for building with us! We look forward to seeing what you create! Chapter 1 Set yourself up for success Set yourself up for success Set yourself up for success Set yourself up for success You can avoid many potential pitfalls while using the X API by ensuring that your service has been built the right way from day 1. This section of the Developer Policy contains rules that all developers must follow before using the X API or X Content. The Free, Basic, and Pro plans (as described at developer.x.com/en ) are designed for hobbyists, commercial prototyping, early-stage X product integrations, and supporting applications with limited end-users. If you use the X API and X Content beyond this scope, then you must apply (or already subscribe to) an Enterprise plan (as described at developer.x.com/en ). We review all proposed uses of the X developer platform to verify policy compliance — so you’re required to disclose (and update, as applicable) your planned use of the X API and X Content in order to be granted and to maintain access. All new developers must apply for a developer account to access the X API. Current developers without an approved developer account must apply for one as directed to do so by X. As part of this process, you’ll need to provide us with a written description of your intended uses of the X API and X Content. Your use case description is binding on you, and any substantive deviation from it may constitute a violation of our rules and result in enforcement action. You must notify us of any substantive modification to your use case and receive approval before you may begin using X Content for that new purpose. Failure to do so may result in suspension and termination of your API and data access. By building on the X API or accessing X Content, you must comply with ALL X policies. These include this Developer Policy , the Automation Rules , the Display Requirements , the API Restricted Uses Rules , the X Rules , and the X Brand Resources , as well as any other agreements you enter into with X relating to your use of the X API or X Content, including but not limited to the Developer Agreement or a Master Licensing Agreement or Order (as applicable). You must also comply with any modifications to these policies and any new policies launched by X. It is your responsibility to monitor the use of your service and to design your service to prevent violations of X policy by people who use it. Failure to do so may result in suspension or termination of your API and X Content access. You may not register multiple applications for a single use case or substantially similar or overlapping use cases. In this context, a “use case” is a consistent set of analyses, displays, or actions performed via an application. "White label" versions of a tool or service are not permissible. If you plan to “white label” versions of your application, you must notify and receive separate approval from us. As a single exception to these rules, you may create and use a maximum of 3 applications for development, staging, and production instances of the same service. These apps must be registered to a single account, and should be clearly identified (in the name and description) as dev, staging, and prod instances of a single service. You may not use development or staging applications for production purposes. You must keep all API keys or other access credentials private. You may not use, and may not encourage or facilitate others to use, API keys or other access credentials owned by others. Your license agreement with X limits your use of the X API and X Content. Among other things, the X API has rate limits which help to ensure fair data usage and to combat spam on the platform. You may not exceed or circumvent rate limits, or any other limitations or restrictions described in this Policy or your agreement with X, listed on the Developer Site , or communicated to you by X. You may not remove or alter any proprietary notices or marks on X Content received via the X API. This helps to make sure that people know where X Content is coming from, and who it belongs to. For data integrity and platform health reasons, you may not interfere with, intercept, disrupt, or disable any features of the X API or the X service. In other words, use the APIs as intended and documented on developer.x.com . Refer to our HackerOne guidelines for more details about acceptable use. Chapter 2 Privacy and control are essential Privacy and control are essential Consent & permissions Content compliance Off-X matching Your privacy policy Using geo-data X passwords Privacy and control are essential Consent & permissions Content compliance Off-X matching Your privacy policy Using geo-data X passwords Privacy and control are essential X takes privacy seriously, and we expect everyone using X Content and the X API to do the same. Any use of the X developer platform, X API, or X Content in a manner that is inconsistent with peoples’ reasonable expectations of privacy may be subject to enforcement action, which can include suspension and termination of API and X Content access. Your commitment to privacy and control must extend to all uses of X Content and all aspects of the service that you build using our API. To that end, the people using your service must understand and consent to how you use their data, and how you access X on their behalf. This can be accomplished through providing people with a clear, comprehensive, and transparent privacy policy, as well as ensuring that you get express and informed consent from each person using your service before taking any action on their behalf. Please note that a person authenticating into your service does not by itself constitute consent. Consent & permissions In particular, you must get express and informed consent from people before doing any of the following: Taking any actions on their behalf. This includes (but is not limited to): Posting content to X Following/unfollowing accounts Modifying profile or account information Adding hashtags or any other content to Posts Republishing content accessed by means other than via the X API or other X tools Using someone’s X Content to promote a product or service Storing non-public content such as Direct Messages (DMs), or any other private or confidential information Sharing or publishing protected content, or any other private or confidential information If your service allows people to post content to X you must do the following before publishing: Show exactly what will be published Make it clear to people using your service what geo information (if any) will be added to the content If your service allows people to post content to both your service and X, you must do the following before publishing: Obtain permission to post the content Explain where you will post the content You must respect the protected and blocked status of all X Content. You may not serve content obtained using one person’s authentication token to a different person who is not authorized to view that content. Protected accounts: A protected account ’s content is only available to people who have been approved by the owner to follow that account. So, if you run a service that accesses protected accounts, you may only do so to serve such content to the specific people with permission to view that content. Blocked accounts: People on X are able to block access to their accounts for any reason they choose. Commingling information obtained from tokens (or any other API-based action) to bypass this choice is not permitted. As Direct Messages (DMs) are non-public in nature, services that provide DM features must take extra steps to safeguard personal privacy. You may not serve DM content to people who are not authorized to view that content. If your service provides DM functionality you must also: Notify people if you send read receipt events for DMs. You can do this by providing a notice directly in your service, or by displaying read receipts from other participants in a conversation. Get consent before configuring media to be sent in a DM as "shared" (i.e. reusable across multiple DMs). If you do allow media in a DM to be “shared,” you must provide a clear notice that this content will be accessible to anyone with the media’s URL. Content compliance If you store X Content offline, you must keep it up to date with the current state of that content on X. Specifically, you must delete or modify any content you have if it is deleted or modified on X. This must be done as soon as reasonably possible, or within 24 hours after receiving a request to do so by X or the applicable X account owner, or as otherwise required by your agreement with X or applicable law. This must be done unless otherwise prohibited by law, and only then with the express written permission of X. Modified content can take various forms. This includes (but is not limited to): Content that has been made private or gained protected status Content that has been suspended from the platform Content that has had geotags removed from it Content that has been withheld or removed from X Off-X matching We limit the circumstances under which you may match a person on X to information obtained or stored off-X. Off-X matching involves associating X Content, including a X @handle or user ID, with a person, household, device, browser, or other off-X identifier. You may only do this if you have express opt-in consent from the person before making the association, or as described below. In situations in which you don’t have a person’s express, opt-in consent to link their Xidentity to an off-X identifier, we require that any connection you draw be based only on information that someone would reasonably expect to be used for that purpose. In addition, absent a person’s express opt-in consent you may only attempt to match your records about someone to a X identity based on: Information provided directly to you by the person. Note that records about individuals with whom you have no prior relationship, including data about individuals obtained from third parties, do not meet this standard; and/or Public data. “Public data” in this context refers to: Information about a person that you obtained from a public, generally-available resource (such as a directory of members of a professional association) Information on X about a person that is publicly available, including: Posts Profile information, including an account bio and publicly-stated location Display name and @handle Your privacy policy You must display your service’s privacy policy to people before they are permitted to download, install, or sign up to your service. It must disclose at least the following information: The information that you collect from people who use your service How you use and share that information (including with X) How people can contact you with inquiries and requests regarding their information Your privacy policy must be consistent with all applicable laws, and be no less protective of people than X’s Privacy Policy and the privacy policy of our other services and corporate affiliates . You must cease your access to the X API and the use of all X Content if you are unable to comply with your and/or X’s Privacy Policy. Using geo-data Use of geo data comes with additional restrictions due to the sensitive nature of this information. If your service adds location information to Posts, you must disclose to people: When you add location information Whether you add location information as a geotag or annotations data Whether your location information is listed as a place, or as geographic coordinates If your application allows people to post with their location you must comply with X’s geo guidelines in full. Any use of location data or geographic information on a standalone basis is prohibited. You may not (and may not permit others to) store, aggregate, or cache location data and other geographic information contained in X Content, except as part of a Post. For example, you may not separate location data or geographic information out from Posts to show where individuals have been over time. Heat maps and related tools that show aggregated geo activity (e.g., the number of people in a city using a hashtag) are permitted. X passwords You may not store X passwords, or request that people provide their X password, account credentials, or developer application information (including consumer key) to you directly. We suggest the use of Sign-in with X as the authentication tool to link your service and people on X. Chapter 3 Platform usage guidelines Platform usage guidelines Spam, bots, and automation X performance benchmarking Public display of Posts Content redistribution Pay to engage Service authenticy X name, logo, and likeness Advertising on X Platform usage guidelines Spam, bots, and automation X performance benchmarking Public display of Posts Content redistribution Pay to engage Service authenticy X name, logo, and likeness Advertising on X Platform usage guidelines Have you taken care to review X’s policies and set up your API access the right way? Does your service follow X’s privacy and control guidelines? If you can answer yes to these two questions, then you are ready to start using the X API and X Content. X’s Platform Usage Guidelines provide the assistance needed to ensure that your use of X Content is compliant from day 1 throughout the lifecycle of your service. We suggest reviewing these rules on a regular basis to make sure that your integration is operating in a way that is safe and beneficial to people on X and the X platform as a whole. Spam, bots, and automation The use of the X API and developer products to create spam, or engage in any form of platform manipulation, is prohibited. You should review the X Rules on platform manipulation and spam , and ensure that your service does not, and does not enable people to, violate our policies. Services that perform write actions, including posting Posts, following accounts, or sending Direct Messages, must follow the Automation Rules . In particular, you should: Always get explicit consent before sending people automated replies or Direct Messages Immediately respect requests to opt-out of being contacted by you Never perform bulk, aggressive, or spammy actions, including bulk following Never post identical or substantially similar content across multiple accounts If you’re operating an API-based bot account you must clearly indicate what the account is and who is responsible for it. You should never mislead or confuse people about whether your account is or is not a bot. A good way to do this is by including a statement that the account is a bot in the profile bio. X performance benchmarking You may not use the X API to measure the availability, performance, functionality, or usage of X for benchmarking, competitive, or commercial purposes. For example, you should never use the X API to: Calculate aggregate X metrics, such as the total number of Monthly Actives (MAs) or Daily Actives (DAs) Calculate aggregate X Post metrics, such as the total number of Posts posted per day, or the number of account engagements Measure or analyze the responsiveness of X Measure or analyze spam or security on X, except as permitted below We support research that helps improve conversational health on X. You may not publicly disclose any research or findings concerning, or develop, create, or offer services using, the X API or X Content that measure, analyze, or attempt to identify behaviors or content which violate X policies without express written permission from X. DSA Researchers: If you need to contact X relating to access under Art. 40 of the Digital Services Act, please contact EU-Questions@X.com . If you wish to apply for researcher access, please submit an application . Public display of Posts You must maintain the integrity of all X Content that you display publicly or to people who use your service. If you don’t use X for Websites to display content, then you must use the X API to retrieve the most current version available for display. If displayed content ceases to be available through the X API, then you must remove it from your service as soon as reasonably possible, or within 24 hours after the receipt of a removal request from X, or the applicable X account owner, or as otherwise required by applicable law. There are specific rules you must follow if you display X Content offline. Follow the guidelines for using Posts in broadcast if you display Posts offline. If you embed or display Posts, you must contact us about your X API access if your site exceeds 10 million daily impressions. X reserves the right to require additional terms as a condition to your use of the X API. Additional restrictions on X for Websites developer use include: Embedded Posts and/or embedded timelines You must provide people with legally sufficient notice that fully discloses X’s collection and use of data about browsing activities on your website, including for interest-based advertising and personalization. You must also obtain legally sufficient consent from people for such collection and use You must provide legally sufficient instructions on how people can opt out of X’s interest-based advertising and personalization as described here X for Websites widgets You must ensure that people are provided with clear and comprehensive information about, and consent to, the storing and accessing of cookies or other information on their devices as described in X’s cookie use , where providing such information and obtaining such consent is required by law Services targeted to children under 13 Services targeted to children under 13 must opt out of tailoring X in any embedded Post and/or embedded timelines by setting the opt-out parameter to be ‘true’ as described here Content redistribution The best place to get X Content is directly from X. Consequently, we restrict the redistribution of X Content to third parties. If you provide X Content to third parties, including downloadable datasets or via an API, you may only distribute Post IDs, Direct Message IDs, and/or User IDs (except as described below). In total, you may not distribute more than 1,500,000 Post IDs to any entity (inclusive of multiple individuals associated with a single entity) within any 30 day period unless you have received written permission from X. In addition, developers may provide up to 500 public Posts Objects and/or User Objects to each person who uses your service on a daily basis if this is done via non-automated means (e.g., download of spreadsheets or PDFs). Academic researchers are permitted to distribute Post IDs and/or User IDs solely for the purposes of non-commercial research on behalf of an academic institution, and that has been approved by X in writing, or peer review or validation of such research. Only as many Post IDs or User IDs that is necessary for such research, and has been approved by X may be used. Any X Content provided to third parties remains subject to this Policy, and those third parties must agree to the X Terms of Service , Privacy Policy , Developer Agreement , and Developer Policy before receiving such downloads. You may not enable any entity to circumvent any other limitations or restrictions on the distribution of X Content as contained in this Policy , the Developer Agreement , or any other agreement with X. Note: This Section does not apply to researchers with X API access via Art. 40 of the EU Digital Services Act (2022) (“ DSA ”), who are instead subject to the procedures and restrictions set forth in the DSA and the Developer Agreement. Pay to engage Your service shouldn’t compensate people to take actions on X, as that results in inauthentic engagement that degrades the health of the platform. As you use the X API you may not sell or receive monetary or virtual compensation for any X actions. This includes, but is not limited to, Posts, follows, unfollows, reposts, likes, comments, and replies. Service authenticity You must clearly identify your service so that people can understand its source and purpose. Don’t use names, logos, or URLs that mask your service’s identity and features, or that falsely imply an affiliation with X or third parties. Note that creating applications for the purpose of selling names, or to prevent others from using names, is prohibited. You may not use any URL (including shortened URLs) for your service that directs people to: A site that is unrelated to your service A spam or malware site A site that encourages people to violate X policy X name, logo, and likeness You may only use and display the X name and logo to identify X as the source of X Content. You should never use the X name and logo, the X Official Partner Program badge, or any other similar marks or names in a manner that creates a false sense of endorsement, sponsorship, or association with X. The X Brand Resources contain detailed information to help you use the X brand in the right way. You may only use the X Verified Account badge and any other enhanced account categorization as it is reported to you by X through the API. This helps people know that the content your service displays is equivalent to that shown on X. Advertising on X There are restrictions regarding how and where you are allowed to advertise around X Content. To start, your advertisements can’t resemble or reasonably be confused by people as a Post. Other rules on advertising include: There must be a clear separation between X Content and your advertisements. You may not place any advertisements within the X timeline other than X Ads. X reserves the right to serve advertising via the X API. If you decide to serve X Ads once we start delivering them via the API, we will share a portion of advertising revenue with you in accordance with the relevant terms and conditions. You may not use X Content, or information obtained from the X API to target people with advertising outside of the X platform. Chapter 4 Rules for specific X services or features X login X Cards Definitions X login X Cards Definitions The following additional rules apply for any use of the X services or features listed below: X login You must present people with easy to find options to log into and out of X, for example via the OAuth protocol. The Sign in with X option must be displayed at least as prominently as any other sign-up or sign-in feature on your service. You must also provide people without a X account the opportunity to create one via X. Once someone on your service authenticates via Sign in with X you must clearly display their X identity. X identity includes the person’s current X @handle, avatar, and X logo. Any display of someone’s X followers on your service must clearly show that the relationship is associated with X. X Cards To ensure a quality experience you must develop your Card to render across all platforms where Cards are displayed. Additional rules that you must follow when using Cards include: You must mark your Post as ‘true’ for sensitive media if you plan to display such media within a Card You must use HTTPS for hosting all assets within your Card. Your Card should never generate active mixed content browser warnings Audio and video content should include stop or pause controls, and default to ‘sound off’ for videos that automatically play content You may not exceed or circumvent X’s limitations placed on any Cards, including the Card’s intended use. Additional restrictions on Cards use include: You may not place third-party sponsored content within Cards without X’s approval You may not attach monetary incentives (including virtual currency) within your Card or on X from your Card You may not include content or actions within your Card that are misleading or not contextually relevant, such as URLs and media You may only attach an App Card to a Post when someone is explicitly promoting or referring to the app in the Post Definitions X Content ‒ Posts, Post IDs, X end user profile information, and any other data and information made available to you through the X API or by any other means authorized by X, and any copies and derivative works thereof. Developer Site ‒ X’s developer site located at https://developer.x.com . Services ‒ Your websites, applications and other offerings that display X Content or otherwise use the Licensed Material as explicitly approved by X. Post ID ‒ A unique identification number generated for each Post. Post ‒ A posting made on X Applications. “X” ‒ Means (a) X Corp. (865 FM 1209, Building 2, Bastrop, TX 78602, USA) if your principal place of business is outside the European Union, EFTA States, and the United Kingdom; or (b) X Internet Unlimited Company (One Cumberland Place, Fenian Street, Dublin 2, D02 AX07, Ireland) if your principal place of business is in the European Union, EFTA States, or the United Kingdom. Direct Message - A message that is privately sent on X Applications by one end user to one or more specific end user(s) using X’s Direct Message function. X API ‒ The X Application Programming Interface (“API”), Software Development Kit (“SDK”) and/or the related documentation, data, code, and other materials provided by X with the API, as updated from time to time, including without limitation through the Developer Site. X Applications ‒ X’s consumer facing products, services, applications, websites, web pages, platforms, and other offerings, including without limitation, those offered via https://x.com and X's mobile applications. Developer policy and terms Follow @XDevelopers Subscribe to developer news X platform X.com Status Accessibility Embed a post Privacy Center Transparency Center Download the X app Try Grok.com X Corp. About the company Company news Brand toolkit Jobs and internships Investors Help Help Center Using X X for creators Ads Help Center Managing your account Email Preference Center Rules and policies Contact us Developer resources Developer home Documentation Forums Communities Developer blog Engineering blog Developer terms Business resources Advertise X for business Resources and guides X for marketers Marketing insights Brand inspiration X Ads Academy © 2026 X Corp. Cookies Privacy Terms and conditions Did someone say … cookies? X and its partners use cookies to provide you with a better, safer and faster service and to support our business. Some cookies are necessary to use our services, improve our services, and make sure they work properly. Show more about your choices . Accept all cookies Refuse non-essential cookies | 2026-01-13T08:48:28 |
https://www.linkedin.com/signup/cold-join?session_redirect=https%3A%2F%2Fwww.linkedin.com%2Ffeed%2Fhashtag%2Fsoftwareeng&trk=organization_guest_main-feed-card-text | Sign Up | LinkedIn Join LinkedIn now — it’s free! Not you? Remove photo Join LinkedIn To create a LinkedIn account, you must understand how LinkedIn processes your personal information by selecting learn more for each item listed. Agree to all terms We collect and use personal information. Learn more We share personal information with third parties to provide our services. Learn more Further information is available in our Korea Privacy Addendum . Privacy Policy Addendum 1 of 2 2 of 2 Agree to the term Continue Back Agree to all terms Email Password Show First name Last name By clicking Agree & Join, you agree to the LinkedIn User Agreement , Privacy Policy , and Cookie Policy . Agree & Join or Security verification Already on LinkedIn? Sign in Looking to create a page for a business? Get help LinkedIn © 2026 About Accessibility User Agreement Privacy Policy Cookie Policy Copyright Policy Brand Policy Guest Controls Community Guidelines العربية (Arabic) বাংলা (Bangla) Čeština (Czech) Dansk (Danish) Deutsch (German) Ελληνικά (Greek) English (English) Español (Spanish) فارسی (Persian) Suomi (Finnish) Français (French) हिंदी (Hindi) Magyar (Hungarian) Bahasa Indonesia (Indonesian) Italiano (Italian) עברית (Hebrew) 日本語 (Japanese) 한국어 (Korean) मराठी (Marathi) Bahasa Malaysia (Malay) Nederlands (Dutch) Norsk (Norwegian) ਪੰਜਾਬੀ (Punjabi) Polski (Polish) Português (Portuguese) Română (Romanian) Русский (Russian) Svenska (Swedish) తెలుగు (Telugu) ภาษาไทย (Thai) Tagalog (Tagalog) Türkçe (Turkish) Українська (Ukrainian) Tiếng Việt (Vietnamese) 简体中文 (Chinese (Simplified)) 正體中文 (Chinese (Traditional)) Language Follow top companies Over 60% of the fortune 100 companies use LinkedIn to hire. Join now Leave | 2026-01-13T08:48:28 |
https://www.linkedin.com/signup/cold-join?session_redirect=https%3A%2F%2Fwww%2Elinkedin%2Ecom%2Fcompany%2Fdevcyclehq&trk=organization_guest_main-feed-card_share-cta | Sign Up | LinkedIn Join LinkedIn now — it’s free! Not you? Remove photo Join LinkedIn To create a LinkedIn account, you must understand how LinkedIn processes your personal information by selecting learn more for each item listed. Agree to all terms We collect and use personal information. Learn more We share personal information with third parties to provide our services. Learn more Further information is available in our Korea Privacy Addendum . Privacy Policy Addendum 1 of 2 2 of 2 Agree to the term Continue Back Agree to all terms Email Password Show Remember me First name Last name By clicking Agree & Join, you agree to the LinkedIn User Agreement , Privacy Policy , and Cookie Policy . Agree & Join or Security verification Already on LinkedIn? Sign in Looking to create a page for a business? Get help LinkedIn © 2026 About Accessibility User Agreement Privacy Policy Cookie Policy Copyright Policy Brand Policy Guest Controls Community Guidelines العربية (Arabic) বাংলা (Bangla) Čeština (Czech) Dansk (Danish) Deutsch (German) Ελληνικά (Greek) English (English) Español (Spanish) فارسی (Persian) Suomi (Finnish) Français (French) हिंदी (Hindi) Magyar (Hungarian) Bahasa Indonesia (Indonesian) Italiano (Italian) עברית (Hebrew) 日本語 (Japanese) 한국어 (Korean) मराठी (Marathi) Bahasa Malaysia (Malay) Nederlands (Dutch) Norsk (Norwegian) ਪੰਜਾਬੀ (Punjabi) Polski (Polish) Português (Portuguese) Română (Romanian) Русский (Russian) Svenska (Swedish) తెలుగు (Telugu) ภาษาไทย (Thai) Tagalog (Tagalog) Türkçe (Turkish) Українська (Ukrainian) Tiếng Việt (Vietnamese) 简体中文 (Chinese (Simplified)) 正體中文 (Chinese (Traditional)) Language | 2026-01-13T08:48:28 |
https://www.coursera.org/account/accomplishments/verify/XHXRQD3A274V?trk=public_profile_see-credential | Coursera | Online Courses & Credentials From Top Educators. Join for Free | Coursera For Individuals For Businesses For Universities For Governments Explore Degrees ​ Log In Join for Free Join for Free Course Certificate Convolutional Neural Networks Completed by Daniel Bourke January 16, 2018 35 hours (approximately) Daniel Bourke's account is verified. Coursera certifies their successful completion of Convolutional Neural Networks Convolutional Neural Networks DeepLearning.AI Filled Star Filled Star Filled Star Filled Star Filled Star 4.9 (42,561 ratings) | 560,734 already enrolled Enroll for Free Skills you will gain Computer Vision Deep Learning Image Analysis Tensorflow Keras (Neural Network Library) PyTorch (Machine Learning Library) Convolutional Neural Networks Transfer Learning Artificial Neural Networks Data Preprocessing Coursera Footer Skills Artificial Intelligence (AI) Cybersecurity Data Analytics Digital Marketing English Speaking Generative AI (GenAI) Microsoft Excel Microsoft Power BI Project Management Python Certificates & Programs Google Cybersecurity Certificate Google Data Analytics Certificate Google IT Support Certificate Google Project Management Certificate Google UX Design Certificate IBM Data Analyst Certificate IBM Data Science Certificate Machine Learning Certificate Microsoft Power BI Data Analyst Certificate UI / UX Design Certificate Industries & Careers Business Computer Science Data Science Education & Teaching Engineering Finance Healthcare Human Resources (HR) Information Technology (IT) Marketing Career Resources Career Aptitude Test Examples of Strengths and Weaknesses for Job Interviews High-Income Skills to Learn How Does Cryptocurrency Work? How to Highlight Duplicates in Google Sheets How to Learn Artificial Intelligence Popular Cybersecurity Certifications Preparing for the PMP Certification Signs You Will Get the Job After an Interview What Is Artificial Intelligence? Coursera About What We Offer Leadership Careers Catalog Coursera Plus Professional Certificates MasterTrack® Certificates Degrees For Enterprise For Government For Campus Become a Partner Social Impact Free Courses Share your Coursera learning story Community Learners Partners Beta Testers Blog The Coursera Podcast Tech Blog More Press Investors Terms Privacy Help Accessibility Contact Articles Directory Affiliates Modern Slavery Statement Cookies Preference Center Learn Anywhere © 2026 Coursera Inc. All rights reserved. | 2026-01-13T08:48:28 |
https://stackoverflow.blog/2026/01/02/a-new-worst-coder-has-entered-the-chat-vibe-coding-without-code-knowledge/ | A new worst coder has entered the chat: vibe coding without code knowledge - Stack Overflow Blog Loading… Everything Productivity AI/ML Open Source Business Hub Company Releases Podcast Newsletter Stack Overflow Business Stack Internal : the knowledge intelligence layer that powers enterprise AI. Stack Data Licensing : decades of verified, technical knowledge to boost AI performance and trust. Stack Ads : engage developers where it matters — in their daily workflow. January 2, 2026 A new worst coder has entered the chat: vibe coding without code knowledge In the age of AI, being able to make applications and create code has never been easier. But is it any good? Here's what vibe coding is like for someone without technical skills. [Ed. note: While we take some time to rest up over the holidays and prepare for next year, we are re-publishing our top ten posts for the year. Please enjoy our favorite work this year and we’ll see you in 2026.] If I asked you to guess the job title of someone coding an app for work, your first guess probably wouldn’t be “writer”. It probably wouldn’t be your second or fifth guess either. The fact I wouldn’t be the first person you think of doesn’t offend me. None of my resumes have ever listed coding expertise as a skill. Most of what I know I picked up through work, which necessitates an understanding of technical language and an interest in programming trends. A little of what I know is osmosis from living in the Bay Area, where tech conversations are unavoidable for anyone with a social life. But life is full of little surprises, and one of those is that I did in fact create an app for work. I’ll add an unsurprising caveat: I didn’t actually code it—instead it was created completely through vibes, doing what a lot of code curious folks are doing with vibe coding apps like Bolt. Is vibe coding as powerful as it seems? “ Vibe coding ” as a concept only emerged in early 2025, but it’s already one of the most talked-about usages of large language models. It’s sparked a lot of debate on its effectiveness as a tool for coding and a lot of anxiety over how it will change the tech landscape, especially for junior developers . Even for experienced developers, it holds the existential threat of imposter syndrome , and past that complete replacement. The promise that vibe coding will give anyone, even those with a nontechnical background, the power to create their own usable applications is also debatable. I can say that from my own experience. It felt like hitting one of those “That was easy!” buttons from Staples. But it was too easy, and immediately upon handing the output over to someone with more technical expertise than me, the holes began to show. While it may be a powerful tool in the hands of someone who knows what they’re doing, in my hands it was like one of those AI filters that makes you look like a Studio Ghibli character: fun to post, but not actually substantive. Creating the “Do Not Go In There” app I created my “app” as part of Bolt’s Hackathon . In collaboration with Reddit, the contest prompt was to create something silly that was irreverent and overall useless. I often have useless ideas, so it was perfect for me. “It’s like Yelp but for bathrooms. And it’s for the worst bathrooms in the world,” I told my mom. “Uh, what do you do for work again?” she replied. The process for getting started was fairly easy. Or, it should have been fairly easy. For someone who doesn’t know where the terminal is on her computer, it was not. Devpost, the hosts of the contest, touted that it would take me less than one minute to start building my application with Bolt. They had provided several resources for me to look through, including links to Reddit’s Developer Quickstart. I ended up sinking a lot of time into that particular resource because I didn’t know what I was doing. I’ll take this time to formally apologize to the Help Desk at Stack Overflow for trying to download node . js onto my work laptop even though I definitely didn’t need it. When I figured out that Bolt could do everything I needed, it became much easier. That is a true statement, by the way. Bolt can create a simple app end-to-end almost seamlessly, as long as the person doing it has a rudimentary knowledge of code or clear instructions on what to run. I fell into the second category; I didn’t have a clue about what commands I would need to make the program work until I read one of the Devpost resources. Whether the app would be any good was what I would find out. Bolt’s interface is sleek and intuitive, with a live preview of your creation on the side. It also allows you to look through your codebase and manually update lines as needed. For my purposes, I used the natural language prompt box, which came with some tips for efficient prompt engineering. I used none of them. My prompt was simply, “Create an app for Reddit that’s like Yelp but for bad bathrooms.” (Come on, it’s a joke app for bathrooms; I don’t have to be an eloquent prompt engineer.) My friendly vibe coding AI immediately started working, creating folders to dump code into. All in all, it took about ten minutes to create the foundation of what I had asked for. The app was launchable on my tester subreddit, including a slightly silly UI that used a toilet emoji. It had a place to leave reviews, a rating scale, and a page that would populate with reviews as people wrote them. All of these things were automatically created in a lovely little UI I could click around in on my tester Subreddit. It also didn’t work at all. Almost immediately, error messages popped up in both my Bolt interface and the app itself. No matter how much I tried, I couldn’t upload a bathroom review. I got several error messages in scary red text telling me that location services weren’t available and that I wouldn’t be able to upload a review. Although it had hardly been any work on my end, I did feel the sting of defeat. So I told my Bolt AI, “The app doesn’t work.” What came was about 45 minutes of troubleshooting, where the AI told me exactly where to find error messages. I didn’t have to understand any of them myself; I just had to paste them into the dialogue box verbatim, unformatted, and Bolt would deal with the issue. And while Bolt did provide me with information on what it had fixed, it wasn’t useful to me as a non-coder, who didn’t know what it meant when API endpoints were not being served at the root level. I’m sure if I had any understanding of what exactly was happening inside my app, I could ask it to dig deeper, but the whole point of this experiment was that I didn’t . My lack of understanding went beyond the codebase and to some of the basics of testing and working with my app. For instance, I didn’t realize the `npm run dev` command would update the existing tester app in my tester subreddit. I thought I had to relaunch and repost the app every time edits were made to test a new “version” of the app. In my head, each version of the app was its own respective entity, as opposed to an evolving application that would update itself. Because of this, my tester subreddit had 20 posts on it by the time I had an actual working toilet app. But Bolt was a powerful helper. I cannot overstate how lost I was in the process of creating this application and how easy Bolt made it for me to make something. It even helped me make simple changes to the interface, allowing me to play with the design in a way that was more comfortable for me as someone with a graphic design background. Eventually, I made something that worked, with the use of the word “I” being loose. Really, Bolt had created something; all I had done was give it a prompt and feed it error messages when it asked me to. With each iteration of the application, more and more started to work. I was able to input information, look through reviews, and even add little flourishes like a Bolt badge and different review options. But even with the app live and working , was it any good? Sharing the fruits of my non-labor I felt I had fulfilled the challenge posed by the hackathon competition: I had created something silly, irreverent, and totally useless. Immediately, my coworkers started inputting some of their least favorite bathrooms. It was a ball, for sure. When I met with Ryan Donovan , who you definitely know if you’ve ever listened to our podcast or read anything on the blog, to review my app, the holes started showing immediately. To start with, he was pleasantly [ Ed. note: I don’t know if “pleasantly” is the right word here ] surprised by how many technologies were being used in my simple app. He asked if I knew what JSON or Redis were, as they were both formats being used to run my toilet application. My answer was a resounding no. Ryan didn’t even need to look at my actual code to find issues. He could find glaring ones just from visiting my testing Subreddit and hitting the inspect feature. He let me know right away that my application was ripe for hacking, as there were no security features present to stop someone from accessing any of the data it was storing. This is obviously a big deal, but I’ll get back to it later. As part of my edification, Ryan suggested I get feedback on the code itself. He mentioned posting it publicly to GitHub and asking the community to give me feedback, but as I started to understand just how bad what I had created was, I shied away from the idea of a public lashing. It wasn’t that I was afraid to kill my darling; in fact, there was no darling to be killed. It was more of a simmering feeling of dread, the kind one gets when they know they didn’t do their homework very well and are afraid of what the teacher will say. Luckily, I live in the Bay Area, which means almost all my friends are developers. So before I let strangers play around in my code, I turned to them. It was a cowardly move, because the added layer of context meant that my friends would go easy on me, knowing that my creation was vibe coded and that I probably didn’t understand any of the feedback they were giving me. The main piece of feedback from my friends was that the code was messy and nearly impossible to understand. I intentionally gave them little context on what was being built, instead letting the ` .readme ` that Bolt created for my project speak for itself. The lack of organization started there, mainly because I have no experience using GitHub. “You have a nice readme, but for some reason you buried everything inside ` ./project` ,” one of my friends, a software engineer in Palo Alto, wrote. “Would you consider putting all that stuff in the top level, so people can see everything automatically when they visit your repo?” Another friend wrote, “All the styling is inlined into the ` tsx ` components, which makes it much more cluttered/hard to read.” I didn’t know if that meant I had done something wrong in my GitHub upload or if the code itself was the issue. Her overarching piece of feedback was that the code wasn’t created in a way that facilitated feedback or understanding: “For example, the block of code that is returned from ` LocationDetails.tsx ` is huge. I would split it into several smaller components.” Then at the end she added, “There are no unit tests .” I took this to mean that she couldn’t understand if the components of what I had created even made sense, or could exist on their own. That, I thought to myself, was probably not good. An unmet promise A clear disconnect then stood out to me between the vibe coding of this app and the actual practiced work of coding. Because this app existed solely as an experiment for myself, the fact that it didn’t work so well and the code wasn’t great didn’t really matter. But vibe coding isn’t being touted as “a great use of AI if you’re just mucking about and don’t really care.” It’s supposed to be a tool for developer productivity, a bridge for nontechnical people into development, and someday a replacement for junior developers. That was the promise. And, sure, if I wanted to, I could probably take the feedback from my software engineer pals and plug it into Bolt. One of my friends recommended adding “descriptive class names” to help with the readability, and it took almost no time for Bolt to update the code. It even had an innate understanding of why I might want to add descriptive classnames, something I wouldn’t have understood unless my friend had explained it to me. But what if I wasn’t someone with developer friends? What if the project I was working on wasn’t just for the fun of it but instead something I was really passionate about, or even wanted to bring to market? The mess of my code would be a problem in any of those situations. Even though I made something that worked , did it really? Had this been a real work project, a developer would have had to come in after the fact to clean up everything I had made, lest future developers be lost in the mayhem of my creation. This is called the “ productivity tax ,” the biggest frustration that developers have with AI tools, because they spit out code that is almost—but not quite—right. Our Developer Survey found that 66% of developers experience this tax when they use these coding tools. But even if we weren’t to worry about my good buddies down at engineering, there is an even bigger problem: security. I want to touch back on the point that Ryan made about none of the data being protected on my silly toilet app. Luckily, in this case at least, no data of importance is being shared or stored on my application. But there are many instances where this would not be the case. Because these tools are promising powerful results without the need for developer experience, there are probably a lot of people without experience who will use something like Bolt to create their passion projects. And probably a lot of these passion projects will be well-meaning, and will work, on the front end at least. And maybe some of these programs will ask for information like ZIP code, or email address, or date of birth, or to even create a password. You can probably see where I’m going here; GDPR can too. It does seem unlikely that something that’s going to be pushed to market would go live without having someone with a development background look at it, but what of the fun side projects like mine? I could easily imagine an evil world where someone vibe codes something for their loved ones that includes identifying information about the people in their lives, and that falls into the hands of malicious folks who know how to use the inspect function. Was what Bolt created good enough for my purposes? Sure. And with the help of a few knowledgeable friends and coworkers, could I have fixed the issues I had with security and organization without ever having to learn a single command? Yes, definitely. But for a technology that is supposedly going to make junior developers obsolete, it needed a lot of help from my friends—all of whom are junior developers. On the other side of this story, I want to share something about one of my best friends who also regularly vibe codes. He’s a theoretical physicist with a doctorate from Stanford. He had wanted to remain in research after finishing his PhD, but found the opportunities slim and the pay even slimmer because of the current state of higher education. So he pivoted, pretty hard, into a role that meant he had to learn how to code quickly. He shared with me that LLMs had increased his learning capabilities ten-fold because they allowed him to find information fast. He talked about his mish-mashed usage of CoPilot, Gemini, and ChatGPT almost like it was a fond tutor of his, referencing times when he couldn’t figure out a bug and so had Gemini explain it to him. This, he told me, helped him the next time he experienced a similar bug. This, I think, is the real promise of vibe coding tools—that you can learn how to code without a CS degree. There is no one in the world who would say my friend isn’t intelligent enough to code, but the issue was that he had no experience. And after five years in the Stanford physics department, there was no way he was going back for another degree. Vibe coding tools were giving him the support and knowledge he needed, so he could learn these skills himself. Like anything in the wild west that is this age of AI, it all depends on how you use it. To take a page from my friend, I want my vibe coding experience to be the first step in me learning how to code. So, I’m offering up my vibe code for feedback, criticism, and tips from the community. Let me know what you think of my GitHub, and what you think I should do next to stop being the worst coder in the world. Author s Phoebe Sajor Content Associate Staff vibe coding ai coding generative AI worst coder in the world Recent articles January 12, 2026 Now everyone can chat on Stack Overflow January 5, 2026 What’s new at Stack Overflow: January 2026 January 1, 2026 Documents: The architect’s programming language December 31, 2025 A look under the hood: How (and why) we built Question Assistant Latest Podcast January 13, 2026 Vibe code anything in a Hanselminute Add to the discussion Login with your stackoverflow.com account to take part in the discussion. Our Stack Stack Internal Features Customers Security Pricing Stack Data Licensing Stack Ads Partnerships Services Stack Overflow Company Leadership Press Careers Social Impact Support Contact Stack Overflow help Stack Internal help Terms Privacy policy Cookie policy Your Privacy Choices Elsewhere Blog Dev Newsletter Podcast Releases Dev Survey Site design / logo © 2026 Stack Exchange Inc. Light Dark Auto | 2026-01-13T08:48:28 |
https://developer.x.com/developer-terms/policy#3-c | Developer Policy – X Developers | X Developer Platform <g> <g> <defs> <rect id="SVGID_1_" x="-468" y="-1360" width="1440" height="3027" /> </defs> <clippath id="SVGID_2_"> <use xlink:href="#SVGID_1_" style="overflow:visible;" /> </clippath> </g> </g> <rect x="-468" y="-1360" class="st0" width="1440" height="3027" style="fill:rgb(0,0,0,0);stroke-width:3;stroke:rgb(0,0,0)" /> <path d="M13.4,12l5.8-5.8c0.4-0.4,0.4-1,0-1.4c-0.4-0.4-1-0.4-1.4,0L12,10.6L6.2,4.8c-0.4-0.4-1-0.4-1.4,0c-0.4,0.4-0.4,1,0,1.4 l5.8,5.8l-5.8,5.8c-0.4,0.4-0.4,1,0,1.4c0.2,0.2,0.4,0.3,0.7,0.3s0.5-0.1,0.7-0.3l5.8-5.8l5.8,5.8c0.2,0.2,0.5,0.3,0.7,0.3 s0.5-0.1,0.7-0.3c0.4-0.4,0.4-1,0-1.4L13.4,12z" /> </svg>" data-icon-chevron-right="<svg xmlns="http://www.w3.org/2000/svg" width="24" height="24" viewbox="0 0 24 24" aria-hidden="true" focusable="false" role="none" class="twtr-icon"> <path opacity="0" d="M0 0h24v24H0z" /> <path d="M17.207 11.293l-7.5-7.5c-.39-.39-1.023-.39-1.414 0s-.39 1.023 0 1.414L15.086 12l-6.793 6.793c-.39.39-.39 1.023 0 1.414.195.195.45.293.707.293s.512-.098.707-.293l7.5-7.5c.39-.39.39-1.023 0-1.414z" /> </svg>" data-icon-chevron-down="<svg xmlns="http://www.w3.org/2000/svg" width="24" height="24" viewbox="0 0 24 24" aria-hidden="true" focusable="false" role="none" class="twtr-icon"> <path opacity="0" d="M0 0h24v24H0z" /> <path d="M20.207 7.043c-.39-.39-1.023-.39-1.414 0L12 13.836 5.207 7.043c-.39-.39-1.023-.39-1.414 0s-.39 1.023 0 1.414l7.5 7.5c.195.195.45.293.707.293s.512-.098.707-.293l7.5-7.5c.39-.39.39-1.023 0-1.414z" /> </svg>" data-icon-arrow-left="<svg width="28px" height="28px" viewbox="0 0 28 28" version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" aria-hidden="true" focusable="false" role="none" class="twtr-icon u01-meganav__icon-arrow-left"> <g stroke="none" stroke-width="1" fill="none" fill-rule="evenodd" stroke-linecap="round"> <g transform="translate(-1216.000000, -298.000000)" stroke-width="2.25"> <g transform="translate(1200.000000, 282.000000)"> <g transform="translate(17.000000, 17.000000)"> <path d="M0.756410256,12.8589744 L25.7179487,12.8589744"></path> <path d="M13.2371795,25.3397436 L25.7179487,12.8589744"></path> <path d="M13.2371795,12.4807692 L25.3397436,0.378205128" transform="translate(19.288462, 6.429487) rotate(-90.000000) translate(-19.288462, -6.429487) "></path> </g> </g> </g> </g> </svg>" data-left-nav-items="[{"isActive":false,"hasActiveChild":false,"children":[{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"X API","linkDisabled":false,"title":"X API","path":"https://developer.x.com/en/products/twitter-api"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"X Ads API","linkDisabled":false,"title":"X Ads API","path":"https://developer.x.com/en/products/x-ads-api"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"X for websites","linkDisabled":false,"title":"X for websites","path":"https://developer.x.com/en/products/x-for-websites"}],"overviewTitle":"Products","linkDisabled":true,"title":"Products","path":"https://developer.x.com/en/products"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Docs","linkDisabled":false,"title":"Docs","path":"https://docs.x.com/"},{"isActive":false,"hasActiveChild":false,"children":[{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Build for business","linkDisabled":false,"title":"Build for business","path":"https://developer.x.com/en/use-cases/build-for-businesses"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Build for the public","linkDisabled":false,"title":"Build for the public","path":"https://developer.x.com/en/use-cases/build-for-consumers"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Do research","linkDisabled":false,"title":"Do research","path":"https://developer.x.com/en/use-cases/do-research"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Teach \u0026 learn","linkDisabled":false,"title":"Teach \u0026 learn","path":"https://developer.x.com/en/use-cases/teach-and-learn"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Build for good","linkDisabled":false,"title":"Build for good","path":"https://developer.x.com/en/use-cases/build-for-good"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Build for fun","linkDisabled":false,"title":"Build for fun","path":"https://developer.x.com/en/use-cases/build-for-fun"}],"overviewTitle":"Use Cases","linkDisabled":true,"title":"Use Cases","path":"https://developer.x.com/en/navigation/left-nav-items/use-cases"},{"isActive":false,"hasActiveChild":false,"children":[{"isActive":false,"hasActiveChild":false,"children":[{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Changelog","linkDisabled":false,"title":"Changelog","path":"https://docs.x.com/updates/changelog"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Blog","linkDisabled":false,"title":"Blog","path":"https://developer.x.com/en/blog"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Newsletter","linkDisabled":false,"title":"Newsletter","path":"https://developer.x.com/en/updates/stay-informed"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"YouTube","linkDisabled":false,"title":"YouTube","path":"https://www.youtube.com/c/twitterdev"}],"linkDisabled":true,"title":"Stay informed","path":"https://developer.x.com/"},{"isActive":false,"hasActiveChild":false,"children":[{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Forums","linkDisabled":false,"title":"Forums","path":"https://twittercommunity.com/"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Events","linkDisabled":false,"title":"Events","path":"https://twitterdev.bevylabs.com/"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Insiders","linkDisabled":false,"title":"Insiders","path":"https://developer.twitter.com/en/community/insiders"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Community leaders","linkDisabled":false,"title":"Community leaders","path":"https://developer.x.com/en/community/leaders"}],"linkDisabled":true,"title":"Connect","path":"https://developer.x.com/"}],"overviewTitle":"Community","linkDisabled":false,"menuType":"multiCategory","title":"Community","path":"https://developer.x.com/en/community"}]" data-right-nav-items="[{"isActive":false,"hasActiveChild":false,"children":[{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Policies","linkDisabled":false,"title":"Policies","path":"https://developer.x.com/en/developer-terms"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Developer agreement","linkDisabled":false,"title":"Developer agreement","path":"https://developer.x.com/en/developer-terms/agreement-and-policy/source"}],"overviewTitle":"Support","linkDisabled":false,"title":"Support","path":"https://developer.x.com/en/support"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Developer Portal","linkDisabled":false,"title":"Developer Portal","path":"https://developer.twitter.com/en/portal/petition/essential/basic-info"}]" data-cta-enabled="true" data-profile-enabled="true" data-cta-link-new-tab="false" data-root-page-title="Developer Platform"> Developer terms Developer Policy Let's get started X + Developers Using this policy X + Developers Using this policy X + Developers X loves developers. We’re delighted and amazed by the tools and services this community creates by harnessing the power of X data. As part of our commitment to this community, we aim to provide data access that is open and fair for developers, safe for people on X, and beneficial for the X platform as a whole. To further these goals we’ve crafted the Developer Policy as a guide to help people understand our rules and expectations about appropriate API and X Content usage. This Developer Policy (“ Policy ”) provides rules and guidelines for developers who interact with X’s ecosystem of applications, services, website, web pages and content. It is part of your contract with X governing access to and use of the X API and X Content (either as part of the Developer Agreement or other written agreement with X). Policy violations are considered violations of your agreement. This Policy may be changed from time to time without notice. Capitalized terms used in this Policy, which are not defined in this Policy, will have the respective meanings ascribed to them in the Developer Agreement or the Master License Agreement. Using this policy We’ve structured this policy to make it as easy to follow as possible. Please keep information from the following policy sections top of mind as you use the X API and X Content: 1. Set Yourself Up for Success - You are responsible for complying with all X policies. It’s important that you review and understand this Policy, as well as the policies we link to in this document, before you access the X API and X Content. The time spent reviewing our policies may save you hours of rework down the road. 2. Privacy and Control are Essential - Protecting and defending the privacy of people on X is built into the core DNA of our company. As such, we prohibit the use of X data in any way that would be inconsistent with people’s reasonable expectations of privacy. By building on the X API or accessing X Content, you have a special role to play in safeguarding this commitment, most importantly by respecting people’s privacy and providing them with transparency and control over how their data is used. 3. Follow the Platform Usage Guidelines - Getting approved to access the X API and X Content is just the first step. Our Platform Usage Guidelines should be your first stop anytime you have questions about how to ensure policy compliance for your planned use of the X platform. We’ve provided a lot more detail on what each of these three key sections mean below. Please review them carefully to ensure that your usage of the X API and X Content is consistent with our policies. If we believe you are in violation of this Policy (or any other X policy), we may suspend or permanently revoke your access to the X API and X Content. Finally, please note that X may monitor your use of the X API to improve the X Applications, to examine any commercial use, and to ensure your compliance with your approved use case and this Policy. Thanks for reading, and thank you for building with us! We look forward to seeing what you create! Chapter 1 Set yourself up for success Set yourself up for success Set yourself up for success Set yourself up for success You can avoid many potential pitfalls while using the X API by ensuring that your service has been built the right way from day 1. This section of the Developer Policy contains rules that all developers must follow before using the X API or X Content. The Free, Basic, and Pro plans (as described at developer.x.com/en ) are designed for hobbyists, commercial prototyping, early-stage X product integrations, and supporting applications with limited end-users. If you use the X API and X Content beyond this scope, then you must apply (or already subscribe to) an Enterprise plan (as described at developer.x.com/en ). We review all proposed uses of the X developer platform to verify policy compliance — so you’re required to disclose (and update, as applicable) your planned use of the X API and X Content in order to be granted and to maintain access. All new developers must apply for a developer account to access the X API. Current developers without an approved developer account must apply for one as directed to do so by X. As part of this process, you’ll need to provide us with a written description of your intended uses of the X API and X Content. Your use case description is binding on you, and any substantive deviation from it may constitute a violation of our rules and result in enforcement action. You must notify us of any substantive modification to your use case and receive approval before you may begin using X Content for that new purpose. Failure to do so may result in suspension and termination of your API and data access. By building on the X API or accessing X Content, you must comply with ALL X policies. These include this Developer Policy , the Automation Rules , the Display Requirements , the API Restricted Uses Rules , the X Rules , and the X Brand Resources , as well as any other agreements you enter into with X relating to your use of the X API or X Content, including but not limited to the Developer Agreement or a Master Licensing Agreement or Order (as applicable). You must also comply with any modifications to these policies and any new policies launched by X. It is your responsibility to monitor the use of your service and to design your service to prevent violations of X policy by people who use it. Failure to do so may result in suspension or termination of your API and X Content access. You may not register multiple applications for a single use case or substantially similar or overlapping use cases. In this context, a “use case” is a consistent set of analyses, displays, or actions performed via an application. "White label" versions of a tool or service are not permissible. If you plan to “white label” versions of your application, you must notify and receive separate approval from us. As a single exception to these rules, you may create and use a maximum of 3 applications for development, staging, and production instances of the same service. These apps must be registered to a single account, and should be clearly identified (in the name and description) as dev, staging, and prod instances of a single service. You may not use development or staging applications for production purposes. You must keep all API keys or other access credentials private. You may not use, and may not encourage or facilitate others to use, API keys or other access credentials owned by others. Your license agreement with X limits your use of the X API and X Content. Among other things, the X API has rate limits which help to ensure fair data usage and to combat spam on the platform. You may not exceed or circumvent rate limits, or any other limitations or restrictions described in this Policy or your agreement with X, listed on the Developer Site , or communicated to you by X. You may not remove or alter any proprietary notices or marks on X Content received via the X API. This helps to make sure that people know where X Content is coming from, and who it belongs to. For data integrity and platform health reasons, you may not interfere with, intercept, disrupt, or disable any features of the X API or the X service. In other words, use the APIs as intended and documented on developer.x.com . Refer to our HackerOne guidelines for more details about acceptable use. Chapter 2 Privacy and control are essential Privacy and control are essential Consent & permissions Content compliance Off-X matching Your privacy policy Using geo-data X passwords Privacy and control are essential Consent & permissions Content compliance Off-X matching Your privacy policy Using geo-data X passwords Privacy and control are essential X takes privacy seriously, and we expect everyone using X Content and the X API to do the same. Any use of the X developer platform, X API, or X Content in a manner that is inconsistent with peoples’ reasonable expectations of privacy may be subject to enforcement action, which can include suspension and termination of API and X Content access. Your commitment to privacy and control must extend to all uses of X Content and all aspects of the service that you build using our API. To that end, the people using your service must understand and consent to how you use their data, and how you access X on their behalf. This can be accomplished through providing people with a clear, comprehensive, and transparent privacy policy, as well as ensuring that you get express and informed consent from each person using your service before taking any action on their behalf. Please note that a person authenticating into your service does not by itself constitute consent. Consent & permissions In particular, you must get express and informed consent from people before doing any of the following: Taking any actions on their behalf. This includes (but is not limited to): Posting content to X Following/unfollowing accounts Modifying profile or account information Adding hashtags or any other content to Posts Republishing content accessed by means other than via the X API or other X tools Using someone’s X Content to promote a product or service Storing non-public content such as Direct Messages (DMs), or any other private or confidential information Sharing or publishing protected content, or any other private or confidential information If your service allows people to post content to X you must do the following before publishing: Show exactly what will be published Make it clear to people using your service what geo information (if any) will be added to the content If your service allows people to post content to both your service and X, you must do the following before publishing: Obtain permission to post the content Explain where you will post the content You must respect the protected and blocked status of all X Content. You may not serve content obtained using one person’s authentication token to a different person who is not authorized to view that content. Protected accounts: A protected account ’s content is only available to people who have been approved by the owner to follow that account. So, if you run a service that accesses protected accounts, you may only do so to serve such content to the specific people with permission to view that content. Blocked accounts: People on X are able to block access to their accounts for any reason they choose. Commingling information obtained from tokens (or any other API-based action) to bypass this choice is not permitted. As Direct Messages (DMs) are non-public in nature, services that provide DM features must take extra steps to safeguard personal privacy. You may not serve DM content to people who are not authorized to view that content. If your service provides DM functionality you must also: Notify people if you send read receipt events for DMs. You can do this by providing a notice directly in your service, or by displaying read receipts from other participants in a conversation. Get consent before configuring media to be sent in a DM as "shared" (i.e. reusable across multiple DMs). If you do allow media in a DM to be “shared,” you must provide a clear notice that this content will be accessible to anyone with the media’s URL. Content compliance If you store X Content offline, you must keep it up to date with the current state of that content on X. Specifically, you must delete or modify any content you have if it is deleted or modified on X. This must be done as soon as reasonably possible, or within 24 hours after receiving a request to do so by X or the applicable X account owner, or as otherwise required by your agreement with X or applicable law. This must be done unless otherwise prohibited by law, and only then with the express written permission of X. Modified content can take various forms. This includes (but is not limited to): Content that has been made private or gained protected status Content that has been suspended from the platform Content that has had geotags removed from it Content that has been withheld or removed from X Off-X matching We limit the circumstances under which you may match a person on X to information obtained or stored off-X. Off-X matching involves associating X Content, including a X @handle or user ID, with a person, household, device, browser, or other off-X identifier. You may only do this if you have express opt-in consent from the person before making the association, or as described below. In situations in which you don’t have a person’s express, opt-in consent to link their Xidentity to an off-X identifier, we require that any connection you draw be based only on information that someone would reasonably expect to be used for that purpose. In addition, absent a person’s express opt-in consent you may only attempt to match your records about someone to a X identity based on: Information provided directly to you by the person. Note that records about individuals with whom you have no prior relationship, including data about individuals obtained from third parties, do not meet this standard; and/or Public data. “Public data” in this context refers to: Information about a person that you obtained from a public, generally-available resource (such as a directory of members of a professional association) Information on X about a person that is publicly available, including: Posts Profile information, including an account bio and publicly-stated location Display name and @handle Your privacy policy You must display your service’s privacy policy to people before they are permitted to download, install, or sign up to your service. It must disclose at least the following information: The information that you collect from people who use your service How you use and share that information (including with X) How people can contact you with inquiries and requests regarding their information Your privacy policy must be consistent with all applicable laws, and be no less protective of people than X’s Privacy Policy and the privacy policy of our other services and corporate affiliates . You must cease your access to the X API and the use of all X Content if you are unable to comply with your and/or X’s Privacy Policy. Using geo-data Use of geo data comes with additional restrictions due to the sensitive nature of this information. If your service adds location information to Posts, you must disclose to people: When you add location information Whether you add location information as a geotag or annotations data Whether your location information is listed as a place, or as geographic coordinates If your application allows people to post with their location you must comply with X’s geo guidelines in full. Any use of location data or geographic information on a standalone basis is prohibited. You may not (and may not permit others to) store, aggregate, or cache location data and other geographic information contained in X Content, except as part of a Post. For example, you may not separate location data or geographic information out from Posts to show where individuals have been over time. Heat maps and related tools that show aggregated geo activity (e.g., the number of people in a city using a hashtag) are permitted. X passwords You may not store X passwords, or request that people provide their X password, account credentials, or developer application information (including consumer key) to you directly. We suggest the use of Sign-in with X as the authentication tool to link your service and people on X. Chapter 3 Platform usage guidelines Platform usage guidelines Spam, bots, and automation X performance benchmarking Public display of Posts Content redistribution Pay to engage Service authenticy X name, logo, and likeness Advertising on X Platform usage guidelines Spam, bots, and automation X performance benchmarking Public display of Posts Content redistribution Pay to engage Service authenticy X name, logo, and likeness Advertising on X Platform usage guidelines Have you taken care to review X’s policies and set up your API access the right way? Does your service follow X’s privacy and control guidelines? If you can answer yes to these two questions, then you are ready to start using the X API and X Content. X’s Platform Usage Guidelines provide the assistance needed to ensure that your use of X Content is compliant from day 1 throughout the lifecycle of your service. We suggest reviewing these rules on a regular basis to make sure that your integration is operating in a way that is safe and beneficial to people on X and the X platform as a whole. Spam, bots, and automation The use of the X API and developer products to create spam, or engage in any form of platform manipulation, is prohibited. You should review the X Rules on platform manipulation and spam , and ensure that your service does not, and does not enable people to, violate our policies. Services that perform write actions, including posting Posts, following accounts, or sending Direct Messages, must follow the Automation Rules . In particular, you should: Always get explicit consent before sending people automated replies or Direct Messages Immediately respect requests to opt-out of being contacted by you Never perform bulk, aggressive, or spammy actions, including bulk following Never post identical or substantially similar content across multiple accounts If you’re operating an API-based bot account you must clearly indicate what the account is and who is responsible for it. You should never mislead or confuse people about whether your account is or is not a bot. A good way to do this is by including a statement that the account is a bot in the profile bio. X performance benchmarking You may not use the X API to measure the availability, performance, functionality, or usage of X for benchmarking, competitive, or commercial purposes. For example, you should never use the X API to: Calculate aggregate X metrics, such as the total number of Monthly Actives (MAs) or Daily Actives (DAs) Calculate aggregate X Post metrics, such as the total number of Posts posted per day, or the number of account engagements Measure or analyze the responsiveness of X Measure or analyze spam or security on X, except as permitted below We support research that helps improve conversational health on X. You may not publicly disclose any research or findings concerning, or develop, create, or offer services using, the X API or X Content that measure, analyze, or attempt to identify behaviors or content which violate X policies without express written permission from X. DSA Researchers: If you need to contact X relating to access under Art. 40 of the Digital Services Act, please contact EU-Questions@X.com . If you wish to apply for researcher access, please submit an application . Public display of Posts You must maintain the integrity of all X Content that you display publicly or to people who use your service. If you don’t use X for Websites to display content, then you must use the X API to retrieve the most current version available for display. If displayed content ceases to be available through the X API, then you must remove it from your service as soon as reasonably possible, or within 24 hours after the receipt of a removal request from X, or the applicable X account owner, or as otherwise required by applicable law. There are specific rules you must follow if you display X Content offline. Follow the guidelines for using Posts in broadcast if you display Posts offline. If you embed or display Posts, you must contact us about your X API access if your site exceeds 10 million daily impressions. X reserves the right to require additional terms as a condition to your use of the X API. Additional restrictions on X for Websites developer use include: Embedded Posts and/or embedded timelines You must provide people with legally sufficient notice that fully discloses X’s collection and use of data about browsing activities on your website, including for interest-based advertising and personalization. You must also obtain legally sufficient consent from people for such collection and use You must provide legally sufficient instructions on how people can opt out of X’s interest-based advertising and personalization as described here X for Websites widgets You must ensure that people are provided with clear and comprehensive information about, and consent to, the storing and accessing of cookies or other information on their devices as described in X’s cookie use , where providing such information and obtaining such consent is required by law Services targeted to children under 13 Services targeted to children under 13 must opt out of tailoring X in any embedded Post and/or embedded timelines by setting the opt-out parameter to be ‘true’ as described here Content redistribution The best place to get X Content is directly from X. Consequently, we restrict the redistribution of X Content to third parties. If you provide X Content to third parties, including downloadable datasets or via an API, you may only distribute Post IDs, Direct Message IDs, and/or User IDs (except as described below). In total, you may not distribute more than 1,500,000 Post IDs to any entity (inclusive of multiple individuals associated with a single entity) within any 30 day period unless you have received written permission from X. In addition, developers may provide up to 500 public Posts Objects and/or User Objects to each person who uses your service on a daily basis if this is done via non-automated means (e.g., download of spreadsheets or PDFs). Academic researchers are permitted to distribute Post IDs and/or User IDs solely for the purposes of non-commercial research on behalf of an academic institution, and that has been approved by X in writing, or peer review or validation of such research. Only as many Post IDs or User IDs that is necessary for such research, and has been approved by X may be used. Any X Content provided to third parties remains subject to this Policy, and those third parties must agree to the X Terms of Service , Privacy Policy , Developer Agreement , and Developer Policy before receiving such downloads. You may not enable any entity to circumvent any other limitations or restrictions on the distribution of X Content as contained in this Policy , the Developer Agreement , or any other agreement with X. Note: This Section does not apply to researchers with X API access via Art. 40 of the EU Digital Services Act (2022) (“ DSA ”), who are instead subject to the procedures and restrictions set forth in the DSA and the Developer Agreement. Pay to engage Your service shouldn’t compensate people to take actions on X, as that results in inauthentic engagement that degrades the health of the platform. As you use the X API you may not sell or receive monetary or virtual compensation for any X actions. This includes, but is not limited to, Posts, follows, unfollows, reposts, likes, comments, and replies. Service authenticity You must clearly identify your service so that people can understand its source and purpose. Don’t use names, logos, or URLs that mask your service’s identity and features, or that falsely imply an affiliation with X or third parties. Note that creating applications for the purpose of selling names, or to prevent others from using names, is prohibited. You may not use any URL (including shortened URLs) for your service that directs people to: A site that is unrelated to your service A spam or malware site A site that encourages people to violate X policy X name, logo, and likeness You may only use and display the X name and logo to identify X as the source of X Content. You should never use the X name and logo, the X Official Partner Program badge, or any other similar marks or names in a manner that creates a false sense of endorsement, sponsorship, or association with X. The X Brand Resources contain detailed information to help you use the X brand in the right way. You may only use the X Verified Account badge and any other enhanced account categorization as it is reported to you by X through the API. This helps people know that the content your service displays is equivalent to that shown on X. Advertising on X There are restrictions regarding how and where you are allowed to advertise around X Content. To start, your advertisements can’t resemble or reasonably be confused by people as a Post. Other rules on advertising include: There must be a clear separation between X Content and your advertisements. You may not place any advertisements within the X timeline other than X Ads. X reserves the right to serve advertising via the X API. If you decide to serve X Ads once we start delivering them via the API, we will share a portion of advertising revenue with you in accordance with the relevant terms and conditions. You may not use X Content, or information obtained from the X API to target people with advertising outside of the X platform. Chapter 4 Rules for specific X services or features X login X Cards Definitions X login X Cards Definitions The following additional rules apply for any use of the X services or features listed below: X login You must present people with easy to find options to log into and out of X, for example via the OAuth protocol. The Sign in with X option must be displayed at least as prominently as any other sign-up or sign-in feature on your service. You must also provide people without a X account the opportunity to create one via X. Once someone on your service authenticates via Sign in with X you must clearly display their X identity. X identity includes the person’s current X @handle, avatar, and X logo. Any display of someone’s X followers on your service must clearly show that the relationship is associated with X. X Cards To ensure a quality experience you must develop your Card to render across all platforms where Cards are displayed. Additional rules that you must follow when using Cards include: You must mark your Post as ‘true’ for sensitive media if you plan to display such media within a Card You must use HTTPS for hosting all assets within your Card. Your Card should never generate active mixed content browser warnings Audio and video content should include stop or pause controls, and default to ‘sound off’ for videos that automatically play content You may not exceed or circumvent X’s limitations placed on any Cards, including the Card’s intended use. Additional restrictions on Cards use include: You may not place third-party sponsored content within Cards without X’s approval You may not attach monetary incentives (including virtual currency) within your Card or on X from your Card You may not include content or actions within your Card that are misleading or not contextually relevant, such as URLs and media You may only attach an App Card to a Post when someone is explicitly promoting or referring to the app in the Post Definitions X Content ‒ Posts, Post IDs, X end user profile information, and any other data and information made available to you through the X API or by any other means authorized by X, and any copies and derivative works thereof. Developer Site ‒ X’s developer site located at https://developer.x.com . Services ‒ Your websites, applications and other offerings that display X Content or otherwise use the Licensed Material as explicitly approved by X. Post ID ‒ A unique identification number generated for each Post. Post ‒ A posting made on X Applications. “X” ‒ Means (a) X Corp. (865 FM 1209, Building 2, Bastrop, TX 78602, USA) if your principal place of business is outside the European Union, EFTA States, and the United Kingdom; or (b) X Internet Unlimited Company (One Cumberland Place, Fenian Street, Dublin 2, D02 AX07, Ireland) if your principal place of business is in the European Union, EFTA States, or the United Kingdom. Direct Message - A message that is privately sent on X Applications by one end user to one or more specific end user(s) using X’s Direct Message function. X API ‒ The X Application Programming Interface (“API”), Software Development Kit (“SDK”) and/or the related documentation, data, code, and other materials provided by X with the API, as updated from time to time, including without limitation through the Developer Site. X Applications ‒ X’s consumer facing products, services, applications, websites, web pages, platforms, and other offerings, including without limitation, those offered via https://x.com and X's mobile applications. Developer policy and terms Follow @XDevelopers Subscribe to developer news X platform X.com Status Accessibility Embed a post Privacy Center Transparency Center Download the X app Try Grok.com X Corp. About the company Company news Brand toolkit Jobs and internships Investors Help Help Center Using X X for creators Ads Help Center Managing your account Email Preference Center Rules and policies Contact us Developer resources Developer home Documentation Forums Communities Developer blog Engineering blog Developer terms Business resources Advertise X for business Resources and guides X for marketers Marketing insights Brand inspiration X Ads Academy © 2026 X Corp. Cookies Privacy Terms and conditions Did someone say … cookies? X and its partners use cookies to provide you with a better, safer and faster service and to support our business. Some cookies are necessary to use our services, improve our services, and make sure they work properly. Show more about your choices . Accept all cookies Refuse non-essential cookies | 2026-01-13T08:48:28 |
https://www.linkedin.com/company/devcyclehq | DevCycle | LinkedIn Skip to main content LinkedIn Top Content People Learning Jobs Games Sign in Register now DevCycle Software Development Toronto, Ontario 1,008 followers A feature flag management platform built for developers 👩💻 🚩 | Part of the OpenFeature Ecosystem 🌎 Follow View all 21 employees Report this company About us A feature flag management platform built for developers 👩💻 🚩 | Part of the OpenFeature Ecosystem 🌎 Website https://devcycle.com External link for DevCycle Industry Software Development Company size 11-50 employees Headquarters Toronto, Ontario Type Privately Held Founded 2021 Specialties feature flags, feature management, and developer productivity Locations Primary 49 Spadina Ave Suite 304 Toronto, Ontario 55V 2J1, US Get directions Employees at DevCycle Mark Allen Bryan Clark Chris Aniszczyk Julia Gilinets See all employees Updates DevCycle 1,008 followers 3w Report this post 🧑💻 Engineering managers: 😬 If every deploy makes your team nervous, the problem isn’t confidence — it’s tooling. 🧗 Feature flags turn production into a controlled environment, not a cliff edge. https://lnkd.in/esqHPr-f #FeatureFlags #SoftwareEng #EngManager by Mark Allen Why Feature Flags Are a Must in Every Engineering Manager’s Toolkit blog.devcycle.com Like Comment Share DevCycle 1,008 followers 3w Report this post ⏱️ Every hour your engineers spend maintaining a homegrown feature flag system 🏗️ Is an hour they’re not building features users actually pay for. DIY flags aren’t free. 🐢 They’re paid for in lost velocity, focus, and morale. https://lnkd.in/eqWXpDfE #FeatureFlags #SoftwareEng #EngManager by Mark Allen Why a Homegrown Feature Flag System is a Trap blog.devcycle.com Like Comment Share DevCycle 1,008 followers 3w Report this post ✅ The era of smashing the big green deploy button and praying is over. When AI writes code, you don’t launch it wide. You wrap it in a feature flag. Ship to prod. Turn it on for 3 people. Watch it breathe. Then roll it out. This is how AI code survives production. 🏕️ https://lnkd.in/da5eDB8W #FeatureFlags #SoftwareEng #EngManager by Mark Allen Who Knew Feature Flags Would Save AI Coding blog.devcycle.com 4 Like Comment Share DevCycle 1,008 followers 3w Report this post 👾 Engineering teams don’t slow down because of code 🐌 They slow down because every deployment is treated like a launch 🏎️ Feature flags fix that 👯♂️ Decouple deploy from release → ship faster, fear less, validate sooner 🔥 If you’re still shipping big-bang style… you’re burning velocity https://lnkd.in/esqHPr-f #FeatureFlags #SoftwareEng #EngManager by Mark Allen Why Feature Flags Are a Must in Every Engineering Manager’s Toolkit blog.devcycle.com 1 Like Comment Share DevCycle 1,008 followers 4w Report this post The real data is brutal: • 30% of engineering time lost to DIY flag maintenance 🚧 • 73% of flags never removed 🔒 • Thousands of hours per year navigating flag technical debt and bloat 🫃 Homegrown feature flags aren’t “lightweight.” They’re a slow bleed. 🩸 🩸 🩸 https://lnkd.in/eqWXpDfE #FeatureFlags #SoftwareEng #EngManager by Mark Allen Why a Homegrown Feature Flag System is a Trap blog.devcycle.com 2 1 Comment Like Comment Share DevCycle 1,008 followers 1mo Report this post 🔁 The modern dev loop (or cycle 😉) isn’t write → test → ship anymore. It’s: 🤖 generate → 🏁wrap behind feature flag → 🚀 deploy → 🍰 test on a tiny slice → 🛼 roll out 🏃💨 That loop is why AI-driven teams ship faster without lighting prod on 🔥🚒. https://lnkd.in/da5eDB8W #FeatureFlags #SoftwareEng #EngManager by Mark Allen Who Knew Feature Flags Would Save AI Coding blog.devcycle.com 2 Like Comment Share DevCycle 1,008 followers 1mo Report this post ⚔️ Most teams think they have a product/engineering alignment problem. 🏁 Really, they just don’t have feature flags. 🎚️ Flags turn launches into decisions, not deployments—PMs own timing, engineers own flow, and everyone sleeps better. https://lnkd.in/esqHPr-f #FeatureFlags #SoftwareEng #EngManager by Mark Allen Why Feature Flags Are a Must in Every Engineering Manager’s Toolkit blog.devcycle.com 5 Like Comment Share DevCycle reposted this Mark Allen 1mo Report this post I’ve always wrestled with building meaningful frontend + backend demos. Nothing breaks the illusion faster than fake auth flows or placeholder tokens. In the real world, we rely on proper JWTs; therefore, our demos should reflect that. To fix the gap, I built a small Express middleware that issues real JWTs for an email address, mimicking a lightweight IDP. With that, I’ve taken the next step and created an example app using OpenFeature and DevCycle across both the frontend and the backend. The app uses middleware to generate the token and pass it through the stack, end-to-end evaluating the user's feature flags as you would in a real app. If this helps you, I’d love a ⭐ or two and PRs are always welcome. #DevOps #FeatureFlags #OpenFeature #DevCycle #NodeJS #JavaScript #SoftwareEngineering #DevEx 22 1 Comment Like Comment Share DevCycle reposted this Andrew Norris 1mo Report this post 6 months ago our onboarding looked “fine.” Nice UI, polished tutorial, solid drop-off rates. But devs still weren’t hitting SDK install. So we nuked the tutorial and rebuilt around MCP — where onboarding happens in your editor. 3× more installs. https://lnkd.in/gGShAmhK MCP Onboarding for Feature Flagging: 3x SDK Installs blog.devcycle.com 15 1 Comment Like Comment Share DevCycle reposted this Andrew Norris 2mo Report this post We learned something big about onboarding: Even great tutorials can break if they pull developers away from their real workflow. So we rebuilt onboarding around MCP to bring DevCycle into the IDE. 3× more users now reach SDK install. How it works → https://lnkd.in/gGShAmhK MCP Onboarding for Feature Flagging: 3x SDK Installs blog.devcycle.com 8 1 Comment Like Comment Share Join now to see what you are missing Find people you know at DevCycle Browse recommended jobs for you View all updates, news, and articles Join now Similar pages Taplytics Software Development Toronto, Ontario Reprompt (YC W24) Technology, Information and Internet San Francisco, California sync. Software Development San Francisco, California FlexDesk Technology, Information and Internet New York City, NY Wasp Information Technology & Services Capi Money Financial Services VectorShift Technology, Information and Internet Sully.ai Hospitals and Health Care Mountain View, California TeamOut (YC W22) Software Development San Francisco, CA Optery Technology, Information and Internet Show more similar pages Show fewer similar pages Browse jobs Engineer jobs 555,845 open jobs Senior Product Designer jobs 20,576 open jobs User Experience Specialist jobs 7,714 open jobs User Interface Designer jobs 13,154 open jobs Product Designer jobs 45,389 open jobs Product Manager jobs 199,941 open jobs Business Partner jobs 188,284 open jobs User Experience Designer jobs 13,659 open jobs Developer jobs 258,935 open jobs Designer jobs 65,273 open jobs Business Intelligence Analyst jobs 43,282 open jobs Senior Software Engineer jobs 78,145 open jobs Business Development Associate jobs 31,101 open jobs President jobs 92,709 open jobs Salesperson jobs 172,678 open jobs Software Engineer jobs 300,699 open jobs Analyst jobs 694,057 open jobs Application Tester jobs 5,112 open jobs Embedded System Engineer jobs 116,786 open jobs Full Stack Engineer jobs 38,546 open jobs Show more jobs like this Show fewer jobs like this Funding DevCycle 1 total round Last Round Pre seed Feb 1, 2021 External Crunchbase Link for last round of funding See more info on crunchbase More searches More searches Engineer jobs Web Producer jobs Digital Product Manager jobs Intern jobs Training Specialist jobs Customer Experience Manager jobs Strategy Manager jobs President jobs Product Management Intern jobs Data Scientist jobs Project Manager jobs Developer jobs Software Engineer jobs Scientist jobs Full Stack Engineer jobs C Developer jobs Senior Software Engineer jobs Enterprise Account Executive jobs Key Account Manager jobs Buyer jobs Account Manager jobs Senior Product Manager jobs Manager jobs Business Development Representative jobs Site Reliability Engineer jobs Machine Learning Engineer jobs Technical Sales Specialist jobs Claims Adjuster jobs Support Representative jobs Application Developer jobs Support Specialist jobs Lead jobs Specialist jobs Lead Engineer jobs Geographic Information System Specialist jobs Account Executive jobs Geographic Information Systems Analyst jobs Analyst jobs Support Engineer jobs Engineering Manager jobs Product Manager jobs Frontend Developer jobs Software Engineering Manager jobs Senior Tax Manager jobs Technology Lead jobs Tax Attorney jobs Associate Attorney jobs Associate Brand Manager jobs Scout jobs Operations Manager jobs Marketing Coordinator jobs User Experience Designer jobs Science Manager jobs Product Associate jobs Ruby on Rails Developer jobs Quality Assurance Automation Engineer jobs Sourcer jobs Director jobs Data Engineer jobs Research Analyst jobs LinkedIn © 2026 About Accessibility User Agreement Privacy Policy Cookie Policy Copyright Policy Brand Policy Guest Controls Community Guidelines العربية (Arabic) বাংলা (Bangla) Čeština (Czech) Dansk (Danish) Deutsch (German) Ελληνικά (Greek) English (English) Español (Spanish) فارسی (Persian) Suomi (Finnish) Français (French) हिंदी (Hindi) Magyar (Hungarian) Bahasa Indonesia (Indonesian) Italiano (Italian) עברית (Hebrew) 日本語 (Japanese) 한국어 (Korean) मराठी (Marathi) Bahasa Malaysia (Malay) Nederlands (Dutch) Norsk (Norwegian) ਪੰਜਾਬੀ (Punjabi) Polski (Polish) Português (Portuguese) Română (Romanian) Русский (Russian) Svenska (Swedish) తెలుగు (Telugu) ภาษาไทย (Thai) Tagalog (Tagalog) Türkçe (Turkish) Українська (Ukrainian) Tiếng Việt (Vietnamese) 简体中文 (Chinese (Simplified)) 正體中文 (Chinese (Traditional)) Language Agree & Join LinkedIn By clicking Continue to join or sign in, you agree to LinkedIn’s User Agreement , Privacy Policy , and Cookie Policy . Sign in to see who you already know at DevCycle Sign in Welcome back Email or phone Password Show Forgot password? Sign in or By clicking Continue to join or sign in, you agree to LinkedIn’s User Agreement , Privacy Policy , and Cookie Policy . New to LinkedIn? Join now or New to LinkedIn? Join now By clicking Continue to join or sign in, you agree to LinkedIn’s User Agreement , Privacy Policy , and Cookie Policy . | 2026-01-13T08:48:28 |
https://www.linkedin.com/uas/login?fromSignIn=true&session_redirect=https%3A%2F%2Fwww.linkedin.com%2Fcompany%2Fdevcyclehq&trk=organization_guest_main-feed-card_ellipsis-menu-semaphore-sign-in-redirect&guestReportContentType=POST&_f=guest-reporting | LinkedIn Login, Sign in | LinkedIn Sign in Sign in with Apple Sign in with a passkey By clicking Continue, you agree to LinkedIn’s User Agreement , Privacy Policy , and Cookie Policy . or Email or phone Password Show Forgot password? Keep me logged in Sign in We’ve emailed a one-time link to your primary email address Click on the link to sign in instantly to your LinkedIn account. If you don’t see the email in your inbox, check your spam folder. Resend email Back New to LinkedIn? Join now Agree & Join LinkedIn By clicking Continue, you agree to LinkedIn’s User Agreement , Privacy Policy , and Cookie Policy . LinkedIn © 2026 User Agreement Privacy Policy Community Guidelines Cookie Policy Copyright Policy Send Feedback Language العربية (Arabic) বাংলা (Bangla) Čeština (Czech) Dansk (Danish) Deutsch (German) Ελληνικά (Greek) English (English) Español (Spanish) فارسی (Persian) Suomi (Finnish) Français (French) हिंदी (Hindi) Magyar (Hungarian) Bahasa Indonesia (Indonesian) Italiano (Italian) עברית (Hebrew) 日本語 (Japanese) 한국어 (Korean) मराठी (Marathi) Bahasa Malaysia (Malay) Nederlands (Dutch) Norsk (Norwegian) ਪੰਜਾਬੀ (Punjabi) Polski (Polish) Português (Portuguese) Română (Romanian) Русский (Russian) Svenska (Swedish) తెలుగు (Telugu) ภาษาไทย (Thai) Tagalog (Tagalog) Türkçe (Turkish) Українська (Ukrainian) Tiếng Việt (Vietnamese) 简体中文 (Chinese (Simplified)) 正體中文 (Chinese (Traditional)) | 2026-01-13T08:48:28 |
https://www.linkedin.com/learning/search?trk=public_profile_guest_nav_menu_learning | Online Courses, Training and Tutorials on LinkedIn Learning Skip to main content Learning LinkedIn Learning Search skills, subjects, or software Expand search This button displays the currently selected search type. When expanded it provides a list of search options that will switch the search inputs to match the current selection. Jobs People Learning Clear text Clear text Clear text Clear text Clear text Join now Sign in Best Match Best Match View Count Newest Done Level Beginner (139,400) Intermediate (177,800) Advanced (25,176) Done Type Course (10,072) Video (261,879) Learning Path (722) Done Time to complete < 10 mins (260,559) 10 - 30 mins (9,570) 30 - 60 mins (3,390) 1 - 2 hours (3,038) 2 - 3 hours (1,190) 3+ hours (2,073) Done Software Python (8,184) Microsoft Excel (7,096) Azure (5,120) Amazon Web Services (AWS) (4,668) Microsoft 365 (3,044) SQL (2,768) ChatGPT (2,106) Power BI (2,000) Google Cloud Platform (1,612) vSphere (991) Microsoft Teams (801) Fusion 360 (737) Logic Pro (730) Git (620) Gemini (592) OpenAI API (592) Docker (520) Junos (270) Server (265) GPT (245) Done Solutions for: Business Higher Education Government Buy for my team Browse most popular courses Collaborating more effectively with Git using workflows 1m Collaborating more effectively with Git using workflows From: Git Workflows Video What is NGINX? 46s What is NGINX? From: Learning NGINX Video Training for a civil workplace 42s Training for a civil workplace From: Teaching Civility in the Workplace Video Mastering manual testing 44s Mastering manual testing From: Understanding Manual Testing Video An enhanced approach to DevOps 1m An enhanced approach to DevOps From: GitOps Foundations Video Conclusion 34s Conclusion From: AI Product Security: Secure Architecture, Deployment, and Infrastructure Video Security and compliance as code 6m Security and compliance as code From: DevOps Foundations: Infrastructure as Code Video Generative AI is a tool in service of humanity 1m Generative AI is a tool in service of humanity From: What Is Generative AI? Video Introduction 58s Introduction From: AI Product Ideation: Principles and Practical Applications Video Testing infrastructure 2m Testing infrastructure From: DevOps Foundations: Infrastructure as Code Video Introduction 51s Introduction From: AI Product Development: Technical Feasibility and Prototyping Video Using AI to create your IaC 9m Using AI to create your IaC From: DevOps Foundations: Infrastructure as Code Video Meet your AI creative collaborator 1m Meet your AI creative collaborator From: How to Research and Write Using Generative AI Tools (2023) Video Bringing resolution to your conflicts 43s Bringing resolution to your conflicts From: Conflict Resolution Foundations Video The circular economy 1m The circular economy From: Circular Economy Business Strategies Video Opus 4.5 Context Control fine-tuned for coding 9m Opus 4.5 Context Control fine-tuned for coding From: AI Trends Video Your role in a disability-inclusive workplace 49s Your role in a disability-inclusive workplace From: Disability Readiness for Leaders and Managers Video Adapt to an unpredictable workplace 1m Adapt to an unpredictable workplace From: Navigating Your Career Through Restructuring, Layoffs, and Furloughs Video Welcome 1m Welcome From: Learning Design for Sustainability Video Managing your job-seeking mindset 1m Managing your job-seeking mindset From: Managing Your Job Seeker Mindset Video Become a likable job candidate 1m Become a likable job candidate From: Engage the Likability Effect in the Job Search Video What are video interviews? 2m What are video interviews? From: Video Interview Tips Video Finding your unadvertised dream job 1m Finding your unadvertised dream job From: Find a Job in the Hidden Job Market Video Build your professional network online 1m Build your professional network online From: Digital Networking Strategies Video Bouncing back after a layoff 1m Bouncing back after a layoff From: Recovering from a Layoff Video How to succeed in a job search 1m How to succeed in a job search From: A Career Strategist's Guide to Getting a Job Video Writing a successful resume 1m Writing a successful resume From: Writing a Resume Video The empathy deficit 1m The empathy deficit From: Digital Body Language Video Why resume writing is hard (and how to make it easier) 44s Why resume writing is hard (and how to make it easier) From: Resume Makeover Video Preparing for a recession 1m Preparing for a recession From: Recession-Proof Career Strategies Video Welcome 1m Welcome From: Finding a Job Video Introduction to Fundamental Skills for Data Work: Data Visualization 15h 31m Introduction to Fundamental Skills for Data Work: Data Visualization Learning Path Course overview 1m Course overview From: Operations Strategy for Business Video Learning SoapUI for API testing 1m Learning SoapUI for API testing From: API Test Automation with SoapUI Video What is the data science playbook? 43s What is the data science playbook? From: The Data Science Playbook for Private Equity and Venture Capital Video Business taxes foundations 1m Business taxes foundations From: Business Tax Foundations Video Why addressing anxiety at work matters 1m Why addressing anxiety at work matters From: Managing Anxiety in the Workplace Video Conclusion 2m Conclusion From: Marketing Analytics: Decoding the Conversion Funnel for Revenue Growth Video Introduction and what's in the course 1m Introduction and what's in the course From: Account Management: Maintaining Relationships Video Data annotation for machine learning 51s Data annotation for machine learning From: Hands-On Data Annotation: Applied Machine Learning Video Facing ambiguity 1m Facing ambiguity From: Navigating Employee Relations as an HR Professional Video Introduction 31s Introduction From: VMware vSphere 8 Certified Technical Associate - Data Center Virtualization (VCTA-DCV) (1V0-21.20) Cert Prep Video Introduction 45s Introduction From: VMware vSphere 8 Certified Technical Associate - Data Center Virtualization (VCTA-DCV) (1V0-21.20) Cert Prep Video Introduction 34s Introduction From: VMware vSphere 8 Certified Technical Associate - Data Center Virtualization (VCTA-DCV) (1V0-21.20) Cert Prep Video Introduction 25s Introduction From: VMware vSphere 8 Certified Technical Associate - Data Center Virtualization (VCTA-DCV) (1V0-21.20) Cert Prep Video Introduction 29s Introduction From: VMware vSphere 8 Certified Technical Associate - Data Center Virtualization (VCTA-DCV) (1V0-21.20) Cert Prep Video Introduction 48s Introduction From: VMware vSphere 8 Certified Technical Associate - Data Center Virtualization (VCTA-DCV) (1V0-21.20) Cert Prep Video Introduction to generative AI in finance 55s Introduction to generative AI in finance From: Leveraging Generative AI in Finance and Accounting Video Introduction to business development strategies 56s Introduction to business development strategies From: Business Development: Strategic Planning Video Urban design and planning 1m Urban design and planning From: Strategic Planning and Urban Design Foundations Video Not seeing what you’re looking for? Join now to see all 272,119 results. Join now Explore Topics Business Technology Buy LinkedIn Learning for your business, higher education, or government team Buy for my team Explore Business Topics Artificial Intelligence for Business Business Analysis and Strategy Business Software and Tools Career Development Customer Service Diversity, Equity, and Inclusion (DEI) Finance and Accounting Human Resources Leadership and Management Marketing Professional Development Project Management Sales Small Business and Entrepreneurship Training and Education See all Explore Creative Topics AEC Animation and Illustration Audio and Music Graphic Design Motion Graphics and VFX Photography Product and Manufacturing User Experience Video Visualization and Real-Time Web Design See all Explore Technology Topics Artificial Intelligence (AI) Cloud Computing Cybersecurity Data Science Database Management DevOps Hardware IT Help Desk Mobile Development Network and System Administration Software Development Web Development See all LinkedIn © 2026 About Accessibility User Agreement Privacy Policy Cookie Policy Copyright Policy Brand Policy Guest Controls Community Guidelines العربية (Arabic) বাংলা (Bangla) Čeština (Czech) Dansk (Danish) Deutsch (German) Ελληνικά (Greek) English (English) Español (Spanish) فارسی (Persian) Suomi (Finnish) Français (French) हिंदी (Hindi) Magyar (Hungarian) Bahasa Indonesia (Indonesian) Italiano (Italian) עברית (Hebrew) 日本語 (Japanese) 한국어 (Korean) मराठी (Marathi) Bahasa Malaysia (Malay) Nederlands (Dutch) Norsk (Norwegian) ਪੰਜਾਬੀ (Punjabi) Polski (Polish) Português (Portuguese) Română (Romanian) Русский (Russian) Svenska (Swedish) తెలుగు (Telugu) ภาษาไทย (Thai) Tagalog (Tagalog) Türkçe (Turkish) Українська (Ukrainian) Tiếng Việt (Vietnamese) 简体中文 (Chinese (Simplified)) 正體中文 (Chinese (Traditional)) Language | 2026-01-13T08:48:28 |
https://developer.x.com/developer-terms/policy#3-f | Developer Policy – X Developers | X Developer Platform <g> <g> <defs> <rect id="SVGID_1_" x="-468" y="-1360" width="1440" height="3027" /> </defs> <clippath id="SVGID_2_"> <use xlink:href="#SVGID_1_" style="overflow:visible;" /> </clippath> </g> </g> <rect x="-468" y="-1360" class="st0" width="1440" height="3027" style="fill:rgb(0,0,0,0);stroke-width:3;stroke:rgb(0,0,0)" /> <path d="M13.4,12l5.8-5.8c0.4-0.4,0.4-1,0-1.4c-0.4-0.4-1-0.4-1.4,0L12,10.6L6.2,4.8c-0.4-0.4-1-0.4-1.4,0c-0.4,0.4-0.4,1,0,1.4 l5.8,5.8l-5.8,5.8c-0.4,0.4-0.4,1,0,1.4c0.2,0.2,0.4,0.3,0.7,0.3s0.5-0.1,0.7-0.3l5.8-5.8l5.8,5.8c0.2,0.2,0.5,0.3,0.7,0.3 s0.5-0.1,0.7-0.3c0.4-0.4,0.4-1,0-1.4L13.4,12z" /> </svg>" data-icon-chevron-right="<svg xmlns="http://www.w3.org/2000/svg" width="24" height="24" viewbox="0 0 24 24" aria-hidden="true" focusable="false" role="none" class="twtr-icon"> <path opacity="0" d="M0 0h24v24H0z" /> <path d="M17.207 11.293l-7.5-7.5c-.39-.39-1.023-.39-1.414 0s-.39 1.023 0 1.414L15.086 12l-6.793 6.793c-.39.39-.39 1.023 0 1.414.195.195.45.293.707.293s.512-.098.707-.293l7.5-7.5c.39-.39.39-1.023 0-1.414z" /> </svg>" data-icon-chevron-down="<svg xmlns="http://www.w3.org/2000/svg" width="24" height="24" viewbox="0 0 24 24" aria-hidden="true" focusable="false" role="none" class="twtr-icon"> <path opacity="0" d="M0 0h24v24H0z" /> <path d="M20.207 7.043c-.39-.39-1.023-.39-1.414 0L12 13.836 5.207 7.043c-.39-.39-1.023-.39-1.414 0s-.39 1.023 0 1.414l7.5 7.5c.195.195.45.293.707.293s.512-.098.707-.293l7.5-7.5c.39-.39.39-1.023 0-1.414z" /> </svg>" data-icon-arrow-left="<svg width="28px" height="28px" viewbox="0 0 28 28" version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" aria-hidden="true" focusable="false" role="none" class="twtr-icon u01-meganav__icon-arrow-left"> <g stroke="none" stroke-width="1" fill="none" fill-rule="evenodd" stroke-linecap="round"> <g transform="translate(-1216.000000, -298.000000)" stroke-width="2.25"> <g transform="translate(1200.000000, 282.000000)"> <g transform="translate(17.000000, 17.000000)"> <path d="M0.756410256,12.8589744 L25.7179487,12.8589744"></path> <path d="M13.2371795,25.3397436 L25.7179487,12.8589744"></path> <path d="M13.2371795,12.4807692 L25.3397436,0.378205128" transform="translate(19.288462, 6.429487) rotate(-90.000000) translate(-19.288462, -6.429487) "></path> </g> </g> </g> </g> </svg>" data-left-nav-items="[{"isActive":false,"hasActiveChild":false,"children":[{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"X API","linkDisabled":false,"title":"X API","path":"https://developer.x.com/en/products/twitter-api"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"X Ads API","linkDisabled":false,"title":"X Ads API","path":"https://developer.x.com/en/products/x-ads-api"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"X for websites","linkDisabled":false,"title":"X for websites","path":"https://developer.x.com/en/products/x-for-websites"}],"overviewTitle":"Products","linkDisabled":true,"title":"Products","path":"https://developer.x.com/en/products"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Docs","linkDisabled":false,"title":"Docs","path":"https://docs.x.com/"},{"isActive":false,"hasActiveChild":false,"children":[{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Build for business","linkDisabled":false,"title":"Build for business","path":"https://developer.x.com/en/use-cases/build-for-businesses"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Build for the public","linkDisabled":false,"title":"Build for the public","path":"https://developer.x.com/en/use-cases/build-for-consumers"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Do research","linkDisabled":false,"title":"Do research","path":"https://developer.x.com/en/use-cases/do-research"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Teach \u0026 learn","linkDisabled":false,"title":"Teach \u0026 learn","path":"https://developer.x.com/en/use-cases/teach-and-learn"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Build for good","linkDisabled":false,"title":"Build for good","path":"https://developer.x.com/en/use-cases/build-for-good"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Build for fun","linkDisabled":false,"title":"Build for fun","path":"https://developer.x.com/en/use-cases/build-for-fun"}],"overviewTitle":"Use Cases","linkDisabled":true,"title":"Use Cases","path":"https://developer.x.com/en/navigation/left-nav-items/use-cases"},{"isActive":false,"hasActiveChild":false,"children":[{"isActive":false,"hasActiveChild":false,"children":[{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Changelog","linkDisabled":false,"title":"Changelog","path":"https://docs.x.com/updates/changelog"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Blog","linkDisabled":false,"title":"Blog","path":"https://developer.x.com/en/blog"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Newsletter","linkDisabled":false,"title":"Newsletter","path":"https://developer.x.com/en/updates/stay-informed"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"YouTube","linkDisabled":false,"title":"YouTube","path":"https://www.youtube.com/c/twitterdev"}],"linkDisabled":true,"title":"Stay informed","path":"https://developer.x.com/"},{"isActive":false,"hasActiveChild":false,"children":[{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Forums","linkDisabled":false,"title":"Forums","path":"https://twittercommunity.com/"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Events","linkDisabled":false,"title":"Events","path":"https://twitterdev.bevylabs.com/"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Insiders","linkDisabled":false,"title":"Insiders","path":"https://developer.twitter.com/en/community/insiders"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Community leaders","linkDisabled":false,"title":"Community leaders","path":"https://developer.x.com/en/community/leaders"}],"linkDisabled":true,"title":"Connect","path":"https://developer.x.com/"}],"overviewTitle":"Community","linkDisabled":false,"menuType":"multiCategory","title":"Community","path":"https://developer.x.com/en/community"}]" data-right-nav-items="[{"isActive":false,"hasActiveChild":false,"children":[{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Policies","linkDisabled":false,"title":"Policies","path":"https://developer.x.com/en/developer-terms"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Developer agreement","linkDisabled":false,"title":"Developer agreement","path":"https://developer.x.com/en/developer-terms/agreement-and-policy/source"}],"overviewTitle":"Support","linkDisabled":false,"title":"Support","path":"https://developer.x.com/en/support"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Developer Portal","linkDisabled":false,"title":"Developer Portal","path":"https://developer.twitter.com/en/portal/petition/essential/basic-info"}]" data-cta-enabled="true" data-profile-enabled="true" data-cta-link-new-tab="false" data-root-page-title="Developer Platform"> Developer terms Developer Policy Let's get started X + Developers Using this policy X + Developers Using this policy X + Developers X loves developers. We’re delighted and amazed by the tools and services this community creates by harnessing the power of X data. As part of our commitment to this community, we aim to provide data access that is open and fair for developers, safe for people on X, and beneficial for the X platform as a whole. To further these goals we’ve crafted the Developer Policy as a guide to help people understand our rules and expectations about appropriate API and X Content usage. This Developer Policy (“ Policy ”) provides rules and guidelines for developers who interact with X’s ecosystem of applications, services, website, web pages and content. It is part of your contract with X governing access to and use of the X API and X Content (either as part of the Developer Agreement or other written agreement with X). Policy violations are considered violations of your agreement. This Policy may be changed from time to time without notice. Capitalized terms used in this Policy, which are not defined in this Policy, will have the respective meanings ascribed to them in the Developer Agreement or the Master License Agreement. Using this policy We’ve structured this policy to make it as easy to follow as possible. Please keep information from the following policy sections top of mind as you use the X API and X Content: 1. Set Yourself Up for Success - You are responsible for complying with all X policies. It’s important that you review and understand this Policy, as well as the policies we link to in this document, before you access the X API and X Content. The time spent reviewing our policies may save you hours of rework down the road. 2. Privacy and Control are Essential - Protecting and defending the privacy of people on X is built into the core DNA of our company. As such, we prohibit the use of X data in any way that would be inconsistent with people’s reasonable expectations of privacy. By building on the X API or accessing X Content, you have a special role to play in safeguarding this commitment, most importantly by respecting people’s privacy and providing them with transparency and control over how their data is used. 3. Follow the Platform Usage Guidelines - Getting approved to access the X API and X Content is just the first step. Our Platform Usage Guidelines should be your first stop anytime you have questions about how to ensure policy compliance for your planned use of the X platform. We’ve provided a lot more detail on what each of these three key sections mean below. Please review them carefully to ensure that your usage of the X API and X Content is consistent with our policies. If we believe you are in violation of this Policy (or any other X policy), we may suspend or permanently revoke your access to the X API and X Content. Finally, please note that X may monitor your use of the X API to improve the X Applications, to examine any commercial use, and to ensure your compliance with your approved use case and this Policy. Thanks for reading, and thank you for building with us! We look forward to seeing what you create! Chapter 1 Set yourself up for success Set yourself up for success Set yourself up for success Set yourself up for success You can avoid many potential pitfalls while using the X API by ensuring that your service has been built the right way from day 1. This section of the Developer Policy contains rules that all developers must follow before using the X API or X Content. The Free, Basic, and Pro plans (as described at developer.x.com/en ) are designed for hobbyists, commercial prototyping, early-stage X product integrations, and supporting applications with limited end-users. If you use the X API and X Content beyond this scope, then you must apply (or already subscribe to) an Enterprise plan (as described at developer.x.com/en ). We review all proposed uses of the X developer platform to verify policy compliance — so you’re required to disclose (and update, as applicable) your planned use of the X API and X Content in order to be granted and to maintain access. All new developers must apply for a developer account to access the X API. Current developers without an approved developer account must apply for one as directed to do so by X. As part of this process, you’ll need to provide us with a written description of your intended uses of the X API and X Content. Your use case description is binding on you, and any substantive deviation from it may constitute a violation of our rules and result in enforcement action. You must notify us of any substantive modification to your use case and receive approval before you may begin using X Content for that new purpose. Failure to do so may result in suspension and termination of your API and data access. By building on the X API or accessing X Content, you must comply with ALL X policies. These include this Developer Policy , the Automation Rules , the Display Requirements , the API Restricted Uses Rules , the X Rules , and the X Brand Resources , as well as any other agreements you enter into with X relating to your use of the X API or X Content, including but not limited to the Developer Agreement or a Master Licensing Agreement or Order (as applicable). You must also comply with any modifications to these policies and any new policies launched by X. It is your responsibility to monitor the use of your service and to design your service to prevent violations of X policy by people who use it. Failure to do so may result in suspension or termination of your API and X Content access. You may not register multiple applications for a single use case or substantially similar or overlapping use cases. In this context, a “use case” is a consistent set of analyses, displays, or actions performed via an application. "White label" versions of a tool or service are not permissible. If you plan to “white label” versions of your application, you must notify and receive separate approval from us. As a single exception to these rules, you may create and use a maximum of 3 applications for development, staging, and production instances of the same service. These apps must be registered to a single account, and should be clearly identified (in the name and description) as dev, staging, and prod instances of a single service. You may not use development or staging applications for production purposes. You must keep all API keys or other access credentials private. You may not use, and may not encourage or facilitate others to use, API keys or other access credentials owned by others. Your license agreement with X limits your use of the X API and X Content. Among other things, the X API has rate limits which help to ensure fair data usage and to combat spam on the platform. You may not exceed or circumvent rate limits, or any other limitations or restrictions described in this Policy or your agreement with X, listed on the Developer Site , or communicated to you by X. You may not remove or alter any proprietary notices or marks on X Content received via the X API. This helps to make sure that people know where X Content is coming from, and who it belongs to. For data integrity and platform health reasons, you may not interfere with, intercept, disrupt, or disable any features of the X API or the X service. In other words, use the APIs as intended and documented on developer.x.com . Refer to our HackerOne guidelines for more details about acceptable use. Chapter 2 Privacy and control are essential Privacy and control are essential Consent & permissions Content compliance Off-X matching Your privacy policy Using geo-data X passwords Privacy and control are essential Consent & permissions Content compliance Off-X matching Your privacy policy Using geo-data X passwords Privacy and control are essential X takes privacy seriously, and we expect everyone using X Content and the X API to do the same. Any use of the X developer platform, X API, or X Content in a manner that is inconsistent with peoples’ reasonable expectations of privacy may be subject to enforcement action, which can include suspension and termination of API and X Content access. Your commitment to privacy and control must extend to all uses of X Content and all aspects of the service that you build using our API. To that end, the people using your service must understand and consent to how you use their data, and how you access X on their behalf. This can be accomplished through providing people with a clear, comprehensive, and transparent privacy policy, as well as ensuring that you get express and informed consent from each person using your service before taking any action on their behalf. Please note that a person authenticating into your service does not by itself constitute consent. Consent & permissions In particular, you must get express and informed consent from people before doing any of the following: Taking any actions on their behalf. This includes (but is not limited to): Posting content to X Following/unfollowing accounts Modifying profile or account information Adding hashtags or any other content to Posts Republishing content accessed by means other than via the X API or other X tools Using someone’s X Content to promote a product or service Storing non-public content such as Direct Messages (DMs), or any other private or confidential information Sharing or publishing protected content, or any other private or confidential information If your service allows people to post content to X you must do the following before publishing: Show exactly what will be published Make it clear to people using your service what geo information (if any) will be added to the content If your service allows people to post content to both your service and X, you must do the following before publishing: Obtain permission to post the content Explain where you will post the content You must respect the protected and blocked status of all X Content. You may not serve content obtained using one person’s authentication token to a different person who is not authorized to view that content. Protected accounts: A protected account ’s content is only available to people who have been approved by the owner to follow that account. So, if you run a service that accesses protected accounts, you may only do so to serve such content to the specific people with permission to view that content. Blocked accounts: People on X are able to block access to their accounts for any reason they choose. Commingling information obtained from tokens (or any other API-based action) to bypass this choice is not permitted. As Direct Messages (DMs) are non-public in nature, services that provide DM features must take extra steps to safeguard personal privacy. You may not serve DM content to people who are not authorized to view that content. If your service provides DM functionality you must also: Notify people if you send read receipt events for DMs. You can do this by providing a notice directly in your service, or by displaying read receipts from other participants in a conversation. Get consent before configuring media to be sent in a DM as "shared" (i.e. reusable across multiple DMs). If you do allow media in a DM to be “shared,” you must provide a clear notice that this content will be accessible to anyone with the media’s URL. Content compliance If you store X Content offline, you must keep it up to date with the current state of that content on X. Specifically, you must delete or modify any content you have if it is deleted or modified on X. This must be done as soon as reasonably possible, or within 24 hours after receiving a request to do so by X or the applicable X account owner, or as otherwise required by your agreement with X or applicable law. This must be done unless otherwise prohibited by law, and only then with the express written permission of X. Modified content can take various forms. This includes (but is not limited to): Content that has been made private or gained protected status Content that has been suspended from the platform Content that has had geotags removed from it Content that has been withheld or removed from X Off-X matching We limit the circumstances under which you may match a person on X to information obtained or stored off-X. Off-X matching involves associating X Content, including a X @handle or user ID, with a person, household, device, browser, or other off-X identifier. You may only do this if you have express opt-in consent from the person before making the association, or as described below. In situations in which you don’t have a person’s express, opt-in consent to link their Xidentity to an off-X identifier, we require that any connection you draw be based only on information that someone would reasonably expect to be used for that purpose. In addition, absent a person’s express opt-in consent you may only attempt to match your records about someone to a X identity based on: Information provided directly to you by the person. Note that records about individuals with whom you have no prior relationship, including data about individuals obtained from third parties, do not meet this standard; and/or Public data. “Public data” in this context refers to: Information about a person that you obtained from a public, generally-available resource (such as a directory of members of a professional association) Information on X about a person that is publicly available, including: Posts Profile information, including an account bio and publicly-stated location Display name and @handle Your privacy policy You must display your service’s privacy policy to people before they are permitted to download, install, or sign up to your service. It must disclose at least the following information: The information that you collect from people who use your service How you use and share that information (including with X) How people can contact you with inquiries and requests regarding their information Your privacy policy must be consistent with all applicable laws, and be no less protective of people than X’s Privacy Policy and the privacy policy of our other services and corporate affiliates . You must cease your access to the X API and the use of all X Content if you are unable to comply with your and/or X’s Privacy Policy. Using geo-data Use of geo data comes with additional restrictions due to the sensitive nature of this information. If your service adds location information to Posts, you must disclose to people: When you add location information Whether you add location information as a geotag or annotations data Whether your location information is listed as a place, or as geographic coordinates If your application allows people to post with their location you must comply with X’s geo guidelines in full. Any use of location data or geographic information on a standalone basis is prohibited. You may not (and may not permit others to) store, aggregate, or cache location data and other geographic information contained in X Content, except as part of a Post. For example, you may not separate location data or geographic information out from Posts to show where individuals have been over time. Heat maps and related tools that show aggregated geo activity (e.g., the number of people in a city using a hashtag) are permitted. X passwords You may not store X passwords, or request that people provide their X password, account credentials, or developer application information (including consumer key) to you directly. We suggest the use of Sign-in with X as the authentication tool to link your service and people on X. Chapter 3 Platform usage guidelines Platform usage guidelines Spam, bots, and automation X performance benchmarking Public display of Posts Content redistribution Pay to engage Service authenticy X name, logo, and likeness Advertising on X Platform usage guidelines Spam, bots, and automation X performance benchmarking Public display of Posts Content redistribution Pay to engage Service authenticy X name, logo, and likeness Advertising on X Platform usage guidelines Have you taken care to review X’s policies and set up your API access the right way? Does your service follow X’s privacy and control guidelines? If you can answer yes to these two questions, then you are ready to start using the X API and X Content. X’s Platform Usage Guidelines provide the assistance needed to ensure that your use of X Content is compliant from day 1 throughout the lifecycle of your service. We suggest reviewing these rules on a regular basis to make sure that your integration is operating in a way that is safe and beneficial to people on X and the X platform as a whole. Spam, bots, and automation The use of the X API and developer products to create spam, or engage in any form of platform manipulation, is prohibited. You should review the X Rules on platform manipulation and spam , and ensure that your service does not, and does not enable people to, violate our policies. Services that perform write actions, including posting Posts, following accounts, or sending Direct Messages, must follow the Automation Rules . In particular, you should: Always get explicit consent before sending people automated replies or Direct Messages Immediately respect requests to opt-out of being contacted by you Never perform bulk, aggressive, or spammy actions, including bulk following Never post identical or substantially similar content across multiple accounts If you’re operating an API-based bot account you must clearly indicate what the account is and who is responsible for it. You should never mislead or confuse people about whether your account is or is not a bot. A good way to do this is by including a statement that the account is a bot in the profile bio. X performance benchmarking You may not use the X API to measure the availability, performance, functionality, or usage of X for benchmarking, competitive, or commercial purposes. For example, you should never use the X API to: Calculate aggregate X metrics, such as the total number of Monthly Actives (MAs) or Daily Actives (DAs) Calculate aggregate X Post metrics, such as the total number of Posts posted per day, or the number of account engagements Measure or analyze the responsiveness of X Measure or analyze spam or security on X, except as permitted below We support research that helps improve conversational health on X. You may not publicly disclose any research or findings concerning, or develop, create, or offer services using, the X API or X Content that measure, analyze, or attempt to identify behaviors or content which violate X policies without express written permission from X. DSA Researchers: If you need to contact X relating to access under Art. 40 of the Digital Services Act, please contact EU-Questions@X.com . If you wish to apply for researcher access, please submit an application . Public display of Posts You must maintain the integrity of all X Content that you display publicly or to people who use your service. If you don’t use X for Websites to display content, then you must use the X API to retrieve the most current version available for display. If displayed content ceases to be available through the X API, then you must remove it from your service as soon as reasonably possible, or within 24 hours after the receipt of a removal request from X, or the applicable X account owner, or as otherwise required by applicable law. There are specific rules you must follow if you display X Content offline. Follow the guidelines for using Posts in broadcast if you display Posts offline. If you embed or display Posts, you must contact us about your X API access if your site exceeds 10 million daily impressions. X reserves the right to require additional terms as a condition to your use of the X API. Additional restrictions on X for Websites developer use include: Embedded Posts and/or embedded timelines You must provide people with legally sufficient notice that fully discloses X’s collection and use of data about browsing activities on your website, including for interest-based advertising and personalization. You must also obtain legally sufficient consent from people for such collection and use You must provide legally sufficient instructions on how people can opt out of X’s interest-based advertising and personalization as described here X for Websites widgets You must ensure that people are provided with clear and comprehensive information about, and consent to, the storing and accessing of cookies or other information on their devices as described in X’s cookie use , where providing such information and obtaining such consent is required by law Services targeted to children under 13 Services targeted to children under 13 must opt out of tailoring X in any embedded Post and/or embedded timelines by setting the opt-out parameter to be ‘true’ as described here Content redistribution The best place to get X Content is directly from X. Consequently, we restrict the redistribution of X Content to third parties. If you provide X Content to third parties, including downloadable datasets or via an API, you may only distribute Post IDs, Direct Message IDs, and/or User IDs (except as described below). In total, you may not distribute more than 1,500,000 Post IDs to any entity (inclusive of multiple individuals associated with a single entity) within any 30 day period unless you have received written permission from X. In addition, developers may provide up to 500 public Posts Objects and/or User Objects to each person who uses your service on a daily basis if this is done via non-automated means (e.g., download of spreadsheets or PDFs). Academic researchers are permitted to distribute Post IDs and/or User IDs solely for the purposes of non-commercial research on behalf of an academic institution, and that has been approved by X in writing, or peer review or validation of such research. Only as many Post IDs or User IDs that is necessary for such research, and has been approved by X may be used. Any X Content provided to third parties remains subject to this Policy, and those third parties must agree to the X Terms of Service , Privacy Policy , Developer Agreement , and Developer Policy before receiving such downloads. You may not enable any entity to circumvent any other limitations or restrictions on the distribution of X Content as contained in this Policy , the Developer Agreement , or any other agreement with X. Note: This Section does not apply to researchers with X API access via Art. 40 of the EU Digital Services Act (2022) (“ DSA ”), who are instead subject to the procedures and restrictions set forth in the DSA and the Developer Agreement. Pay to engage Your service shouldn’t compensate people to take actions on X, as that results in inauthentic engagement that degrades the health of the platform. As you use the X API you may not sell or receive monetary or virtual compensation for any X actions. This includes, but is not limited to, Posts, follows, unfollows, reposts, likes, comments, and replies. Service authenticity You must clearly identify your service so that people can understand its source and purpose. Don’t use names, logos, or URLs that mask your service’s identity and features, or that falsely imply an affiliation with X or third parties. Note that creating applications for the purpose of selling names, or to prevent others from using names, is prohibited. You may not use any URL (including shortened URLs) for your service that directs people to: A site that is unrelated to your service A spam or malware site A site that encourages people to violate X policy X name, logo, and likeness You may only use and display the X name and logo to identify X as the source of X Content. You should never use the X name and logo, the X Official Partner Program badge, or any other similar marks or names in a manner that creates a false sense of endorsement, sponsorship, or association with X. The X Brand Resources contain detailed information to help you use the X brand in the right way. You may only use the X Verified Account badge and any other enhanced account categorization as it is reported to you by X through the API. This helps people know that the content your service displays is equivalent to that shown on X. Advertising on X There are restrictions regarding how and where you are allowed to advertise around X Content. To start, your advertisements can’t resemble or reasonably be confused by people as a Post. Other rules on advertising include: There must be a clear separation between X Content and your advertisements. You may not place any advertisements within the X timeline other than X Ads. X reserves the right to serve advertising via the X API. If you decide to serve X Ads once we start delivering them via the API, we will share a portion of advertising revenue with you in accordance with the relevant terms and conditions. You may not use X Content, or information obtained from the X API to target people with advertising outside of the X platform. Chapter 4 Rules for specific X services or features X login X Cards Definitions X login X Cards Definitions The following additional rules apply for any use of the X services or features listed below: X login You must present people with easy to find options to log into and out of X, for example via the OAuth protocol. The Sign in with X option must be displayed at least as prominently as any other sign-up or sign-in feature on your service. You must also provide people without a X account the opportunity to create one via X. Once someone on your service authenticates via Sign in with X you must clearly display their X identity. X identity includes the person’s current X @handle, avatar, and X logo. Any display of someone’s X followers on your service must clearly show that the relationship is associated with X. X Cards To ensure a quality experience you must develop your Card to render across all platforms where Cards are displayed. Additional rules that you must follow when using Cards include: You must mark your Post as ‘true’ for sensitive media if you plan to display such media within a Card You must use HTTPS for hosting all assets within your Card. Your Card should never generate active mixed content browser warnings Audio and video content should include stop or pause controls, and default to ‘sound off’ for videos that automatically play content You may not exceed or circumvent X’s limitations placed on any Cards, including the Card’s intended use. Additional restrictions on Cards use include: You may not place third-party sponsored content within Cards without X’s approval You may not attach monetary incentives (including virtual currency) within your Card or on X from your Card You may not include content or actions within your Card that are misleading or not contextually relevant, such as URLs and media You may only attach an App Card to a Post when someone is explicitly promoting or referring to the app in the Post Definitions X Content ‒ Posts, Post IDs, X end user profile information, and any other data and information made available to you through the X API or by any other means authorized by X, and any copies and derivative works thereof. Developer Site ‒ X’s developer site located at https://developer.x.com . Services ‒ Your websites, applications and other offerings that display X Content or otherwise use the Licensed Material as explicitly approved by X. Post ID ‒ A unique identification number generated for each Post. Post ‒ A posting made on X Applications. “X” ‒ Means (a) X Corp. (865 FM 1209, Building 2, Bastrop, TX 78602, USA) if your principal place of business is outside the European Union, EFTA States, and the United Kingdom; or (b) X Internet Unlimited Company (One Cumberland Place, Fenian Street, Dublin 2, D02 AX07, Ireland) if your principal place of business is in the European Union, EFTA States, or the United Kingdom. Direct Message - A message that is privately sent on X Applications by one end user to one or more specific end user(s) using X’s Direct Message function. X API ‒ The X Application Programming Interface (“API”), Software Development Kit (“SDK”) and/or the related documentation, data, code, and other materials provided by X with the API, as updated from time to time, including without limitation through the Developer Site. X Applications ‒ X’s consumer facing products, services, applications, websites, web pages, platforms, and other offerings, including without limitation, those offered via https://x.com and X's mobile applications. Developer policy and terms Follow @XDevelopers Subscribe to developer news X platform X.com Status Accessibility Embed a post Privacy Center Transparency Center Download the X app Try Grok.com X Corp. About the company Company news Brand toolkit Jobs and internships Investors Help Help Center Using X X for creators Ads Help Center Managing your account Email Preference Center Rules and policies Contact us Developer resources Developer home Documentation Forums Communities Developer blog Engineering blog Developer terms Business resources Advertise X for business Resources and guides X for marketers Marketing insights Brand inspiration X Ads Academy © 2026 X Corp. Cookies Privacy Terms and conditions Did someone say … cookies? X and its partners use cookies to provide you with a better, safer and faster service and to support our business. Some cookies are necessary to use our services, improve our services, and make sure they work properly. Show more about your choices . Accept all cookies Refuse non-essential cookies | 2026-01-13T08:48:28 |
https://www.epa.gov/topics-epa-web | A - Z Topic Index | US EPA Skip to main content An official website of the United States government Here’s how you know Here’s how you know Official websites use .gov A .gov website belongs to an official government organization in the United States. Secure .gov websites use HTTPS A lock ( Lock A locked padlock ) or https:// means you’ve safely connected to the .gov website. Share sensitive information only on official, secure websites. JavaScript appears to be disabled on this computer. Please click here to see any active alerts . Menu Search Search Primary navigation Environmental Topics Environmental Topics Air Bed Bugs Chemicals, Toxics, and Pesticide Emergency Response Environmental Information by Location Health Land, Waste, and Cleanup Lead Mold Radon Research Science Topics Water Topics A-Z Topic Index Laws & Regulations Laws & Regulations By Business Sector By Topic Compliance Enforcement Guidance Laws and Executive Orders Regulations Report a Violation Report a Violation Environmental Violations Fraud, Waste or Abuse About EPA About EPA Our Mission and What We Do Headquarters Offices Regional Offices Labs and Research Centers Planning, Budget, and Results Organization Chart EPA History Breadcrumb Home A - Z Topic Index 2 2025 Southern California Wildfires A About EPA Acid Rain Acute Exposure Guideline Levels for Airborne Chemicals Agriculture AgSTAR: Biogas Recovery in the Agriculture Sector Air Data: Air Quality Data Collected at Outdoor Monitors Across the US Air Emission Measurement Center (EMC) Air Emissions Factors and Quantification Air Emissions Inventories Air Emissions Modeling Air Emissions Monitoring Knowledge Base Air Monitoring at Agricultural Operations Air Quality Air Quality Analysis Air Quality Designations for Lead Air Quality Designations for Nitrogen Dioxide Air Quality Designations for Ozone Air Quality Designations for Particle Pollution Air Quality Designations for Sulfur Dioxide Air Quality Implementation Plans Air Quality in New England Air Quality Information for International Audiences Air Quality System (AQS) Air Research Air Sensor Toolbox Air Toxics Screening Assessment Air: Fate, Exposure, and Risk Analysis (FERA) Ambient Monitoring Technology Information Center (AMTIC) Ambient Water Monitoring and Assessment: Resources and Tools America's Children and the Environment American Rescue Plan (ARP) Anaerobic Digestion (AD) Analytical Methods and Procedures for Pesticides Asbestos Assessing and Managing Chemicals under TSCA Asthma AVoided Emissions and geneRation Tool (AVERT) B Beaches Bed Bugs: Get Them Out and Keep Them Out Benchmark Dose Tools Biosolids Board of Scientific Counselors (BOSC) Bonita Peak Mining District Bristol Bay Brownfields Building the Capacity of Drinking Water Systems Burn Wise C California Clean Air Technology Initiative CAMEO (Computer-Aided Management of Emergency Operations) Carbon Monoxide (CO) Pollution in Outdoor Air Careers Causal Analysis/Diagnosis Decision Information System (CADDIS) Certification and Compliance for Vehicles and Engines Certification of Laboratories that Analyze Drinking Water Samples to Ensure Compliance with Regulations Charles River Chemical Data Reporting under the Toxic Substances Control Act Chemicals under the Toxic Substances Control Act (TSCA) Chesapeake Bay Total Maximum Daily Load (TMDL) Choose Fish and Shellfish Wisely CHP Resource Center Circular Economy Civil Rights Clean Air Power Sector Programs Clean Air Status and Trends Network (CASTNET) Clean Air Technology Center Clean and Safe Water in Indian Country Clean Heavy-Duty Vehicles Program Clean School Bus Program Clean Water Act Analytical Methods Clean Water Act Hazardous Substance Facility Response Plans Clean Water Act Section 303(d): Impaired Waters and Total Maximum Daily Loads (TMDLs) Clean Water Act Section 404(g) Tribal and State Assumption Clean Water State Revolving Fund (CWSRF) Clean Watersheds Needs Survey Cleaning Up Our Land, Water and Air Cleaning Up, Protecting and Preserving Tribal Lands Cleanups at Federal Facilities Clearinghouse for Inventories and Emissions Factors (CHIEF) Climate Change Climate Change Adaptation Resource Center (ARC-X) Climate Change Research Climate Change Science Climate Change: Resilience and Adaptation in New England (RAINE) Climate Ready Estuaries Clinical Studies in Environmental Health CMAQ: The Community Multiscale Air Quality Modeling System CO-Benefits Risk Assessment Health Impacts Screening and Mapping Tool (COBRA) Coal Combustion Residuals (CCR) Coalbed Methane Outreach Program (CMOP) Collision Repair Campaign to Reduce Air Toxics Colorado Smelter Columbia River Combined Air Emissions Reporting Communicating Risks from Contaminated Sites Community Information about the Union Pacific Site in Houston's Fifth Ward Compliance Compliance and Fuel Economy Data for Vehicles and Engines Complying with Air Emissions Standards for Stationary Sources Computational Toxicology and Exposure Online Resources Confidential Business Information under TSCA Congressional and Intergovernmental Relations Continuous Improvement Contracting with EPA Controlled Unclassified Information (CUI) Controlling Air Pollution from Oil and Natural Gas Operations Controlling Air Pollution from Stationary Engines Controlling Rodents and Regulating Rodenticides Cooling Water Intakes Coral Reefs Coronavirus (COVID-19) and Disinfectants Corrective Action Cleanups around the Nation Criteria Air Pollutants Cross-Media Electronic Reporting Rule (CROMERR) Cross-State Air Pollution Cumulative Impacts Cybersecurity for the Water Sector D Data Developer Central Diesel Emissions Reduction Act Funding Diesel Fuel Standards Digital Accessibility Dioxin Disaster Debris Mitigation and Planning Drinking Water and Wastewater Laboratory Network Drinking Water and Wastewater Resilience Drinking Water Contaminant Candidate List (CCL) and Regulatory Determination Drinking Water Data and Tools Drinking Water Requirements for States and Public Water Systems Drinking Water State Revolving Fund (DWSRF) Drinking Water System Operations in Wyoming and on Tribal Lands in EPA Region 8 E E-Enterprise for the Environment E3: Economy - Energy - Environment Earth Day East Palestine, Ohio Train Derailment EcoDIVER: Ecological Database and Interactive Visualizations of Evidence Records Economic and Cost Analysis for Air Pollution Regulations Ecosystems Research Effluent Guidelines Electric Power Systems Partnership Electronic Reporting of Air Emissions Emergencies and Indoor Air Quality Emergency Planning and Community Right-to-Know Act Emergency Response Emergency Response for Drinking Water and Wastewater Utilities Emergency Response Research Emergency Response to August 2015 Release from Gold King Mine Emission Standards Reference Guide for On-road and Nonroad Vehicles and Engines Emissions & Generation Resource Integrated Database (eGRID) Emissions Trading Endocrine Disruptor Screening Program (EDSP) Energy and the Environment Energy Resources for State, Local, and Tribal Governments Enforcement EnviroAtlas Envirofacts Environmental Benefits Mapping and Analysis Program - Community Edition (BenMAP-CE) Environmental Collaboration and Conflict Resolution (ECCR) Environmental Concerns of Communities around Ambler, Pennsylvania Environmental Economics Environmental Education (EE) Environmental Geophysics Environmental Information Exchange Network (EN) Environmental Management Systems Environmental Measurements and Modeling Environmental Protection in Indian Country Environmental Response Team (ERT) Environmental Sampling and Analytical Methods (ESAM) Program Environmental Topics EPA Build America, Buy America (BABA) EPA Center for Corporate Climate Leadership EPA Cleanups: Communities around New Bedford Harbor EPA Cleanups: GE-Pittsfield/Housatonic River Site EPA Docket Center EPA EcoBox (A Toolbox for Ecological Risk Assessors) EPA Freedom of Information Act (FOIA) EPA Grants EPA Guidance Documents EPA History EPA in Alabama EPA in Alaska EPA in Arizona EPA in Arkansas EPA in California EPA in Colorado EPA in Connecticut EPA in Delaware EPA in District of Columbia EPA in Florida EPA in Georgia EPA in Hawai'i EPA in Idaho EPA in Illinois EPA in Indiana EPA in Iowa EPA in Kansas EPA in Kentucky EPA in Louisiana EPA in Maine EPA in Maryland EPA in Massachusetts EPA in Michigan EPA in Minnesota EPA in Mississippi EPA in Missouri EPA in Montana EPA in Nebraska EPA in Nevada EPA in New Hampshire EPA in New Jersey EPA in New Mexico EPA in New York EPA in North Carolina EPA in North Dakota EPA in Ohio EPA in Oklahoma EPA in Oregon EPA in Pennsylvania EPA in Puerto Rico EPA in Rhode Island EPA in South Carolina EPA in South Dakota EPA in Tennessee EPA in Texas EPA in the Pacific Islands EPA in the U.S. Virgin Islands EPA in Utah EPA in Vermont EPA in Virginia EPA in Washington EPA in West Virginia EPA in Wisconsin EPA in Wyoming EPA National Library Network EPA National Records Management Program EPA Quality Program EPA Regional Monitoring Networks (RMNs) for Aquatic Ecosystems EPA Requirements for Importers and Exporters EPA Research to Support States EPA Response to Enbridge Spill in Michigan EPA Science Matters Newsletter EPA Smart Sectors Program EPA Template Accessibility Compliance Check EPA Transcriptomic Assessment Product (ETAP) EPA's Federal Employee Relocation Center EPA's Implementation of the Privacy Act EPA's Laboratory Enterprise (LE) EPA's Office of Inspector General EPA's Report on the Environment (ROE) EPA's Study of Hydraulic Fracturing for Oil and Gas and Its Potential Impact on Drinking Water Resources EPA's Work in the Gulf of America EPA’s Portfolio of Human Health Science Assessments Estuaries and the National Estuary Program Evaluating EPA's Programs Exposure Assessment Resources (ExpoBox) External Civil Rights F Facility Registry Service Facts and Figures about Materials, Waste and Recycling Federal Advisory Committee Act Federal Air Rules for Indian Reservations (FARR) in Idaho, Oregon and Washington Federal Certification to Apply Restricted Use Pesticides in Indian Country Federal Electronics Challenge (FEC) Federal Funding for Water and Wastewater Utilities in National Disasters (Fed FUNDS) Federal Green Challenge (FGC) FEDFacts: Information about the Federal Electronic Docket Facilities Fiat Chrysler Automobile Diesel Vehicle Violations FIFRA Scientific Advisory Panel Filings, Procedures, Orders and Decisions of EPA's Administrative Law Judges Financial Services Flint Flooded Homes Cleanup Guidance Formaldehyde Fuel Economy Fuels Registration, Reporting and Compliance Help G Gasoline Standards General Conformity Geoengineering Geospatial Resources at EPA Global Change Explorer Global Methane Initiative (GMI) Grants Mining District in New Mexico Great Lakes Areas of Concern Great Lakes Funding Great Lakes Initiative (GLI) Clearinghouse Great Lakes Monitoring Great Lakes Water Quality Agreement (GLWQA) Green Building Tools for Tribes Green Chemistry Green Engineering Green Infrastructure Green Power Markets Green Power Partnership Green Streets, Green Jobs, Green Towns (G3) Program Green Vehicle Guide GreenChill Program Greener Cleanups Greenhouse Gas (GHG) Emissions and Removals Greenhouse Gas Reporting Program (GHGRP) Greening EPA Ground Water and Drinking Water Ground-level Ozone Pollution H Harmful Algal Blooms (HABs) in Water Bodies Hazardous Air Pollutants Hazardous Air Pollutants: Ethylene Oxide (EtO) Hazardous Waste Hazardous Waste Generators Hazardous Waste Permitting Hazardous Waste Test Methods / SW-846 Health of the Salish Sea Ecosystem Report Health Research Healthy Child Care Healthy School Environments Healthy Watersheds Protection Heat Island Effect High-End Scientific Computing Household Medication Disposal Hudson River PCBs Superfund Site Hurricane Response Hydrologic Modeling Community of Practice I Importing or Exporting Chemical Substances under TSCA Importing Vehicles and Engines into the United States Incorporating Energy Efficiency and Renewable Energy into State and Tribal Implementation Plans Indian Environmental General Assistance Program (GAP) Indoor Air Quality (IAQ) Indoor Air Quality Tools for Schools Indoor AirPlus Inflation Reduction Act Information Collection Request (ICR) Center Information for Individuals with Limited English Proficiency Infrastructure Investment and Jobs Act Ingredients Used in Pesticide Products Innovation at EPA Integrated Pest Management Integrated Risk Information System Integrated Science Assessments (ISAs) Interagency Steering Committee on Radiation Standards (ISCORS) International Cooperation Investigating for Possible Contamination in Norwood, Pennsylvania Investigating for Possible Contamination in the East Avenue Study Area L Lake Tahoe Land and Waste Management Research Land Revitalization Landfill Methane Outreach Program (LMOP) Landfills Lapses in Appropriation Large-Scale Residential Demolition Laws & Regulations Lead Lead (Pb) Air Pollution Learning and Teaching about the Environment Lindsay Light Superfund Sites M Managing and Transforming Waste Streams: A Tool for Communities Marine Protection Permitting Maui Wildfires Mercury Methane Emissions from the Oil and Gas Sector Methods Approved to Analyze Drinking Water Samples to Ensure Compliance with Regulations Minimum Risk Pesticides Exempted from FIFRA Registration Mississippi River/Gulf of America Hypoxia Task Force Mobile Source Pollution and Related Health Effects Mold Monitoring Unregulated Contaminants in Drinking Water Mosquito Control Motor Vehicle Air Conditioner (MVAC) System Servicing MOVES and Mobile Source Emissions Research N National Air Quality: Status and Trends of Key Air Pollutants National Air Toxics Assessment National Aquatic Resource Surveys National Drinking Water Advisory Council (NDWAC) National Environmental Policy Act National Pollutant Discharge Elimination System (NPDES) National Security National Service Center for Environmental Publications National Water Program Performance Natural Disasters Navajo Nation: Cleaning Up Abandoned Uranium Mines New Source Review (NSR) Permitting Newsroom Nitrogen Dioxide (NO2) Pollution Non-CO2 Greenhouse Gas Emission Projections & Mitigation Nonattainment Areas for Criteria Pollutants (Green Book) NPDES Permits around the Nation Nutrient Pollution O Occupational Pesticide Safety and Health Ocean and Coastal Acidification Office of Finance and Administration Policies Oil Spill Prevention and Preparedness Regulations One Health Operating Permits Issued under Title V of the Clean Air Act Organon Overview of the Clean Air Act and Air Pollution Ozone and Your Patients' Health Ozone Layer Protection Ozone Layer Protection Milestones of the Clean Air Act P Pacific Southwest (Region 9) Media Center Participatory Science for Environmental Protection Particle Pollution and Your Patients' Health Particulate Matter (PM) Pollution People, Prosperity and the Planet (P3) Student Design Competition Per- and Polyfluoroalkyl Substances (PFAS) Permitting at EPA Permitting Under the Clean Air Act Pest Control and Pesticide Safety for Consumers Pesticide Advisory Committees and Regulatory Partners Pesticide Contacts and Organizational Information Pesticide Environmental Stewardship Program (PESP) Pesticide Labels Pesticide Registration Pesticide Registration Improvement Act Pesticide Science and Assessing Pesticide Risks Pesticides Petitions Phaseout of Ozone-Depleting Substances (ODS) Planning, Budget, and Results Polluted Runoff: Nonpoint Source (NPS) Pollution Pollution Prevention (P2) Polychlorinated Biphenyls (PCBs) Ports Initiative Power Sector Modeling Predictive Models and Tools for Assessing Chemicals under the Toxic Substances Control Act (TSCA) Private Drinking Water Wells Programs and Projects of the Office of General Counsel (OGC) Protecting Bees and Other Pollinators from Pesticides Protecting Children's Environmental Health Protecting Endangered Species from Pesticides Protecting Our Climate by Reducing Use of HFCs Protecting Pets from Fleas and Ticks Protecting Underground Sources of Drinking Water from Underground Injection (UIC) Provisional Peer-Reviewed Toxicity Values (PPRTVs) Public notices at U.S. EPA Puget Sound R Radiation Protection Radiological Preparedness & Response: Advisory Team for Environment, Food and Health RadNet Radon RadTown RE-Powering America's Land Red Hill Bulk Fuel Storage Facility in Hawai'i Reduce, Reuse, Recycle Reducing Pesticide Drift Reevaluation: Review of Registered Pesticides Region 3 Documents Regional Streamflow Duration Assessment Methods Regulation of Biotechnology under TSCA and FIFRA Regulation of Pesticide Residues on Food Regulations for Emissions from Vehicles and Engines Regulatory and Guidance Information By Topic Regulatory Flexibility for Small Entities Regulatory Information By Business Sector Renewable Fuel Standard Repellents: Protection against Mosquitoes, Ticks and Other Arthropods Report a Violation Reporting Unintended Exposure and Harm from Pesticides (Incidents) Research Research Fellowships Research Grants Research Milestones Resource Conservation and Recovery Act (RCRA) Laws and Regulations Resources for Small Businesses Restoration and Protection Screening Restoration of the Florida Everglades Restoring the Gulf of America After the Deepwater Horizon Oil Spill Reviewing National Ambient Air Quality Standards (NAAQS): Scientific and Technical Information Reviewing New Chemicals under the Toxic Substances Control Act (TSCA) Risk Assessment Risk Communication Risk Management Program (RMP) Rule Risk-Screening Environmental Indicators (RSEI) Model S Safe Drinking Water Act (SDWA) Safe Drinking Water Act: Consumer Confidence Reports (CCR) Safe Drinking Water on Tribal Lands Safer Chemicals Research Safer Choice San Francisco Bay Delta Watershed San Francisco Bay Program San Joaquin Valley San Juan Watershed Scientific Diving Scientific Integrity Scientific Leadership Section 401 of the Clean Water Act Section 404 of the Clean Water Act: Permitting Discharges of Dredge or Fill Material Senior Leaders' Calendars Septic Systems (Decentralized/Onsite Systems) Significant New Alternatives Policy (SNAP) Program Silver Bow Creek - Butte Area Site Six-Year Review of Drinking Water Standards Small and Rural Wastewater Systems Small Business Innovation Research (SBIR) Program Smart Growth SmartWay Soak Up the Rain Soil Fumigant Toolbox Sole Source Aquifers for Drinking Water Source Water Protection South Florida Program (SFP) Southeast New England Program State and Local Transportation Resources Stationary Refrigeration and Air Conditioning Stationary Sources of Air Pollution Sulfur Dioxide (SO2) Pollution Sun Safety Superfund Superfund Contract Laboratory Program Superfund Redevelopment Program Support Center for Regulatory Atmospheric Modeling (SCRAM) Surface Coal Mining in Appalachia Sustainability Sustainable Futures Sustainable Management of Electronics and Batteries Sustainable Management of Food Sustainable Management of Plastics Sustainable Marketplace: Greener Products and Services Sustainable Materials Management Sustainable Water Infrastructure T Technologies for Cleaning Up Contaminated Sites Test Guidelines for Pesticides and Toxic Substances The EPA Automotive Trends Report The Federal Technology Transfer Act (FTTA) The Great Lakes The Hazardous Waste Electronic Manifest (e-Manifest) System Toxic Substances Control Act (TSCA) Administration Fees Toxics Release Inventory (TRI) Program Transportation, Air Pollution and Climate Change Trash Free Waters TRI National Analysis Tribal Air and Climate Resources Tribal Programs in EPA's Pacific Southwest (Region 9) Tribal Programs in the Pacific Northwest and Alaska Tribal Science Council: Research and Resources to Support Tribes TSCA Chemical Substance Inventory TSCA Scientific Peer Review Committees U U.S. Environmental Protection Agency U.S.-Mexico Border Program Underground Storage Tanks (USTs) Urban River: Merrimack River Urban Waters - Neponset River Urban Waters - The Mystic River Watershed Urban Waters Federal Partnership US EPA's Web Analytics USS Lead Superfund Site V Vapor Intrusion Vehicle and Fuel Emissions Testing Vehicles and Engines Verified Technologies for SmartWay and Clean Diesel Vessels, Marinas and Ports Violations, Recalls and other Compliance Actions of Vehicles and Engines Visibility and Regional Haze Volkswagen Light Duty Diesel Vehicle Violations for Model Years 2009-2016 Voluntary Consensus Standards W Waste Reduction Model Water as a Climate Change Solution Water Data and Tools Water Infrastructure Water Infrastructure and Resiliency Finance Center Water Infrastructure Finance and Innovation Act (WIFIA) Water Pollution Control (Section 106) Grants Water Quality Criteria Water Quality Standards: Regulations and Resources Water Research Water Reuse and Recycling Waters of the United States WaterSense Watershed Academy Web Guide Web Guide: Policies and Procedures WebCMS Training West Coast Collaborative: Partnering to Reduce Diesel Emissions Wetlands Protection and Restoration Wildfire Smoke and Your Patients' Health Wyckoff/Eagle Harbor Superfund site Assistance Spanish Arabic Chinese (simplified) Chinese (traditional) French Haitian Creole Korean Portuguese Russian Tagalog Vietnamese Discover. Accessibility Statement EPA Administrator Budget & Performance Contracting EPA www Web Snapshot Grants No FEAR Act Data Plain Writing Privacy and Security Notice Connect. Data Inspector General Jobs Newsroom Regulations.gov Subscribe USA.gov White House Ask. Contact EPA EPA Disclaimers Hotlines FOIA Requests Frequent Questions Site Feedback Follow. | 2026-01-13T08:48:28 |
https://stackoverflow.blog/engineering/ | Engineering - Stack Overflow Blog Loading… Everything Productivity AI/ML Open Source Business Hub Company Releases Podcast Newsletter Stack Overflow Business Stack Internal : the knowledge intelligence layer that powers enterprise AI. Stack Data Licensing : decades of verified, technical knowledge to boost AI performance and trust. Stack Ads : engage developers where it matters — in their daily workflow. Engineering Related Tags cloud Leaders of code Business Hub Stack Internal Code for a Living the stack overflow podcast Subscribe to the podcast Get The Stack Overflow Podcast at your favorite listening service. Apple Podcasts Overcast Overcast Pocket Casts Spotify RSS feed December 31, 2025 A look under the hood: How (and why) we built Question Assistant Evaluating question quality and determining the appropriate feedback required some classic ML techniques in addition to our GenAI solution. Derek Cheng , Caroline Thomas , Ryan Donovan 3 comment s questions staging ground Question Assistant AI ML Engineering December 24, 2025 The Great Unracking: Saying goodbye to the servers at our physical datacenter So long and thanks for all the bits! Ryan Donovan 17 comment s Server cloud Engineering May 12, 2025 Beyond speed: Measuring engineering success by impact, not velocity If velocity is just a tool and not a goal, how do you measure real success for engineering teams? Phoebe Sajor 3 comment s Leaders of code Business Hub software development Engineering velocity development velocity metrics April 28, 2025 Banking on innovation: Engineering excellence in regulated financial services Financial institutions face a balancing act between tech innovation and strict regulations. As customer expectations for improved user experience and demands from those tasked with enhancing features keep rising, engineering teams need to find a harmonious middle ground. Katja Skafar , Susi O'Neill 1 comment Leaders of code Business Hub software development Engineering April 16, 2025 Engineering teams need to adapt to AI’s scaling challenges AI is not a linear process. To scale effectively, engineering leaders must account for varied edge cases, presenting a new set of challenges. Katja Skafar , Susi O'Neill Business Hub Leaders of code engineering leadership Engineering generative AI December 31, 2024 Generative AI is not going to build your engineering team for you It’s easy to generate code, but not so easy to generate good code. Charity Majors 20 comment s generative AI Engineering coding Business Hub contributed November 7, 2023 He helped create Jira. Now he's searching for meaningful engineering metrics Dylan Etkin, founder and CEO of Sleuth, joins Ryan to talk all things engineering efficiency, DORA metrics, continuous delivery, and how his psychology degree has proven useful in his work as an engineering manager and startup founder. Eira May 0 comment s devops jira Engineering engineering leadership metrics The Stack Overflow Podcast September 5, 2023 Journey to the cloud part II: Migrating Stack Overflow for Teams to Azure We needed to remove the dependency on the Sites database and contain all Teams infrastructure and data within the TFZ which is all part of Phase II. Wouter de Kort 3 comment s cloud azure Stack Internal Engineering August 30, 2023 Journey to the cloud part I: Migrating Stack Overflow Teams to Azure Stack Overflow for Teams' journey to the cloud started with a new name. Wouter de Kort 1 comment Engineering Code for a Living cloud Stack Internal March 21, 2023 What our engineers learned building Stack Overflow (Ep. 551) Charles “Cobih” Obih and Radek Markiewicz of the Stack Overflow platform team join Ben and Ryan to talk about changes to the inbox and what it’s like to build Stack Overflow’s public platform. Eira May 0 comment s Engineering platform platform engineering the stack overflow podcast The Stack Overflow Podcast February 24, 2023 ML and AI consulting-as-a-service (Ep. 542) The home team talks with Jaclyn Rice Nelson, cofounder and CEO of Tribe AI, about the explosion of hype surrounding generative AI, what it’s like to work at a startup after working at Google, and how Tribe is leveraging the power of a specialist network. Eira May 0 comment s AI data science Engineering machine learning ML the stack overflow podcast The Stack Overflow Podcast tribe ai July 4, 2022 How Stack Overflow is leveling up its unit testing game We neglected unit tests for a long time because our code base made them difficult. But now we're putting in the work to change that. Wouter de Kort 13 comment s Code for a Living Engineering testing unit tests May 16, 2022 Stack under attack: what we learned about handling DDoS attacks When the bots came for us, we strengthened our defenses. Here's what we learned about parrying a few DDoS attacks. Josh Zhang 8 comment s Code for a Living DDoS devops Engineering security January 24, 2022 Securing the data in your online code repository is a shared responsibility What would you do if your code repositories suddenly stopped working? James Ciesielski, 2 comment s backups Code for a Living code repositories Engineering Partner Content partnercontent December 22, 2021 Best practices can slow your application down In order to get the most performant site possible when building the codebase for our public Stack Overflow site, we didn’t always follow best practices. Roberta Arcoverde , Ryan Donovan 54 comment s best practices Code for a Living Engineering Engineering performance May 31, 2021 CSS in SVG in CSS: Shipping confetti to Stack Overflow’s design system Stack Overflow celebrates site accomplishments with confetti in multiple places. That means it's time to formalize it in our design system. Aaron Shekey 6 comment s css Engineering stacks May 14, 2021 Podcast 338: Why is it so hard to find Ruby developers? Your early developers loved Ruby, so you center your company around that. Now you can't find young talent. Ben Popper 3 comment s Engineering ruby The Stack Overflow Podcast the stack overflow podcast February 23, 2021 Level Up: Mastering statistics with Python - part 2 Investigate a dataset with summary statistics and some basic data visualizations using the Python libraries NumPy, pandas, matplotlib, and Seaborn. Ben Popper , Sophie Sommer 0 comment s Code for a Living codecademy data science Engineering statistics January 25, 2021 A deeper dive into our May 2019 security incident We take a detailed look at a hacking incident that gave a user unauthorized access to our code and data. Dean Ward Company Engineering Legal security October 23, 2020 Failing over without falling over You’ve gone through the motions and play-acted a disaster recovery scenario, but despite spending a lot on the production, it’s not real. What you have is a fairy tale: “Once upon a time, in theory, if everything works perfectly, we have a plan to survive the disasters we thought of in advance.” In practice, it’s more likely to be a nightmare. Adrian Cockcroft 0 comment s aws chaos engineering Code for a Living Engineering failover Partner Content Partner Content partnercontent August 12, 2020 How we built it: our new Articles feature for Stack Overflow for Teams Roberta Arcoverde, tech lead for Stack Overflow Teams, provides a deep dive into the decisions that shaped the architecture of Articles, an entirely new content type. Roberta Arcoverde 10 comment s Code for a Living Company Engineering product Stack Internal Stackoverflow April 24, 2020 Podcast 229: Jokes On Us Tune in for part two of our conversation with Adam Lear and Jon Chan, Stack Overflow developers working on our public sites and community tools. Ben Popper 1 comment Bulletin Community Community Engineering Engineering Stackoverflow Stackoverflow the stack overflow podcast The Stack Overflow Podcast April 21, 2020 Podcast 228: chatting with Stack Overflow's community developers On this episode of the podcast, we chat with two of the Stack Overflow developers working on our public sites and community tools. Ben Popper 4 comment s Bulletin Community Engineering stack exchange Stackexchange Stackoverflow Stackoverflow The Stack Overflow Podcast the stack overflow podcast April 9, 2020 The Unfriendly Robot: Automatically flagging unwelcoming comments Unfriendly comments are an issue in our system because of the effect that their tone has on their recipient’s and future readers’ willingness to contribute to Stack Overflow. The solution to these issues isn’t to argue about circumstance or intent. The only remaining option is to work on the comments themselves. Jason Punyon , Kevin Montrose 1 comment bots Community Community Engineering Stackoverflow Stackoverflow Show more Our Stack Stack Internal Features Customers Security Pricing Stack Data Licensing Stack Ads Partnerships Services Stack Overflow Company Leadership Press Careers Social Impact Support Contact Stack Overflow help Stack Internal help Terms Privacy policy Cookie policy Your Privacy Choices Elsewhere Blog Dev Newsletter Podcast Releases Dev Survey Site design / logo © 2026 Stack Exchange Inc. Light Dark Auto | 2026-01-13T08:48:28 |
https://unpkg.com | UNPKG UNPKG UNPKG is a fast, global content delivery network for everything on npm . Use it to quickly and easily load any file on npm using a URL like: unpkg.com/:pkg@:ver/:file https://unpkg.com/:package@:version/:file :pkg :package is the name of the package on npm :ver :version is the version of the package :file is the path to a file in the package For example: unpkg.com/preact@10.26.4/dist/preact.min.js unpkg.com/react@18.3.1/umd/react.production.min.js unpkg.com/three@0.174.0/build/three.module.min.js You can also use any valid semver range or npm tag : unpkg.com/preact@latest/dist/preact.min.js unpkg.com/react@^18/umd/react.production.min.js If you don't specify a version, the latest tag is used by default. unpkg.com/preact/dist/preact.min.js unpkg.com/vue/dist/vue.esm-browser.prod.js Add a trailing / to a directory URL to view a listing of all the files in that directory. unpkg.com/react/ unpkg.com/preact/src/ unpkg.com/react-router/ If you'd like to browse an older version of a package, include a version number in the URL. unpkg.com/react@18/ unpkg.com/react-router@5/ If you don't specify a file path, UNPKG will resolve the file based on the package's default entry point . In many packages that are meant solely for frontend development, like jQuery and GSAP, this will be the value of the main field in the package.json file. unpkg.com/jquery unpkg.com/gsap In modern packages that use the exports field , UNPKG will resolve the file using the default export condition . So, for example if you publish a package with the following package.json : { "name" : "my-package" , "exports" : { "default" : "./dist/index.js" } } You would be able to load your package from UNPKG using a <script> tag like: < script src = "https://unpkg.com/my-package" > </ script > The full exports spec is supported, including subpaths. So if your package.json looks like: { "name" : "my-package" , "exports" : { "./exp" : { "default" : "./dist/exp.js" } } } You can load the exp subpath with: < script src = "https://unpkg.com/my-package/exp" > </ script > Custom export conditions are supported via the ?conditions query parameter. This allows you to load a different file based on the environment or other conditions. For example, to fetch React using the react-server condition, you could do: fetch ("https://unpkg.com/react?conditions=react-server") If you'd like to specify a custom build of your package that should be used as the default entry point on UNPKG, you can use either the unpkg field in your package.json or the unpkg export condition in your exports field. { "name" : "my-package" , "unpkg" : "./dist/index.unpkg.js" , // This works "exports" : { "unpkg" : "./dist/index.unpkg.js" // This works, too "default" : "./dist/index.js" } } Nobuild Apps UNPKG is ideal for loading dependencies in apps that run entirely in the browser without a build step. You can load JavaScript modules from UNPKG directly in your HTML using an import map . Below is a fully functional Preact app that does not require a build in order to run. <!doctype html > < html lang = "en" > < head > < meta charset = "UTF-8" /> < script type = "importmap" > { "imports" : { "preact" : "https://unpkg.com/preact@10.25.4/dist/preact.module.js" , "preact/hooks" : "https://unpkg.com/preact@10.25.4/hooks/dist/hooks.module.js" , "htm" : "https://unpkg.com/htm@3.1.1/dist/htm.module.js" } } </ script > </ head > < body > < script type = "module" > import { h, render } from "preact" ; import { useState } from "preact/hooks" ; import htm from "htm" ; const html = htm. bind (h); function App ( ) { let [count, setCount] = useState ( 0 ); return html` < div > < p > Count: ${count} </ p > < button onClick = ${() => setCount(count + 1 )} > Increment </ button > </ div > ` ; } render (html` < ${App} />` , document . body ); </ script > </ body > </ html > No bundler required! This is ideal for small projects, prototypes, or any situation where you'd like to get something up and running quickly without setting up a build pipeline. Metadata API UNPKG serves metadata about the files in a package when you append ?meta to any package root or subdirectory URL. For example: unpkg.com/react-router@7.3.0/?meta unpkg.com/react-router@7.3.0/dist/?meta This will return a JSON object with information about the files in that directory, including path, size, type, and subresource integrity value. { package: "react-router" , version: "7.3.0" , prefix: "/dist/" , files: [ { path : "/dist/development/dom-export.js" , size: 195045 , type: "text/javascript" , integrity: "sha256-z5j8OHOsGkvfGAjBtW8sbj+M68LLmgLTSjDHk4A5uYA=" }, { path : "/dist/production/dom-export.js" , size: 195047 , type: "text/javascript" , integrity: "sha256-Gh8wMHW9MO5IMaBq7fOc7szDMRemnO/7Qr8kTK4ebgY=" }, // ... ] } Cache Performance UNPKG is a mirror of everything on npm. Every file on npm is automatically available on unpkg.com within minutes of being published. Additionally, UNPKG runs on Cloudflare's global edge network using Cloudflare Workers , which allow UNPKG to serve billions of requests every day with low latency from hundreds of locations worldwide. The "serverless" nature of Cloudflare Workers also allows UNPKG to scale immediately to satisfy sudden spikes in traffic. Files are cached on Cloudflare's global content-delivery network based on their permanent URL, which includes the npm package version. This works because npm does not allow package authors to overwrite a package that has already been published with a different one at the same version number. URLs that do not specify a fully resolved package version number redirect to one that does. This is the latest version when none is specified, or the maximum satisfying version when a semver range is given. For the best chance of getting a cache hit, use the full package version number and file path in your UNPKG URLs instead of an npm tag or semver range . For example, a URL like unpkg.com/preact@10 will not be a direct cache hit because UNPKG needs to resolve the version 10 to the latest matching version of Preact published with that major, plus it needs to figure out which file to serve. So a short URL like this will always cause a redirect to the permanent URL for that resource. If you need to make sure you hit the cache, use a fixed version number and the full file path, like unpkg.com/preact@10.5.0/dist/preact.min.js . About UNPKG is an open source project from @mjackson . UNPKG is not affiliated with or supported by npm in any way. Please do not contact npm for help with UNPKG. Instead, please reach out to @unpkg with any questions or concerns. Overview Nobuild Apps Metadata API Cache Performance About | 2026-01-13T08:48:28 |
https://www.linkedin.com/legal/user-agreement?trk=public_profile_auth-button_user-agreement | User Agreement | LinkedIn Skip to main content User Agreement Summary of User Agreement Privacy Policy Professional Community Policies Cookie Policy Copyright Policy Regional Info EU Notice California Privacy Disclosure U.S. State Privacy Laws User Agreement Summary of User Agreement Privacy Policy Professional Community Policies Cookie Policy Copyright Policy Regional Info EU Notice California Privacy Disclosure U.S. State Privacy Laws User Agreement Effective on November 3, 2025 Our mission is to connect the world’s professionals to allow them to be more productive and successful. Our services are designed to promote economic opportunity for our members by enabling you and millions of other professionals to meet, exchange ideas, learn, and find opportunities or employees, work, and make decisions in a network of trusted relationships. Table of Contents: Introduction Obligations Rights and Limits Disclaimer and Limit of Liability Termination Governing Law and Dispute Resolution General Terms LinkedIn “Dos and Don’ts” Complaints Regarding Content How To Contact Us Introduction 1.1 Contract When you use our Services you agree to all of these terms. Your use of our Services is also subject to our Cookie Policy and our Privacy Policy, which covers how we collect, use, share, and store your personal information. By creating a LinkedIn account or accessing or using our Services (described below), you are agreeing to enter into a legally binding contract with LinkedIn (even if you are using third party credentials or using our Services on behalf of a company). If you do not agree to this contract (“Contract” or “User Agreement”), do not create an account or access or otherwise use any of our Services. If you wish to terminate this Contract at any time, you can do so by closing your account and no longer accessing or using our Services. As a Visitor or Member of our Services, the collection, use, and sharing of your personal data is subject to our Privacy Policy , our Cookie Policy and other documents referenced in our Privacy Policy , and updates. You acknowledge and have read our Privacy Policy . Services This Contract applies to LinkedIn.com, LinkedIn-branded apps, and other LinkedIn-related sites, apps, communications, and other services that state that they are offered under this Contract (“Services”), including the offsite collection of data for those Services, such as via our ads and the “Apply with LinkedIn” and “Share with LinkedIn” plugins. LinkedIn and other Key Terms You are entering into this Contract with LinkedIn (also referred to as “we” and “us”). Designated Countries . We use the term “Designated Countries” to refer to countries in the European Union (EU), European Economic Area (EEA), and Switzerland. If you reside in the “Designated Countries”, you are entering into this Contract with LinkedIn Ireland Unlimited Company (“LinkedIn Ireland”) and LinkedIn Ireland will be the controller of your personal data provided to, or collected by or for, or processed in connection with our Services. If you reside outside of the “Designated Countries”, you are entering into this Contract with LinkedIn Corporation (“LinkedIn Corp.”) and LinkedIn Corp. will be the controller of (or business responsible for) your personal data provided to, or collected by or for, or processed in connection with our Services. Affiliates . Affiliates are companies controlling, controlled by or under common control with us, including, for example, LinkedIn Ireland, LinkedIn Corporation, LinkedIn Singapore and Microsoft Corporation or any of its subsidiaries (e.g., Github, Inc.). Social Action . Actions that members take on our services such as likes, comments, follows, sharing content. Content . Content includes, for example, feed posts, feedback, comments, profiles, articles (and contributions), group posts, job postings, messages (including InMails), videos, photos, audio, and/or PDFs. 1.2 Members and Visitors This Contract applies to Members and Visitors. When you register and join the LinkedIn Services, you become a “Member”. If you have chosen not to register for our Services, you may access certain features as a “Visitor.” 1.3 Changes We may make changes to this Contract. We may modify this Contract, our Privacy Policy and our Cookie Policy from time to time. If we materially change these terms or if we are legally required to provide notice, we will provide you notice through our Services, or by other means, to provide you the opportunity to review the changes before they become effective. However, we may not always provide prior notice of changes to these terms (1) when those changes are legally required to be implemented with immediate effect, or (2) when those changes relate to a newly launched service or feature. We agree that changes cannot be retroactive. If you object to any of these changes, you may close your account . Your continued use of our Services after we publish or send a notice about our changes to these terms means that you are consenting to the updated terms as of their effective date. 2. Obligations 2.1 Service Eligibility Here are some promises that you make to us in this Contract: You’re eligible to enter into this Contract and you are at least our “Minimum Age.” The Services are not for use by anyone under the age of 16. To use the Services, you agree that: (1) you must be the "Minimum Age" (described below) or older; (2) you will only have one LinkedIn account, which must be in your real name; and (3) you are not already restricted by LinkedIn from using the Services. Creating an account with false information is a violation of our terms, including accounts registered on behalf of others or persons under the age of 16. “Minimum Age” means 16 years old. However, if law requires that you must be older in order for LinkedIn to lawfully provide the Services to you without parental consent (including using your personal data) then the Minimum Age is such older age. Learn More 2.2 Your Account You will keep your password a secret You will not share your account with anyone else and will follow our policies and the law. Members are account holders. You agree to: (1) protect against wrongful access to your account (e.g., use a strong password and keep it confidential); (2) not share or transfer your account or any part of it (e.g., sell or transfer the personal data of others by transferring your connections); and (3) follow the law, our list of Dos and Don’ts (below), and our Professional Community Policies . Learn More You are responsible for anything that happens through your account unless you close it or report misuse. As between you and others (including your employer), your account belongs to you. However, if the Services were purchased by another party for you to use in connection with your work for them (e.g., Recruiter seat or LinkedIn Learning subscription bought by your employer), the party paying for such Service has the right to control access to and get reports on your use of such paid Service; however, they do not have rights to your personal account. 2.3 Payment You’ll honor your payment obligations and you are okay with us storing your payment information. You understand that there may be fees and taxes that are added to our prices. Refunds are subject to our policy, and we may modify our prices and those modified prices will apply prospectively. If you buy any of our paid Services, you agree to pay us the applicable fees and taxes and you agree to the additional terms specific to the paid Services. Failure to pay these fees will result in the termination of your paid Services. Also, you agree that: Your purchase may be subject to foreign exchange fees or differences in prices based on location (e.g., exchange rates). We may store and continue billing your payment method (e.g., credit card), even after it has expired, to avoid interruptions in your paid Services and to use it to pay for other Services you may buy. If your primary payment method fails, we may automatically charge a secondary payment method, if you have provided one. You may update or change your payment method. Learn more If you purchase a subscription, your payment method automatically will be charged at the start of each subscription period for the fees and taxes applicable to that period. To avoid future charges, cancel before the renewal date. Learn how to cancel or suspend your paid subscription Services. We may modify our prices effective prospectively upon reasonable notice to the extent allowed under the law. All of your paid Services are subject to LinkedIn’s refund policy . We may calculate taxes payable by you based on the billing information that you provide us. You can get a copy of your invoice through your LinkedIn account settings under “ Purchase History ”. 2.4 Notices and Messages You’re okay with us providing notices and messages to you through our websites, apps, and contact information. If your contact information is out of date, you may miss out on important notices. You agree that we will provide notices and messages to you in the following ways: (1) within the Services or (2) sent to the contact information you provided us (e.g., email, mobile number, physical address). You agree to keep your contact information up to date. Please review your settings to control and limit the types of messages you receive from us. 2.5 Sharing When you share information on our Services, others can see, copy and use that information. Our Services allow sharing of information (including content) in many ways, such as through your profile, posts, articles, group posts, links to news articles, job postings, messages, and InMails. Depending on the feature and choices you make, information that you share may be seen by other Members, Visitors, or others (on or off of the Services). Where we have made settings available, we will honor the choices you make about who can see content or other information (e.g., message content to your addressees, sharing content only to LinkedIn connections, restricting your profile visibility from search tools, or opting not to notify others of your LinkedIn profile update). For job searching activities, we default to not notifying your connections or the public. So, if you apply for a job through our Services or opt to signal that you are interested in a job, our default is to share it only with the job poster. To the extent that laws allow this, we are not obligated to publish any content or other information on our Services and can remove it with or without notice. 3. Rights and Limits 3.1. Your License to LinkedIn You own all of your original content that you provide to us, but you also grant us a non-exclusive license to it. We’ll honor the choices you make about who gets to see your content, including how it can be used for ads. As between you and LinkedIn, you own your original content that you submit or post to the Services. You grant LinkedIn and our Affiliates the following non-exclusive license to the content and other information you provide (e.g., share, post, upload, and/or otherwise submit) to our Services: A worldwide, transferable and sublicensable right to use, copy, modify, distribute, publicly perform and display, host, and process your content and other information without any further consent, notice and/or compensation to you or others. These rights are limited in the following ways: You can end this license for specific content by deleting such content from the Services, or generally by closing your account, except (a) to the extent you (1) shared it with others as part of the Services and they copied, re-shared it or stored it, (2) we had already sublicensed others prior to your content removal or closing of your account, or (3) we are required by law to retain or share it with others, and (b) for the reasonable time it takes to remove the content you delete from backup and other systems. We will not include your content in advertisements for the products and services of third parties to others without your separate consent (including sponsored content). However, without compensation to you or others, ads may be served near your content and other information, and your social actions may be visible and included with ads, as noted in the Privacy Policy. If you use a Service feature, we may mention that with your name or photo to promote that feature within our Services, subject to your settings. We will honor the audience choices for shared content (e.g., “Connections only”). For example, if you choose to share your post to "Anyone on or off LinkedIn” (or similar): (a) we may make it available off LinkedIn; (b) we may enable others to publicly share onto third-party services (e.g., a Member embedding your post on a third party service); and/or (c) we may enable search tools to make that public content findable though their services. Learn More While we may edit and make format changes to your content (such as translating or transcribing it, modifying the size, layout or file type, and removing or adding labels or metadata), we will take steps to avoid materially modifying the meaning of your expression in content you share with others. Because you own your original content and we only have non-exclusive rights to it, you may choose to make it available to others, including under the terms of a Creative Commons license . You and LinkedIn agree that if content includes personal data, it is subject to our Privacy Policy. You and LinkedIn agree that we may access, store, process, and use any information (including content and/or personal data) that you provide in accordance with the terms of the Privacy Policy and your choices (including settings). By submitting suggestions or other feedback regarding our Services to LinkedIn, you agree that LinkedIn can use and share (but does not have to) such feedback for any purpose without compensation to you. You promise to only provide content and other information that you have the right to share and that your LinkedIn profile will be truthful. You agree to only provide content and other information that does not violate the law or anyone’s rights (including intellectual property rights). You have choices about how much information to provide on your profile but also agree that the profile information you provide will be truthful. LinkedIn may be required by law to remove certain content and other information in certain countries. 3.2 Service Availability We may change or limit the availability of some features, or end any Service. We may change, suspend or discontinue any of our Services. We may also limit the availability of features, content and other information so that they are not available to all Visitors or Members (e.g., by country or by subscription access). We don’t promise to store or show (or keep showing) any information (including content) that you’ve shared. LinkedIn is not a storage service. You agree that we have no obligation to store, maintain or provide you a copy of any content or other information that you or others provide, except to the extent required by applicable law and as noted in our Privacy Policy. 3.3 Other Content, Sites and Apps Your use of others’ content and information posted on our Services, is at your own risk. Others may offer their own products and services through our Services, and we aren’t responsible for those third-party activities. Others’ Content: By using the Services, you may encounter content or other information that might be inaccurate, incomplete, delayed, misleading, illegal, offensive, or otherwise harmful. You agree that we are not responsible for content or other information made available through or within the Services by others, including Members. While we apply automated tools to review much of the content and other information presented in the Services, we cannot always prevent misuse of our Services, and you agree that we are not responsible for any such misuse. You also acknowledge the risk that others may share inaccurate or misleading information about you or your organization, and that you or your organization may be mistakenly associated with content about others, for example, when we let connections and followers know you or your organization were mentioned in the news. Members have choices about this feature . Others’ Products and Services: LinkedIn may help connect you to other Members (e.g., Members using Services Marketplace or our enterprise recruiting, jobs, sales, or marketing products) who offer you opportunities (on behalf of themselves, their organizations, or others) such as offers to become a candidate for employment or other work or offers to purchase products or services. You acknowledge that LinkedIn does not perform these offered services, employ those who perform these services, or provide these offered products. You further acknowledge that LinkedIn does not supervise, direct, control, or monitor Members in the making of these offers, or in their providing you with work, delivering products or performing services, and you agree that (1) LinkedIn is not responsible for these offers, or performance or procurement of them, (2) LinkedIn does not endorse any particular Member’s offers, and (3) LinkedIn is not an agent or employment agency on behalf of any Member offering employment or other work, products or services. With respect to employment or other work, LinkedIn does not make employment or hiring decisions on behalf of Members offering opportunities and does not have such authority from Members or organizations using our products. For Services Marketplace , (a) you must be at least 18 years of age to procure, offer, or perform services, and (b) you represent and warrant that you have all the required licenses and will provide services consistent with the relevant industry standards and our Professional Community Policies . Others’ Events: Similarly, LinkedIn may help you register for and/or attend events organized by Members and connect with other Members who are attendees at such events. You agree that (1) LinkedIn is not responsible for the conduct of any of the Members or other attendees at such events, (2) LinkedIn does not endorse any particular event listed on our Services, (3) LinkedIn does not review and/or vet any of these events or speakers, and (4) you will adhere to the terms and conditions that apply to such events. 3.4 Limits We have the right to limit how you connect and interact on our Services. LinkedIn reserves the right to limit your use of the Services, including the number of your connections and your ability to contact other Members. LinkedIn reserves the right to restrict, suspend, or terminate your account if you breach this Contract or the law or are misusing the Services (e.g., violating any of the Dos and Don’ts or Professional Community Policies ). We can also remove any content or other information you shared if we believe it violates our Professional Community Policies or Dos and Don’ts or otherwise violates this Contract. Learn more about how we moderate content. 3.5 Intellectual Property Rights We’re providing you notice about our intellectual property rights. LinkedIn reserves all of its intellectual property rights in the Services. Trademarks and logos used in connection with the Services are the trademarks of their respective owners. LinkedIn, and “in” logos and other LinkedIn trademarks, service marks, graphics and logos used for our Services are trademarks or registered trademarks of LinkedIn. 3.6 Recommendations and Automated Processing We use data and other information about you to make and order relevant suggestions and to generate content for you and others. Recommendations: We use the data and other information that you provide and that we have about Members and content on the Services to make recommendations for connections, content, ads, and features that may be useful to you. We use that data and other information to recommend and to present information to you in an order that may be more relevant for you. For example, that data and information may be used to recommend jobs to you and you to recruiters and to organize content in your feed in order to optimize your experience and use of the Services. Keeping your profile accurate and up to date helps us to make these recommendations more accurate and relevant. Learn More Generative AI Features: By using the Services, you may interact with features we offer that automate content generation for you. The content that is generated might be inaccurate, incomplete, delayed, misleading or not suitable for your purposes. Please review and edit such content before sharing with others. Like all content you share on our Services, you are responsible for ensuring it complies with our Professional Community Policies , including not sharing misleading information. The Services may include content automatically generated and shared using tools offered by LinkedIn or others off LinkedIn. Like all content and other information on our Services, regardless of whether it's labeled as created by “AI”, be sure to carefully review before relying on it. 4. Disclaimer and Limit of Liability 4.1 No Warranty This is our disclaimer of legal liability for the quality, safety, or reliability of our Services. LINKEDIN AND ITS AFFILIATES MAKE NO REPRESENTATION OR WARRANTY ABOUT THE SERVICES, INCLUDING ANY REPRESENTATION THAT THE SERVICES WILL BE UNINTERRUPTED OR ERROR-FREE, AND PROVIDE THE SERVICES (INCLUDING CONTENT, OUTPUT AND INFORMATION) ON AN “AS IS” AND “AS AVAILABLE” BASIS. TO THE FULLEST EXTENT PERMITTED UNDER APPLICABLE LAW, LINKEDIN AND ITS AFFILIATES DISCLAIM ANY IMPLIED OR STATUTORY WARRANTY, INCLUDING ANY IMPLIED WARRANTY OF TITLE, ACCURACY, NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. If you plan to use content, output and information for any reason, it is your responsibility to verify its accuracy and fitness for your purposes, because any content, output and information on the service may not reflect accurate, complete, or current information. 4.2 Exclusion of Liability These are the limits of legal liability we may have to you. TO THE FULLEST EXTENT PERMITTED BY LAW (AND UNLESS LINKEDIN HAS ENTERED INTO A SEPARATE WRITTEN AGREEMENT THAT OVERRIDES THIS CONTRACT), LINKEDIN AND ITS AFFILIATES, WILL NOT BE LIABLE IN CONNECTION WITH THIS CONTRACT FOR LOST PROFITS OR LOST BUSINESS OPPORTUNITIES, REPUTATION (E.G., OFFENSIVE OR DEFAMATORY STATEMENTS), LOSS OF DATA (E.G., DOWN TIME OR LOSS, USE OF, OR CHANGES TO, YOUR INFORMATION OR CONTENT) OR ANY INDIRECT, INCIDENTAL, CONSEQUENTIAL, SPECIAL OR PUNITIVE DAMAGES. LINKEDIN AND ITS AFFILIATES WILL NOT BE LIABLE TO YOU IN CONNECTION WITH THIS CONTRACT FOR ANY AMOUNT THAT EXCEEDS (A) THE TOTAL FEES PAID OR PAYABLE BY YOU TO LINKEDIN FOR THE SERVICES DURING THE TERM OF THIS CONTRACT, IF ANY, OR (B) US $1000. 4.3 Basis of the Bargain; Exclusions The limitations of liability in this Section 4 are part of the basis of the bargain between you and LinkedIn and shall apply to all claims of liability (e.g., warranty, tort, negligence, contract and law) even if LinkedIn or its affiliates has been told of the possibility of any such damage, and even if these remedies fail their essential purpose. THESE LIMITATIONS OF LIABILITY DO NOT APPLY TO LIABILITY FOR DEATH OR PERSONAL INJURY OR FOR FRAUD, GROSS NEGLIGENCE OR INTENTIONAL MISCONDUCT, OR IN CASES OF NEGLIGENCE, WHERE A MATERIAL OBLIGATION HAS BEEN BREACHED. A MATERIAL OBLIGATION BEING AN OBLIGATION WHICH FORMS A PREREQUISITE TO OUR DELIVERY OF SERVICES AND ON WHICH YOU MAY REASONABLY RELY, BUT ONLY TO THE EXTENT THAT THE DAMAGES WERE DIRECTLY CAUSED BY THE BREACH AND WERE FORESEEABLE UPON CONCLUSION OF THIS CONTRACT AND TO THE EXTENT THAT THEY ARE TYPICAL IN THE CONTEXT OF THIS CONTRACT. 5. Termination We can each end this Contract, but some rights and obligations survive. Both you and LinkedIn may terminate this Contract at any time with notice to the other. On termination, you lose the right to access or use the Services. The following shall survive termination: Our rights to use and disclose your feedback; Section 3 (subject to 3.1.1); Sections 4, 6, 7, and 8.2 of this Contract; and Any amounts owed by either party prior to termination remain owed after termination. You can visit our Help Center to learn about how to close your account 6. Governing Law and Dispute Resolution In the unlikely event we end up in a legal dispute, depending on where you live, you and LinkedIn agree to resolve it in California courts using California law, Dublin, Ireland courts using Irish law, or as otherwise provided in this section. If you live in the Designated Countries, the laws of Ireland govern all claims related to LinkedIn's provision of the Services, but this shall not deprive you of the mandatory consumer protections under the law of the country to which we direct your Services where you have habitual residence. With respect to jurisdiction, you and LinkedIn agree to choose the courts of the country to which we direct your Services where you have habitual residence for all disputes arising out of or relating to this User Agreement, or in the alternative, you may choose the responsible court in Ireland. If you are a business user within the scope of Article 6(12) of the EU Digital Markets Act (“DMA”) and have a dispute arising out of or in connection with Article 6(12) of the DMA, you may also utilize the alternative dispute resolution mechanism available in the Help Center . For others outside of Designated Countries, including those who live outside of the United States: You and LinkedIn agree that the laws of the State of California, U.S.A., excluding its conflict of laws rules, shall exclusively govern any dispute relating to this Contract and/or the Services. You and LinkedIn both agree that all claims and disputes can be litigated only in the federal or state courts in Santa Clara County, California, USA, and you and LinkedIn each agree to personal jurisdiction in those courts. You may have additional rights of redress and appeal for some decisions made by LinkedIn that impact you. 7. General Terms Here are some important details about the Contract. If a court with authority over this Contract finds any part of it unenforceable, you and we agree that the court should modify the terms to make that part enforceable while still achieving its intent. If the court cannot do that, you and we agree to ask the court to remove that unenforceable part and still enforce the rest of this Contract. This Contract (including additional terms that may be provided by us when you engage with a feature of the Services) is the only agreement between us regarding the Services and supersedes all prior agreements for the Services. If we don't act to enforce a breach of this Contract, that does not mean that LinkedIn has waived its right to enforce this Contract. You may not assign or transfer this Contract (or your membership or use of Services) to anyone without our consent. However, you agree that LinkedIn may assign this Contract to its affiliates or a party that buys it without your consent. There are no third-party beneficiaries to this Contract. You agree that the only way to provide us legal notice is at the addresses provided in Section 10. 8. LinkedIn “Dos and Don’ts” LinkedIn is a community of professionals. This list of “Dos and Don’ts” along with our Professional Community Policies limits what you can and cannot do on our Services, unless otherwise explicitly permitted by LinkedIn in a separate writing (e.g., through a research agreement). 8.1. Dos You agree that you will: Comply with all applicable laws, including, without limitation, privacy laws, intellectual property laws, anti-spam laws, export control laws, laws governing the content shared, and other applicable laws and regulatory requirements; Provide accurate contact and identity information to us and keep it updated; Use your real name on your profile; and Use the Services in a professional manner. 8.2. Don’ts You agree that you will not : Create a false identity on LinkedIn, misrepresent your identity, create a Member profile for anyone other than yourself (a real person), or use or attempt to use another’s account (such as sharing log-in credentials or copying cookies); Develop, support or use software, devices, scripts, robots or any other means or processes (such as crawlers, browser plugins and add-ons or any other technology) to scrape or copy the Services, including profiles and other data from the Services; Override any security feature or bypass or circumvent any access controls or use limits of the Services (such as search results, profiles, or videos); Copy, use, display or distribute any information (including content) obtained from the Services, whether directly or through third parties (such as search tools or data aggregators or brokers), without the consent of the content owner (such as LinkedIn for content it owns); Disclose information that you do not have the consent to disclose (such as confidential information of others (including your employer); Violate the intellectual property rights of others, including copyrights, patents, trademarks, trade secrets or other proprietary rights. For example, do not copy or distribute (except through the available sharing functionality) the posts or other content of others without their permission, which they may give by posting under a Creative Commons license; Violate the intellectual property or other rights of LinkedIn, including, without limitation, (i) copying or distributing our learning videos or other materials, (ii) copying or distributing our technology, unless it is released under open source licenses; or (iii) using the word “LinkedIn” or our logos in any business name, email, or URL except as provided in the Brand Guidelines ; Post (or otherwise share) anything that contains software viruses, worms, or any other harmful code; Reverse engineer, decompile, disassemble, decipher or otherwise attempt to derive the source code for the Services or any related technology that is not open source; Imply or state that you are affiliated with or endorsed by LinkedIn without our express consent (e.g., representing yourself as an accredited LinkedIn trainer); Rent, lease, loan, trade, sell/re-sell or otherwise monetize the Services or related data or access to the same, without LinkedIn’s consent; Deep-link to our Services for any purpose other than to promote your profile or a Group on our Services, without LinkedIn’s consent; Use bots or other unauthorized automated methods to access the Services, add or download contacts, send or redirect messages, create, comment on, like, share, or re-share posts, or otherwise drive inauthentic engagement; Engage in “framing”, “mirroring”, or otherwise simulating the appearance or function of the Services; Overlay or otherwise modify the Services or their appearance (such as by inserting elements into the Services or removing, covering, or obscuring an advertisement included on the Services); Interfere with the operation of, or place an unreasonable load on, the Services (e.g., spam, denial of service attack, viruses, manipulating algorithms); Violate the Professional Community Policies , certain third party terms where applicable, or any additional terms concerning a specific Service that are provided when you sign up for or start using such Service; Use our Services to do anything that is unlawful, misleading, discriminatory, fraudulent or deceitful (e.g. manipulated media that wrongfully depicts a person saying or doing something they did not say or do); and/or Misuse our reporting or appeals process, including by submitting duplicative, fraudulent or unfounded reports, complaints or appeals. 9. Complaints Regarding Content Contact information for complaints about content provided by our Members. We ask that you report content and other information that you believe violates your rights (including intellectual property rights), our Professional Community Policies or otherwise violates this Contract or the law. To the extent we can under law, we may remove or restrict access to content, features, services, or information, including if we believe that it’s reasonably necessary to avoid harm to LinkedIn or others, violates the law or is reasonably necessary to prevent misuse of our Services. We reserve the right to take action against serious violations of this Contract, including by implementing account restrictions for significant violations. We respect the intellectual property rights of others. We require that information shared by Members be accurate and not in violation of the intellectual property rights or other rights of third parties. We provide a policy and process for complaints concerning content shared, and/or trademarks used, by our Members. 10. How To Contact Us Our Contact information. Our Help Center also provides information about our Services. For general inquiries, you may contact us online . For legal notices or service of process, you may write us at these addresses . LinkedIn © 2026 About Accessibility User Agreement Privacy Policy Cookie Policy Copyright Policy Brand Policy Guest Controls Community Guidelines العربية (Arabic) বাংলা (Bangla) Čeština (Czech) Dansk (Danish) Deutsch (German) Ελληνικά (Greek) English (English) Español (Spanish) فارسی (Persian) Suomi (Finnish) Français (French) हिंदी (Hindi) Magyar (Hungarian) Bahasa Indonesia (Indonesian) Italiano (Italian) עברית (Hebrew) 日本語 (Japanese) 한국어 (Korean) मराठी (Marathi) Bahasa Malaysia (Malay) Nederlands (Dutch) Norsk (Norwegian) ਪੰਜਾਬੀ (Punjabi) Polski (Polish) Português (Portuguese) Română (Romanian) Русский (Russian) Svenska (Swedish) తెలుగు (Telugu) ภาษาไทย (Thai) Tagalog (Tagalog) Türkçe (Turkish) Українська (Ukrainian) Tiếng Việt (Vietnamese) 简体中文 (Chinese (Simplified)) 正體中文 (Chinese (Traditional)) Language | 2026-01-13T08:48:28 |
https://support.apple.com/hu-hu/105082 | A Safari-előzmények, a gyorsítótár és a sütik törlése az iPhone-on - Apple Támogatás (HU) Apple Áruház Mac iPad iPhone Watch AirPods TV és Otthon Szórakozás Kiegészítők Támogatás 0 + A Safari-előzmények, a gyorsítótár és a sütik törlése az iPhone-on Az iPhone beállításaiban törölheti a Safari-előzményeket, a sütiket, a gyorsítótárat vagy egy adott webhelyet az előzmények közül. Tartalomblokkolókat is bekapcsolhat. Az előzmények, a gyorsítótár és a cookie-k törlése A gyorsítótár és a cookie-k törlése, de az előzmények megőrzése Webhely törlése az előzmények közül Cookie-k blokkolása Tartalomblokkolók használata Az előzmények, a gyorsítótár és a sütik törlése Lépjen a Beállítások > Appok > Safari menüpontba. Görgessen le, majd koppintson az Előzmények és webhelyadatok törlése elemre. Erősítse meg a törölni kívánt adatok időkeretét, majd koppintson az Előzmények törlése elemre. Ez nem változtatja meg az automatikus kitöltési adatokat. Ha a gomb kiszürkítve jelenik meg, akkor vagy nincs törölhető adat, vagy előfordulhat, hogy ellenőriznie kell a webes tartalmakra vonatkozó korlátozásokat a Képernyőidőnél . A gyorsítótár és a cookie-k törlése, de az előzmények megőrzése Lépjen a Beállítások > Appok > Safari > Haladó > Webhelyadatok menüpontba. Koppintson az Összes webhelyadat eltávolítása elemre. Ha a gomb kiszürkítve jelenik meg, akkor vagy nincs törölhető adat, vagy előfordulhat, hogy ellenőriznie kell a webes tartalmakra vonatkozó korlátozásokat a Képernyőidőnél . Koppintson az Eltávolítás most elemre. Ez törli a nyomon követéshez és használt és az olyan adatokat, amelyek alapján a webhelyek elmentik a bejelentkezési információkat a gyorsabb böngészés érdekében. Webhely törlése az előzmények közül Nyissa meg a Safari appot, majd koppintson a Továbbiak gombra . Koppintson a Könyvjelzők elemre. Koppintson az Előzmények gombra , majd koppintson ismét a Továbbiak gombra . Koppintson a Webhelyek kiválasztása elemre, majd válasszon ki egy vagy több webhelyet, amelyet törölni szeretne az előzményekből. Koppintson a Kuka gombra . A sütik blokkolása Ha le szeretné tiltani a sütiket (olyan adatokat, amelyeket egy webhely helyez el a készülékén, hogy emlékezzen az Ön adataira), lépjen a Beállítások > Alkalmazások > Safari > Haladó menüpontba. Kapcsolja be az Összes süti blokkolása funkciót. Koppintson az Összes blokkolása elemre. Ez eltávolítja az összes meglévő sütit és webhelyadatot. A Safari becsukódik, és a rendszer újra betölti a lapokat. Ha blokkolja a sütiket, lehetséges, hogy egyes weboldalak nem fognak működni. Néhány példa: Előfordulhat, hogy még a megfelelő felhasználónévvel és jelszóval sem fog tudni bejelentkezni bizonyos webhelyekre. Megjelenhet egy üzenet arról, hogy sütikre van szükség, vagy hogy a böngészőjében le vannak tiltva a sütik. Előfordulhat, hogy egy adott webhely egyes funkciói nem működnek. Tartalomblokkolók használata Lépjen az App Store-ba, és töltsön le egy tartalomblokkoló alkalmazást (olyan külső alkalmazást vagy bővítményt, amely ehetővé teszi, hogy a Safari blokkolja a sütiket, képeket, erőforrásokat, felugró ablakokat és egyéb tartalmakat). Ezután koppintson a Beállítások > Appok > Safari > Bővítmények menüpontra. Koppintással megjelenítheti a tartalomblokkolók listáját. Több tartalomblokkolót is használhat. Ha segítségre van szüksége, forduljon az alkalmazás fejlesztőjéhez . A nem az Apple által gyártott termékekre, illetve az Apple ellenőrzésén kívül eső vagy általa nem tesztelt független webhelyekre vonatkozó információk nem tekinthetők javaslatoknak vagy ajánlásoknak. Az Apple nem vállal felelősséget a harmadik felek webhelyeinek és termékeinek kiválasztására, teljesítményére, illetve használatára vonatkozólag. Az Apple nem garantálja, hogy a harmadik felek webhelyei pontosak vagy megbízhatóak. Forduljon az adott félhez további információkért. Közzététel dátuma: 2025. szeptember 24. Hasznos? Igen Nem Karakterkorlát: 250 A maximális karakterkorlát 250. Kérjük, személyes információkat ne adjon meg a megjegyzésben. Küldés Köszönjük a visszajelzést! Kapcsolódó témakörök Apple Footer Apple Támogatás A Safari-előzmények, a gyorsítótár és a sütik törlése az iPhone-on Magyarország Copyright © 2025 Apple Inc. Minden jog fenntartva. Adatvédelmi szabályzat Használati feltételek Értékesítés és visszatérítés Webhelytérkép Sütihasználat | 2026-01-13T08:48:28 |
https://stackoverflow.blog/2026/01/01/documents-the-architect-s-programming-language/#comments | Documents: The architect’s programming language - Stack Overflow Blog Loading… Everything Productivity AI/ML Open Source Business Hub Company Releases Podcast Newsletter Stack Overflow Business Stack Internal : the knowledge intelligence layer that powers enterprise AI. Stack Data Licensing : decades of verified, technical knowledge to boost AI performance and trust. Stack Ads : engage developers where it matters — in their daily workflow. January 1, 2026 Documents: The architect’s programming language Senior developers know how to deploy code to systems made of code. Architects know how to deploy ideas to systems made of people. Credit: Alexandra Francis [Ed. note: While we take some time to rest up over the holidays and prepare for next year, we are re-publishing our top ten posts for the year. Please enjoy our favorite work this year and we’ll see you in 2026.] From junior developer to senior/principal, career paths are typically straightforward. The better you get at coding, and at the technical and non-technical skills that enable you to code more effectively, the faster you’ll advance. But once you hit senior, there’s a major fork in the road. Many developers take the management track. It’s a great way to expand your influence and move up the ladder. But one downside is you’ll inevitably spend less time programming—a lot of engineering managers don’t get time to code at all—and if you’re like me, that’s a deal breaker. The time you used to spend heads-down, translating tricky processes into beautiful abstractions, will instead be spent in meetings, removing roadblocks for your team, mediating disagreements, and checking boxes for HR. It’s challenging and important work, but it’s very different. The other common option is the architect track. This lets you stay knee-deep in code while increasing your impact and leveraging your tenure. At many companies, the architect track has similar compensation and job title advancement opportunities to the management track, and either one can lead to a C-suite role (like CTO). But the architect track may seem poorly-defined by comparison. When you move into people management, your day-to-day work changes completely. Your schedule changes, your team structure changes—your work output is measured in a totally different way. But being an architect looks a lot like being a senior developer: writing code in an IDE, reviewing pull requests, talking about things like deployment pipelines and data structures. So what makes an architect different? Or in other words, if you want to prove you’re ready for an architect role , how do you do it? What is an architect? It’s not just about being knowledgeable or smart. That’s how you got to where you are. And it’s not just about shipping resilient and well-designed systems, though that’s important too. In my opinion, the difference comes down to one main thing: Senior developers know how to deploy code to systems made of code. Architects know how to deploy ideas to systems made of people. This may sound like an empty metaphor. I promise it isn’t. To clarify: I don’t just mean that architects are good communicators or that they work well with others, though both things matter. Nor is this my flowery way of saying soft skills are important, though they are. I mean that an architect knows effective, repeatable processes for organizing and deploying ideas , above and beyond the processes that organize and deploy machines and applications. They know there are limits to what you can achieve with a code push; the most important issues require input, collaboration, and consensus from people with different perspectives and job titles. In other words, most engineers at most companies can’t kick off a multi-month project, rewrite a web service, or choose the programming language for a new product without buy-in from multiple other developers and leaders. The biggest bottlenecks in the software lifecycle have nothing to do with code. They’re people problems: communication, persuasion, decision-making. So in order to make an impact, architects have to consistently make those things happen, sprint after sprint, quarter after quarter. How do you reliably get the right people in the right place, at the right time, talking about the right things? Is there a transfer protocol or infrastructure-as-code tool that works on human beings? As it happens, yes. There are several tools, actually: Confluence, Google Docs, Notion, XWiki, BookStack…you get the idea. If you can write bullet points and link between documents, you can deploy ideas. The most effective way to get something done in most organizations is to write a document, share it with the people most likely to care, and listen to their feedback. A lot of programmers don’t feel confident in their writing skills, though. It’s hard to switch from something you’re experienced at, where quality speaks for itself (programming) to something you’re unfamiliar with, where quality depends on the reader’s judgment (writing). So what follows is a crash course: just enough information to help you confidently write good (even great) documents, no matter who you are. You don’t have to have an English degree, or know how to spell “idempotent,” or even write in your native language. You just have to learn a few techniques. Principles of good documents This is my manifesto on documentation. > As a documentation geek, I’ve come to value: > JOTTING THINGS DOWN over worrying about how to structure them > A CULTURE OF DOCUMENTATION over box-checking behavior > THINKING ABOUT WHAT’S RELEVANT over using a template > POINT-IN-TIME DOCUMENTATION over constant updates This is intentionally similar to the Agile manifesto. The items on the right have value, but the ones on the left are more important. I’ll go into greater detail on some of these points later on, including ideas about how to structure different types of documents, but keep in mind the first and third points: it’s better to write down what you know than to get stuck figuring out the right format. And the format doesn’t even need to be the same from one document to the next. Focus on what works for the information you’re presenting right now, not what’s worked before. How to write a document Even if you don’t have a lot of practice with technical writing, you can still write excellent documentation. There’s one simple yet ridiculously effective hack that will improve practically any document you write: bullet points . Bullet points are magical. They put you in a mindset of completeness and structure, rather than sentence flow and style. People reading a technical document are trying to find information quickly—in fact, one of the best metrics for documentation is how fast people stop reading it. If they find what they need in ten seconds and leave, that’s a win. And since bullet points tend to be information-dense and easy to skim, they’re the perfect tool for the job. Here are the last two paragraphs as bullet points: Bullet points are good for technical writing Help you focus on completeness and structure Don’t require as much writing skill Make documents easier to skim That’s almost 100% of the same information in 25% of the page space. It was easier to write, too. That’s why bullet points are an architect’s best friend. The second most valuable technique you can use is headers . Unless your information can be expressed in very few bullet points, it’s worth breaking it into sections with meaningful titles. For example, most of the documents I write start with a “Context” section. Its purpose is to provide information and links about the history, business domain, or predetermined constraints of a topic. You might know all that information offhand, since you’re actively working on it from day to day, but other readers will appreciate the memory jog. And in a year when you refer back to your own document, you’ll appreciate it too. Of course, people who already have a deep understanding of the topic at hand can skim or skip the Context section. That’s the great thing about headers: they make it even easier for someone to find whatever tidbit of information they’re looking for and ignore whatever they aren’t. (If you’ve got more than a handful of headers and want to optimize even further, a linked table of contents is a great addition.) If you don’t know what headers to use at first, just write bullet points in whatever order comes to mind. Then organize them into logical groups and label them. This isn’t so different from programming: you might write a 200-line method as a first draft, but once you’ve got it working, you usually refactor by breaking it into steps and extracting common patterns into functions. The main thing you want to avoid is a giant wall of text. Often the people whose attention your document needs most are the people with the most demands on their time. If you send them a four-page essay, there’s a good chance they’ll never have the time to get through it. A well-organized set of bullet points, on the other hand, makes it possible for them to scroll through, glean the information they need, and respond whenever they have a minute to spare. What to do with your document Once you’ve got all the necessary information written down, consider doing a sanity check. Send it to someone you work closely with and ask them to point out anything that seems wrong or doesn’t make sense. Then use their feedback to clarify, reorganize, or rephrase. Keep in mind that most documents are more like one-off Bash scripts than living SaaS applications. Once a document has done its job, you probably won’t ever update it again. As an architect, you can easily write a hundred documents a year; you definitely don’t have time to maintain them all. This has two implications. First, you should make sure each document is good enough to be useful later, even as it gradually goes obsolete. It’s worth putting in some extra effort now so you can forget about it until it comes up again. Second, you should make it easy to tell when the document was originally written, and conversely, easy to find documents that were written around the same time. Point-in-time documentation is a lot more useful when it’s obvious how out-of-date it is. My approach to this may seem counterintuitive. Most people start out organizing documents according to topic: one folder for this feature, another folder for that one. But this leads to having a bunch of apparently-equal folders that aren’t all equally valuable. Some of them are full of recent, highly-relevant documents; others don’t have any documentation from the last five years; still others have a mix of new and old documents, some of which directly contradict each other, and it’s not immediately clear what order they should be in. So instead, I organize nearly all documents chronologically: by year and then by sprint. This helps keep the timeline visible. For example, in Confluence, I create a “space” (which other tools may call a “workspace,” “wiki,” or “book”) for each team or product—some high-level logical separation is useful—but within each space, the folder structure looks something like this: 📄 Overview 📄 Architecture 📁 2025 📁 Jan 1 Sprint 📄 Proposal: SSO login 📄 APP-132 Research on user sessions 📁 Jan 15 Sprint 📄 APP-135 Allow SSO login for configured clients 📁 Feb 2 Sprint 📄 Problems with SSO login and user roles 📄 Dev forecast: escalating role-permission complexity Note that for a small number of high-level documents, continuous maintenance makes sense. If someone’s curious about the product in general, it’s good to have an up-to-date landing page and maybe an architecture diagram. But most documents have a shelf life: they’ll get less and less relevant as time goes on. You might ask, “Isn’t this the opposite of how people think? I’m usually looking for docs about a specific project or feature, not about what happened in March of 2020.” My answer is, “There’s a search box for that.” Organizing documents by topic is like categorizing jelly beans: no two people can agree on the right way to do it. That means every time you write a document you’ll waste time trying to figure out where it belongs, and every time you go looking for a document you’ll waste time browsing the wrong folder before you find the right one. It’s like organizing CSS properties logically instead of alphabetically: it might feel good to have `left` and `top` on adjacent lines, but it doesn’t actually accomplish anything. For CSS, alphabetical order is faster, simpler, and always good enough. For documents, chronological order wins for the same reasons. Besides, searching is usually the right move anyway. Browsing is good for discovering what documents exist, but if you’re looking for specific information it’s too easy to overlook documents that have info you need, but whose titles don’t immediately seem relevant. Searching, on the other hand, is fast and turns up everything that matches your search terms. A chronological approach to organization practically forces people to search, which is what they should do. And when they click a search result, they’ll get immediate context about when it was written and what other things were happening at the same time. Once you’ve got your document peer-reviewed and published, the last step is to grab the link and spread it around. If it overrides or extends another document, update that document with the link. If it’s attached to an issue-tracking ticket, add it there too. And finally, send it to the people whose feedback, approval, or consensus you need. Appendix: High-impact document types Following are a few of the most effective types of documents for engineering organizations. The architecture overview Purpose: To help others quickly get up to speed on the structure and design of a system. Audience: All stakeholders in a system: managers, developers, operations engineers, product owners, etc. When to write one: Before you build a new system or restructure an existing one. Also useful when any existing system proves difficult to understand. Content: Describes the major components of a system (databases, applications, cloud services, load balancers, etc.) and how they communicate with each other. May also describe internal components, like data models and classes, though you should avoid excessive detail. Structure: May be a diagram with symbols such as cylinders, boxes, and arrows, a multi-page document with sections and subsections, or just a list of nested bullet points. Common formats include arc42 and C4 . How it orchestrates ideas: An up-to-date architecture overview, or even a somewhat outdated one, can help contributors form a mental model of a system so they can build on, troubleshoot, and reason about it. It also helps leaders and ops engineers understand how to deliver it, what it costs, and how it interacts with existing systems, which is essential to getting it approved in the first place. Tips: Remember, jotting things down is more important than worrying about how to structure them. Don’t stress about following a strict format or using all the right symbols (unless you want to). An imperfect architecture document that exists is better than a perfect one that doesn’t. The dev design Purpose: To get feedback on code you intend to write; to help you surface unknowns and complications before you write a bunch of half-baked code that ends up getting thrown away. Audience: Other developers on your team; future developers who want to understand the evolution of a system. When to write one: Before you start working on any non-trivial coding task. Can also be written after you’ve started working on something that seemed trivial, but is turning out to be more complicated. Content: The level of detail is up to you. Don’t spell out anything obvious or mundane, but include enough information that other developers can call out incorrect assumptions and recommend existing logic/patterns that you might not have been aware of. Structure: A list of steps that will be followed. For example, class A will be modified by adding a method that does X, class B will be created to contain data about Y, a database migration will be created that does Z, and so on. You can also include an Open Questions section with anything that needs to be addressed before you can get started, or an Alternative Approaches section with different implementations you’d like your teammates to weigh in on. How it orchestrates ideas: Dev designs help developers share knowledge and preserve the core patterns and abstractions of a system. They also create a permanent record of how a system came to be the way it is. If your team doesn’t do pair/mob programming, dev designs can give you many of the same benefits while also helping future contributors learn the system. Tips: This sounds false, but it’s true: the more documentation you write, the less code you have to write. Documentation can help you avoid the types of misunderstandings, incorrect assumptions, and design mistakes that lead to PR back-and-forth and rewrites. It can also help you avoid sinking a lot of time into exploratory coding that won’t lead anywhere. The project proposal Purpose: To communicate the value and cost of a project so time and money can be allocated to it. Audience: Leaders and product owners. When to write one: When planning meetings are on the horizon, or whenever you see an opportunity to meaningfully improve or expand the company’s products and systems. Content: Summarizes everything a leader needs to know to evaluate one project’s priority versus another. Why is it important? Who will it affect? How long will it take? And so on. Structure: A few clearly-labeled sections like Context, Problem to be Solved, Proposed Solution, User Impact, and Estimated Engineering Effort. How it orchestrates ideas: Project proposals are how big, impactful, months-long undertakings are born. They set the roadmap for entire teams. Tips: Make your proposal easy to say “yes” to by making it understandable for both technical and non-technical stakeholders. Remember that other people aren’t thinking about what you’re doing all the time, so you need more context than you think. Consider doing some research beforehand, whether that’s data mining to determine how many users would be affected, asking around to find out how frustrating the problem really is, or reading up on how other teams and companies have approached similar projects. The developer forecast Purpose: To raise the possibility of worse-than-expected outcomes, especially ones that your experience makes you uniquely qualified to foresee, then suggest ways to respond to them. Audience: The stakeholders of a business decision. When to write one: When a decision is made that, for you as an engineer, feels risky or likely to disappoint. Content: Start by summarizing why the decision was made and what goals the decisionmakers hoped to achieve. Explain the factors leading you to believe negative outcomes are likely. Describe what those outcomes are. Then suggest ways to mitigate them, even if the decision ultimately doesn’t change. Structure: A well-organized document with sections like Decision, Motivations, Issues, Likely Outcomes, and Solutions. How it orchestrates ideas: A developer forecast helps you share your professional foresight and get people thinking about the pitfalls of a plan. It also prepares the organization to respond quickly and adeptly when something goes wrong, instead of repeatedly painting over the problem. When and if a plan starts to fail, your forecast can become a North Star of sorts, demonstrating the growing contrast between expectations and outcomes. Tips: Maintain a neutral tone so you don’t sound like a doom-and-gloomer. Consider multiple possibilities and don’t try to turn the whole ship around; just point at the iceberg and suggest ways to handle it. The technology menu Purpose: To reduce decision-making time when spinning up a new application. Audience: A development team or organization. When to write one: When you’re planning a project and there are differing opinions about what technologies to use. Content: For a given type of technology (programming languages, runtimes, frameworks, platforms, etc.), focus on the options you and your colleagues favor most. Compare the strengths of each: How familiar is your organization with it (not just building with it, but deploying and maintaining it)? Is it easy to hire developers that know and like it? Does it have a healthy open-source ecosystem and good documentation? How quickly can the average dev go from zero to a useful application with it? Does it encourage standards, structures, and patterns that are recognizable across codebases? Is it performant when it needs to be? Once you’ve got a well-rounded picture of the technical and non-technical pros and cons, make recommendations for when to use each. One might be your default for web services, another for serverless functions, yet another for prototypes and internal apps. Structure: A comparison chart followed by clear recommendations for a few different situations. How it orchestrates ideas: The technology menu helps create a consensus about how things are built, freeing developers to spin up useful tech without getting bogged down in this-versus-that debates. It can also challenge company defaults that have survived by virtue of tradition rather than suitability or popularity. Tips: Try to avoid championing your personal preferences. If you’re the one writing the menu, take it through a few rounds of feedback with developers who have worked with different technologies. Give their opinions as much weight as your own; it’s more important to get the team on the same page than to choose the absolute “best” technology. The problem statement Purpose: To quickly reach consensus about how to solve or work around a problem. Audience: Stakeholders in a project. When to write one: Whenever you encounter a problem with no obvious solution and you need the organization to make a clear decision about it. Content: Explain the nature of the problem in simple terms. If it has a clear business impact, describe (or estimate) the scope and severity. Most problems involve two or more constraints that can’t be satisfied at the same time; if that’s the case here, make it very clear what those constraints are and why they contradict. Then present a few possible ways to move forward, summarizing the pros and cons of each. Structure: Sections like Context, Problem, Impact, Constraints, and Possible Solutions. How it orchestrates ideas: A well-written problem statement makes it possible for anyone, regardless of role, to understand the nature of a problem and why it matters, then weigh in on their preferred solution. It also leaves a permanent record of the conversation so you can refer back to it—the bigger a problem is, the more likely it will reappear or be rehashed later. Tips: Don’t skip the last section, even if none of the solutions that come to mind seem particularly good. Any engineer can find problems, but an architect’s job is to find solutions. If nothing else, presenting a few bad ideas can pave the way for someone to suggest a good one. The postmortem Purpose: To keep catastrophic problems from recurring. Audience: Anyone with an interest in a recent outage, failure, or high-priority bug. When to write one: When a technological problem has had an abnormal impact. Most bugs don’t need a postmortem, but if there’s a major disruption to the flow of business—like an on-call developer getting paged or customers calling in to complain—it’s probably time to take things a step further. Content: Describe, in a blameless way, the apparent problem and how it came to your attention. Include links to any related conversations, pull requests, and issue-tracking tickets. Add details about who was affected, how long the problem took to resolve, and what was done to try to mitigate it in the meantime. Conclude by explaining the root causes of the problem, then recommending ways to prevent it from happening again. Structure: Sections like Context, Problem, Impact, Timeline, Root Causes, and Recommended Process Changes. How it orchestrates ideas: Postmortems help organizations move from the fear and anxiety of “this can never happen again” to the confidence and security of “we’ll make sure of it.” When used correctly, they also help shift culture away from individual blame, toward organizational competence and automatic safeguards. Tips: Postmortems are opportunities to take accountability for your mistakes, but they’re not exercises in self-flagellation. Everyone has bad days and makes mistakes. The purpose of an organization is to create resilience above and beyond what any one person can offer. Acknowledge the role you played, but keep your focus on what the organization as a whole can do better. Author s Isaac Lyman architecture documentation Recent articles January 12, 2026 Now everyone can chat on Stack Overflow January 5, 2026 What’s new at Stack Overflow: January 2026 January 2, 2026 A new worst coder has entered the chat: vibe coding without code knowledge December 31, 2025 A look under the hood: How (and why) we built Question Assistant Latest Podcast January 13, 2026 Vibe code anything in a Hanselminute Add to the discussion Login with your stackoverflow.com account to take part in the discussion. Our Stack Stack Internal Features Customers Security Pricing Stack Data Licensing Stack Ads Partnerships Services Stack Overflow Company Leadership Press Careers Social Impact Support Contact Stack Overflow help Stack Internal help Terms Privacy policy Cookie policy Your Privacy Choices Elsewhere Blog Dev Newsletter Podcast Releases Dev Survey Site design / logo © 2026 Stack Exchange Inc. Light Dark Auto | 2026-01-13T08:48:28 |
https://developer.x.com/docs/x-for-websites/cards/overview/abouts-cards#SVGID_1_ | About Twitter Cards | Docs | X Developer Platform <g> <g> <defs> <rect id="SVGID_1_" x="-468" y="-1360" width="1440" height="3027" /> </defs> <clippath id="SVGID_2_"> <use xlink:href="#SVGID_1_" style="overflow:visible;" /> </clippath> </g> </g> <rect x="-468" y="-1360" class="st0" width="1440" height="3027" style="fill:rgb(0,0,0,0);stroke-width:3;stroke:rgb(0,0,0)" /> <path d="M13.4,12l5.8-5.8c0.4-0.4,0.4-1,0-1.4c-0.4-0.4-1-0.4-1.4,0L12,10.6L6.2,4.8c-0.4-0.4-1-0.4-1.4,0c-0.4,0.4-0.4,1,0,1.4 l5.8,5.8l-5.8,5.8c-0.4,0.4-0.4,1,0,1.4c0.2,0.2,0.4,0.3,0.7,0.3s0.5-0.1,0.7-0.3l5.8-5.8l5.8,5.8c0.2,0.2,0.5,0.3,0.7,0.3 s0.5-0.1,0.7-0.3c0.4-0.4,0.4-1,0-1.4L13.4,12z" /> </svg>" data-icon-chevron-right="<svg xmlns="http://www.w3.org/2000/svg" width="24" height="24" viewbox="0 0 24 24" aria-hidden="true" focusable="false" role="none" class="twtr-icon"> <path opacity="0" d="M0 0h24v24H0z" /> <path d="M17.207 11.293l-7.5-7.5c-.39-.39-1.023-.39-1.414 0s-.39 1.023 0 1.414L15.086 12l-6.793 6.793c-.39.39-.39 1.023 0 1.414.195.195.45.293.707.293s.512-.098.707-.293l7.5-7.5c.39-.39.39-1.023 0-1.414z" /> </svg>" data-icon-chevron-down="<svg xmlns="http://www.w3.org/2000/svg" width="24" height="24" viewbox="0 0 24 24" aria-hidden="true" focusable="false" role="none" class="twtr-icon"> <path opacity="0" d="M0 0h24v24H0z" /> <path d="M20.207 7.043c-.39-.39-1.023-.39-1.414 0L12 13.836 5.207 7.043c-.39-.39-1.023-.39-1.414 0s-.39 1.023 0 1.414l7.5 7.5c.195.195.45.293.707.293s.512-.098.707-.293l7.5-7.5c.39-.39.39-1.023 0-1.414z" /> </svg>" data-icon-arrow-left="<svg width="28px" height="28px" viewbox="0 0 28 28" version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" aria-hidden="true" focusable="false" role="none" class="twtr-icon u01-meganav__icon-arrow-left"> <g stroke="none" stroke-width="1" fill="none" fill-rule="evenodd" stroke-linecap="round"> <g transform="translate(-1216.000000, -298.000000)" stroke-width="2.25"> <g transform="translate(1200.000000, 282.000000)"> <g transform="translate(17.000000, 17.000000)"> <path d="M0.756410256,12.8589744 L25.7179487,12.8589744"></path> <path d="M13.2371795,25.3397436 L25.7179487,12.8589744"></path> <path d="M13.2371795,12.4807692 L25.3397436,0.378205128" transform="translate(19.288462, 6.429487) rotate(-90.000000) translate(-19.288462, -6.429487) "></path> </g> </g> </g> </g> </svg>" data-left-nav-items="[{"isActive":false,"hasActiveChild":false,"children":[{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"X API","linkDisabled":false,"title":"X API","path":"https://developer.x.com/en/products/twitter-api"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"X Ads API","linkDisabled":false,"title":"X Ads API","path":"https://developer.x.com/en/products/x-ads-api"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"X for websites","linkDisabled":false,"title":"X for websites","path":"https://developer.x.com/en/products/x-for-websites"}],"overviewTitle":"Products","linkDisabled":true,"title":"Products","path":"https://developer.x.com/en/products"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Docs","linkDisabled":false,"title":"Docs","path":"https://docs.x.com/"},{"isActive":false,"hasActiveChild":false,"children":[{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Build for business","linkDisabled":false,"title":"Build for business","path":"https://developer.x.com/en/use-cases/build-for-businesses"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Build for the public","linkDisabled":false,"title":"Build for the public","path":"https://developer.x.com/en/use-cases/build-for-consumers"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Do research","linkDisabled":false,"title":"Do research","path":"https://developer.x.com/en/use-cases/do-research"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Teach \u0026 learn","linkDisabled":false,"title":"Teach \u0026 learn","path":"https://developer.x.com/en/use-cases/teach-and-learn"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Build for good","linkDisabled":false,"title":"Build for good","path":"https://developer.x.com/en/use-cases/build-for-good"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Build for fun","linkDisabled":false,"title":"Build for fun","path":"https://developer.x.com/en/use-cases/build-for-fun"}],"overviewTitle":"Use Cases","linkDisabled":true,"title":"Use Cases","path":"https://developer.x.com/en/navigation/left-nav-items/use-cases"},{"isActive":false,"hasActiveChild":false,"children":[{"isActive":false,"hasActiveChild":false,"children":[{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Changelog","linkDisabled":false,"title":"Changelog","path":"https://docs.x.com/updates/changelog"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Blog","linkDisabled":false,"title":"Blog","path":"https://developer.x.com/en/blog"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Newsletter","linkDisabled":false,"title":"Newsletter","path":"https://developer.x.com/en/updates/stay-informed"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"YouTube","linkDisabled":false,"title":"YouTube","path":"https://www.youtube.com/c/twitterdev"}],"linkDisabled":true,"title":"Stay informed","path":"https://developer.x.com/"},{"isActive":false,"hasActiveChild":false,"children":[{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Forums","linkDisabled":false,"title":"Forums","path":"https://twittercommunity.com/"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Events","linkDisabled":false,"title":"Events","path":"https://twitterdev.bevylabs.com/"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Insiders","linkDisabled":false,"title":"Insiders","path":"https://developer.twitter.com/en/community/insiders"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Community leaders","linkDisabled":false,"title":"Community leaders","path":"https://developer.x.com/en/community/leaders"}],"linkDisabled":true,"title":"Connect","path":"https://developer.x.com/"}],"overviewTitle":"Community","linkDisabled":false,"menuType":"multiCategory","title":"Community","path":"https://developer.x.com/en/community"}]" data-right-nav-items="[{"isActive":false,"hasActiveChild":false,"children":[{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Policies","linkDisabled":false,"title":"Policies","path":"https://developer.x.com/en/developer-terms"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Developer agreement","linkDisabled":false,"title":"Developer agreement","path":"https://developer.x.com/en/developer-terms/agreement-and-policy/source"}],"overviewTitle":"Support","linkDisabled":false,"title":"Support","path":"https://developer.x.com/en/support"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Developer Portal","linkDisabled":false,"title":"Developer Portal","path":"https://developer.twitter.com/en/portal/petition/essential/basic-info"}]" data-cta-enabled="true" data-profile-enabled="true" data-cta-link-new-tab="false" data-root-page-title="Developer Platform"> About Twitter Cards About X Cards With X Cards, you can attach rich photos, videos and media experiences to Tweets, helping to drive traffic to your website. Simply add a few lines of markup to your webpage, and users who Tweet links to your content will have a “Card” added to the Tweet that’s visible to their followers. The Tweet embedded below shows a Player Card along with the text of the Tweet: The dusk and dawn light in @DeathValleyNPS is amazing. I visit almost every year for #photography . https://t.co/Lcm76CSQrY — Jonathan Cipriano (@joncipriano) February 22, 2016 Drive engagement from your Tweets The different Card types each have a beautiful consumption experience built for X’s web and mobile clients: Summary Card : Title, description, and thumbnail. Summary Card with Large Image : Similar to the Summary Card, but with a prominently-featured image. App Card : A Card with a direct download to a mobile app. Player Card : A Card that can display video/audio/media. To learn more about how the Card meta tags and web crawler work, check out the Getting Started Guide . Drive app downloads from your Tweets In addition to displaying content in a more engaging way, Cards can also drive downloads of mobile apps, and even link directly into installed applications. For more information, see Cards for Mobile Developers . Get started in 4 simple steps Ready to get started with Cards? In most cases, it takes less than 15 minutes to implement. Choose a card type to implement. Add the correct meta tags to the page. Run the URL through the validator tool to test. After testing in the validator or approval of your Player Card, Tweet the URL and see the Card appear below your Tweet in the details view. We hope you enjoy using X Cards, and if you have any questions, drop us a line on the X Cards Forum . Thanks, and happy coding! <path opacity="0" d="M0 0h24v24H0z" /> <path d="M20.207 7.043c-.39-.39-1.023-.39-1.414 0L12 13.836 5.207 7.043c-.39-.39-1.023-.39-1.414 0s-.39 1.023 0 1.414l7.5 7.5c.195.195.45.293.707.293s.512-.098.707-.293l7.5-7.5c.39-.39.39-1.023 0-1.414z" /> </svg>"> Developer policy and terms Follow @XDevelopers Subscribe to developer news X platform X.com Status Accessibility Embed a post Privacy Center Transparency Center Download the X app Try Grok.com X Corp. About the company Company news Brand toolkit Jobs and internships Investors Help Help Center Using X X for creators Ads Help Center Managing your account Email Preference Center Rules and policies Contact us Developer resources Developer home Documentation Forums Communities Developer blog Engineering blog Developer terms Business resources Advertise X for business Resources and guides X for marketers Marketing insights Brand inspiration X Ads Academy © 2026 X Corp. Cookies Privacy Terms and conditions Did someone say … cookies? X and its partners use cookies to provide you with a better, safer and faster service and to support our business. Some cookies are necessary to use our services, improve our services, and make sure they work properly. Show more about your choices . Accept all cookies Refuse non-essential cookies | 2026-01-13T08:48:28 |
https://developer.x.com/twitterdev-news-subscription | XDev newsletter subscription – X Developers | X Developer Platform <g> <g> <defs> <rect id="SVGID_1_" x="-468" y="-1360" width="1440" height="3027" /> </defs> <clippath id="SVGID_2_"> <use xlink:href="#SVGID_1_" style="overflow:visible;" /> </clippath> </g> </g> <rect x="-468" y="-1360" class="st0" width="1440" height="3027" style="fill:rgb(0,0,0,0);stroke-width:3;stroke:rgb(0,0,0)" /> <path d="M13.4,12l5.8-5.8c0.4-0.4,0.4-1,0-1.4c-0.4-0.4-1-0.4-1.4,0L12,10.6L6.2,4.8c-0.4-0.4-1-0.4-1.4,0c-0.4,0.4-0.4,1,0,1.4 l5.8,5.8l-5.8,5.8c-0.4,0.4-0.4,1,0,1.4c0.2,0.2,0.4,0.3,0.7,0.3s0.5-0.1,0.7-0.3l5.8-5.8l5.8,5.8c0.2,0.2,0.5,0.3,0.7,0.3 s0.5-0.1,0.7-0.3c0.4-0.4,0.4-1,0-1.4L13.4,12z" /> </svg>" data-icon-chevron-right="<svg xmlns="http://www.w3.org/2000/svg" width="24" height="24" viewbox="0 0 24 24" aria-hidden="true" focusable="false" role="none" class="twtr-icon"> <path opacity="0" d="M0 0h24v24H0z" /> <path d="M17.207 11.293l-7.5-7.5c-.39-.39-1.023-.39-1.414 0s-.39 1.023 0 1.414L15.086 12l-6.793 6.793c-.39.39-.39 1.023 0 1.414.195.195.45.293.707.293s.512-.098.707-.293l7.5-7.5c.39-.39.39-1.023 0-1.414z" /> </svg>" data-icon-chevron-down="<svg xmlns="http://www.w3.org/2000/svg" width="24" height="24" viewbox="0 0 24 24" aria-hidden="true" focusable="false" role="none" class="twtr-icon"> <path opacity="0" d="M0 0h24v24H0z" /> <path d="M20.207 7.043c-.39-.39-1.023-.39-1.414 0L12 13.836 5.207 7.043c-.39-.39-1.023-.39-1.414 0s-.39 1.023 0 1.414l7.5 7.5c.195.195.45.293.707.293s.512-.098.707-.293l7.5-7.5c.39-.39.39-1.023 0-1.414z" /> </svg>" data-icon-arrow-left="<svg width="28px" height="28px" viewbox="0 0 28 28" version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" aria-hidden="true" focusable="false" role="none" class="twtr-icon u01-meganav__icon-arrow-left"> <g stroke="none" stroke-width="1" fill="none" fill-rule="evenodd" stroke-linecap="round"> <g transform="translate(-1216.000000, -298.000000)" stroke-width="2.25"> <g transform="translate(1200.000000, 282.000000)"> <g transform="translate(17.000000, 17.000000)"> <path d="M0.756410256,12.8589744 L25.7179487,12.8589744"></path> <path d="M13.2371795,25.3397436 L25.7179487,12.8589744"></path> <path d="M13.2371795,12.4807692 L25.3397436,0.378205128" transform="translate(19.288462, 6.429487) rotate(-90.000000) translate(-19.288462, -6.429487) "></path> </g> </g> </g> </g> </svg>" data-left-nav-items="[{"isActive":false,"hasActiveChild":false,"children":[{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"X API","linkDisabled":false,"title":"X API","path":"https://developer.x.com/en/products/twitter-api"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"X Ads API","linkDisabled":false,"title":"X Ads API","path":"https://developer.x.com/en/products/x-ads-api"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"X for websites","linkDisabled":false,"title":"X for websites","path":"https://developer.x.com/en/products/x-for-websites"}],"overviewTitle":"Products","linkDisabled":true,"title":"Products","path":"https://developer.x.com/en/products"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Docs","linkDisabled":false,"title":"Docs","path":"https://docs.x.com/"},{"isActive":false,"hasActiveChild":false,"children":[{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Build for business","linkDisabled":false,"title":"Build for business","path":"https://developer.x.com/en/use-cases/build-for-businesses"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Build for the public","linkDisabled":false,"title":"Build for the public","path":"https://developer.x.com/en/use-cases/build-for-consumers"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Do research","linkDisabled":false,"title":"Do research","path":"https://developer.x.com/en/use-cases/do-research"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Teach \u0026 learn","linkDisabled":false,"title":"Teach \u0026 learn","path":"https://developer.x.com/en/use-cases/teach-and-learn"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Build for good","linkDisabled":false,"title":"Build for good","path":"https://developer.x.com/en/use-cases/build-for-good"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Build for fun","linkDisabled":false,"title":"Build for fun","path":"https://developer.x.com/en/use-cases/build-for-fun"}],"overviewTitle":"Use Cases","linkDisabled":true,"title":"Use Cases","path":"https://developer.x.com/en/navigation/left-nav-items/use-cases"},{"isActive":false,"hasActiveChild":false,"children":[{"isActive":false,"hasActiveChild":false,"children":[{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Changelog","linkDisabled":false,"title":"Changelog","path":"https://docs.x.com/updates/changelog"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Blog","linkDisabled":false,"title":"Blog","path":"https://developer.x.com/en/blog"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Newsletter","linkDisabled":false,"title":"Newsletter","path":"https://developer.x.com/en/updates/stay-informed"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"YouTube","linkDisabled":false,"title":"YouTube","path":"https://www.youtube.com/c/twitterdev"}],"linkDisabled":true,"title":"Stay informed","path":"https://developer.x.com/"},{"isActive":false,"hasActiveChild":false,"children":[{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Forums","linkDisabled":false,"title":"Forums","path":"https://twittercommunity.com/"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Events","linkDisabled":false,"title":"Events","path":"https://twitterdev.bevylabs.com/"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Insiders","linkDisabled":false,"title":"Insiders","path":"https://developer.twitter.com/en/community/insiders"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Community leaders","linkDisabled":false,"title":"Community leaders","path":"https://developer.x.com/en/community/leaders"}],"linkDisabled":true,"title":"Connect","path":"https://developer.x.com/"}],"overviewTitle":"Community","linkDisabled":false,"menuType":"multiCategory","title":"Community","path":"https://developer.x.com/en/community"}]" data-right-nav-items="[{"isActive":false,"hasActiveChild":false,"children":[{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Policies","linkDisabled":false,"title":"Policies","path":"https://developer.x.com/en/developer-terms"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Developer agreement","linkDisabled":false,"title":"Developer agreement","path":"https://developer.x.com/en/developer-terms/agreement-and-policy/source"}],"overviewTitle":"Support","linkDisabled":false,"title":"Support","path":"https://developer.x.com/en/support"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Developer Portal","linkDisabled":false,"title":"Developer Portal","path":"https://developer.twitter.com/en/portal/petition/essential/basic-info"}]" data-cta-enabled="true" data-profile-enabled="true" data-cta-link-new-tab="false" data-root-page-title="Developer Platform"> Subscribe to developer news Sign up for emails about the latest news, product updates, and events from the X Developer team. Also, check out other options to Stay Informed . First name * First name is required Last name * Last name is required Email address * Email address is required X username (@handle) Twitter username is required -- please include the "@" symbol Country * Please select one United States Afghanistan Aland Islands Albania Algeria American Samoa Andorra Angola Anguilla Antarctica Antigua And Barbuda Argentina Armenia Aruba Australia Austria Azerbaijan Bahamas Bahrain Bangladesh Barbados Belarus Belgium Belize Benin Bermuda Bhutan Bolivia Bosnia And Herzegovina Botswana Bouvet Island Brazil British Indian Ocean Territory Brunei Darussalam Bulgaria Burkina Faso Burundi Cambodia Cameroon Canada Cape Verde Cayman Islands Central African Republic Chad Chile China Christmas Island Cocos (Keeling) Islands Colombia Comoros Congo Cook Islands Costa Rica Cote D'Ivoire Croatia Cuba Cyprus Czech Republic Denmark Djibouti Dominica Dominican Republic Ecuador Egypt El Salvador Equatorial Guinea Eritrea Estonia Ethiopia Falkland Islands (Malvinas) Faroe Islands Fiji Finland France French Guiana French Polynesia French Southern Territories Gabon Gambia Georgia Germany Ghana Gibraltar Greece Greenland Grenada Guadeloupe Guam Guatemala Guernsey Guinea Guinea-Bissau Guyana Haiti Heard Island And Mcdonald Islands Holy See (Vatican City State) Honduras Hong Kong Hungary Iceland India Indonesia Iran, Islamic Republic Of Iraq Ireland Isle Of Man Israel Italy Jamaica Japan Jersey Jordan Kazakhstan Kenya Kiribati Korea, Democratic People'S Republic Of Korea, Republic Of Kuwait Kyrgyzstan Lao People'S Democratic Republic Latvia Lebanon Lesotho Liberia Libyan Arab Jamahiriya Liechtenstein Lithuania Luxembourg Macao Macedonia, The Former Yugoslav Republic Of Madagascar Malawi Malaysia Maldives Mali Malta Marshall Islands Martinique Mauritania Mauritius Mayotte Mexico Micronesia, Federated States Of Moldova, Republic Of Monaco Mongolia Montserrat Morocco Mozambique Myanmar Namibia Nauru Nepal Netherlands Netherlands Antilles New Caledonia New Zealand Nicaragua Niger Nigeria Niue Norfolk Island Northern Mariana Islands Norway Oman Pakistan Palau Palestinian Territory, Occupied Panama Papua New Guinea Paraguay Peru Philippines Pitcairn Poland Portugal Puerto Rico Qatar Reunion Romania Russian Federation Rwanda Saint Helena Saint Kitts And Nevis Saint Lucia Saint Pierre And Miquelon Saint Vincent And The Grenadines Samoa San Marino Sao Tome And Principe Saudi Arabia Senegal Serbia And Montenegro Seychelles Sierra Leone Singapore Slovakia Slovenia Solomon Islands Somalia South Africa South Georgia And The South Sandwich Islands South Korea Spain Sri Lanka Sudan Suriname Svalbard And Jan Mayen Swaziland Sweden Switzerland Syrian Arab Republic Taiwan, Province Of China Tajikistan Tanzania, United Republic Of Thailand Timor-Leste Togo Tokelau Tonga Trinidad And Tobago Tunisia Turkey Turkmenistan Turks And Caicos Islands Tuvalu Uganda Ukraine United Arab Emirates United Kingdom United States Minor Outlying Islands Uruguay Uzbekistan Vanuatu Venezuela Viet Nam Virgin Islands, British Virgin Islands, U.S. Wallis And Futuna Western Sahara Yemen Zambia Zimbabwe Country is required Would you like to get news, announcements and other marketing communications about other X services? You can unsubscribe anytime. Newsletter subscription Yes No Please make a selection from the checkbox group. Submit A field is missing You're subscribed! Developer policy and terms Follow @XDevelopers Subscribe to developer news X platform X.com Status Accessibility Embed a post Privacy Center Transparency Center Download the X app Try Grok.com X Corp. About the company Company news Brand toolkit Jobs and internships Investors Help Help Center Using X X for creators Ads Help Center Managing your account Email Preference Center Rules and policies Contact us Developer resources Developer home Documentation Forums Communities Developer blog Engineering blog Developer terms Business resources Advertise X for business Resources and guides X for marketers Marketing insights Brand inspiration X Ads Academy © 2026 X Corp. Cookies Privacy Terms and conditions Did someone say … cookies? X and its partners use cookies to provide you with a better, safer and faster service and to support our business. Some cookies are necessary to use our services, improve our services, and make sure they work properly. Show more about your choices . Accept all cookies Refuse non-essential cookies | 2026-01-13T08:48:28 |
https://dev.to/hoangleitvn/the-builds-that-last-manifesto-218c#the-gap-between-posts-and-reality | The Builds That Last Manifesto - DEV Community Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account DEV Community Close Add reaction Like Unicorn Exploding Head Raised Hands Fire Jump to Comments Save Boost More... Copy link Copy link Copied to Clipboard Share to X Share to LinkedIn Share to Facebook Share to Mastodon Share Post via... Report Abuse Hoang Le Posted on Jan 11 The Builds That Last Manifesto # productivity # programming # architecture # career Originally published on Builds That Last . I've been building and leading engineering teams for 15 years. Over 50 projects. Startups, enterprises, legacy systems, greenfield builds. Same pattern every time. Teams ship fast. Then they slow down. Not because engineers got lazy. Because the foundation was never there. At my company, we maintain systems 20+ years old. No documentation. No standards. When we ask stakeholders about business logic, they say "read the code". My teams sometimes decompile binary files just to understand what's inside. Debug at runtime because that's the only way to see how things work. Previous teams deployed code to AWS without committing to source control. Gone. This is what engineering looks like for most of us. Not the AI demos. Not the apps shipped in a weekend. The gap between posts and reality You'll see posts about vibe coding, AI-augmented development, shipping apps in hours. I'm not saying AI isn't real. I use these tools every day. The productivity gains are real. But there's a gap between what people post and what I see in actual projects. The posts show demos that work. Reality is production systems that break. The posts celebrate shipping fast. Reality is teams spending months paying back technical debt. The demo works. The demo always works. It's what comes after that separates software that lasts from software that collapses. The iceberg problem What you see is 20% above water. The shiny demos. The fast shipping. Vibe coding, agentic AI, apps built in hours. What you don't see is the 80% below: → Maintenance → Technical debt → Engineers connecting systems never meant to work together → Data inconsistencies accumulated over years → Teams spending days understanding what the previous developer was thinking That 80% is where my teams spend most of our time. And it's where the real lessons are. The speed trap I see this pattern repeat. A team starts fast. AI tools, modern stack, motivated engineers. First version ships in weeks. Everyone celebrates. Then users show up. Edge cases appear. The payment flow breaks. Data sync fails silently. Features that worked in demo crash under real load. Suddenly the team that was "moving fast" spends months fixing things. Not building new features. Just paying back debt from shipping without foundation. Leadership gets frustrated. "Why is the team slow now?" The team isn't slow. They're doing work that should have been done upfront. Speed without foundation creates the illusion of progress. Then reality catches up. Maintenance costs more than building Here's something most people don't think about until it's too late. Maintaining software costs more than building it from scratch. Think about repairing a house. You don't just fix the broken part. You investigate the structure. Remove old materials. Work around things that can't be changed. Then build the new thing. Software is the same. When you inherit a system without documentation, without standards, every change becomes an archaeology project. You spend more time understanding than building. The time you "save" by skipping foundation gets paid back with interest during maintenance. The AI paradox AI makes code generation 10x faster. That's real. AI also increases cognitive load by 30-40%. When AI generates code, someone still needs to verify it's secure. Check for edge cases. Understand the logic before shipping. Maintain it when something breaks. AI doesn't eliminate this work. It changes who's responsible for catching problems. Anthropic's CEO said 90% of their internal code is now AI-generated. The follow-up: "We're not replacing engineers". The 10% humans handle? That's the leverage zone. Architecture decisions. Debugging complex problems. Understanding why something should work, not just what it should do. AI is a turbo, not a robot. Good foundation? AI makes you faster at building good software. Bad foundation? AI makes you faster at building bad software. What this means for engineers The fundamentals matter more than ever. Everyone has access to AI now. The differentiator isn't who prompts better. It's who understands what they're building deeply enough to know when AI helps and when it hurts. Own your code. "The AI wrote it" isn't an excuse when something breaks at 2am. You shipped it. You're responsible. Read the code. Understand the logic. Ship with confidence. The 80% below water is where you build real skills. Legacy systems, maintenance, debugging. Not glamorous. But it's where you learn how software actually behaves. Don't avoid it. Embrace it. What this means for leaders You're only seeing 20% of what your team deals with. The demos work. Sprint reports look fine. But your team might be drowning in the 80% you don't see. The legacy code. Missing documentation. Tribal knowledge that walks out when someone leaves. Buying tools is easy. Training is hard. Teams that succeed with AI invested in foundation first. Standards, process, documentation. Then added AI. Teams that struggle added tools to existing chaos. Now they have faster chaos. Remove friction before adding speed. When you want to go faster, the instinct is to add more. More tools, more people, more pressure. Usually, the answer is to remove things. Remove blockers. Remove unnecessary process. Remove friction slowing your team down. The bottom line Real speed comes from clarity, not from typing faster. In the AI era, shipping is easy. Building to last is what matters. Those legacy systems with no documentation? They taught me more than any greenfield project. Not because they were well-built. Because they showed what happens when foundation is missing. Every time I build something new, I think about the engineer maintaining it in 10 years. Will they understand our decisions? Can they change things confidently? Or will they be stuck doing archaeology? That's what foundation means. Building for the people who come after. What's your experience with the 80% below water? I write about foundation-first engineering at Builds That Last . Top comments (0) Subscribe Personal Trusted User Create template Templates let you quickly answer FAQs or store snippets for re-use. Submit Preview Dismiss Code of Conduct • Report abuse Are you sure you want to hide this comment? It will become hidden in your post, but will still be visible via the comment's permalink . Hide child comments as well Confirm For further actions, you may consider blocking this person and/or reporting abuse Hoang Le Follow Engineering leader. Founder @ INNOMIZE. Building cloud-native systems for startups. Writing about platform engineering and technical leadership at Builds that Last. Location Vietnam Education The Degree of Engineer Information Technology Work Co-Founder, CEO, CTO at INNOMIZE Joined Oct 26, 2019 Trending on DEV Community Hot If a problem can be solved without AI, does AI actually make it better? # ai # architecture # discuss Prompt Engineering Won’t Fix Your Architecture # discuss # career # ai # programming MAWA - El lenguaje simple en sintaxis como Python de bajo nivel. Parte 3, Condicionales. # programming # beginners # showdev # codenewbie 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV DEV Community — A space to discuss and keep up software development and manage your software career Home DEV++ Podcasts Videos DEV Education Tracks DEV Challenges DEV Help Advertise on DEV DEV Showcase About Contact Free Postgres Database Software comparisons Forem Shop Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . DEV Community © 2016 - 2026. We're a place where coders share, stay up-to-date and grow their careers. Log in Create account | 2026-01-13T08:48:28 |
https://www.linkedin.com/legal/cookie-policy?trk=content_footer-cookie-policy | Cookie Policy | LinkedIn Skip to main content User Agreement Summary of User Agreement Privacy Policy Professional Community Policies Cookie Policy Copyright Policy Regional Info EU Notice California Privacy Disclosure U.S. State Privacy Laws User Agreement Summary of User Agreement Privacy Policy Professional Community Policies Cookie Policy Copyright Policy Regional Info EU Notice California Privacy Disclosure U.S. State Privacy Laws Cookie Policy Effective on June 3, 2022 At LinkedIn, we believe in being clear and open about how we collect and use data related to you. This Cookie Policy applies to any LinkedIn product or service that links to this policy or incorporates it by reference. We use cookies and similar technologies such as pixels, local storage and mobile ad IDs (collectively referred to in this policy as “cookies”) to collect and use data as part of our Services, as defined in our Privacy Policy (“Services”) and which includes our sites, communications, mobile applications and off-site Services, such as our ad services and the “Apply with LinkedIn” and “Share with LinkedIn” plugins or tags. In the spirit of transparency, this policy provides detailed information about how and when we use these technologies. By continuing to visit or use our Services, you are agreeing to the use of cookies and similar technologies for the purposes described in this policy. What technologies are used? ENTER A SUMMARY Type of technology Description Cookies A cookie is a small file placed onto your device that enables LinkedIn features and functionality. Any browser visiting our sites may receive cookies from us or cookies from third parties such as our customers, partners or service providers. We or third parties may also place cookies in your browser when you visit non-LinkedIn sites that display ads or that host our plugins or tags . We use two types of cookies: persistent cookies and session cookies. A persistent cookie lasts beyond the current session and is used for many purposes, such as recognizing you as an existing user, so it’s easier to return to LinkedIn and interact with our Services without signing in again. Since a persistent cookie stays in your browser, it will be read by LinkedIn when you return to one of our sites or visit a third party site that uses our Services. Session cookies last only as long as the session (usually the current visit to a website or a browser session). Pixels A pixel is a tiny image that may be embedded within web pages and emails, requiring a call (which provides device and visit information) to our servers in order for the pixel to be rendered in those web pages and emails. We use pixels to learn more about your interactions with email content or web content, such as whether you interacted with ads or posts. Pixels can also enable us and third parties to place cookies on your browser. Local storage Local storage enables a website or application to store information locally on your device(s). Local storage may be used to improve the LinkedIn experience, for example, by enabling features, remembering your preferences and speeding up site functionality. Other similar technologies We also use other tracking technologies, such as mobile advertising IDs and tags for similar purposes as described in this Cookie Policy. References to similar technologies in this policy includes pixels, local storage, and other tracking technologies. Our cookie tables lists cookies and similar technologies that are used as part of our Services. Please note that the names of cookies and similar technologies may change over time. What are these technologies used for? Below we describe the purposes for which we use these technologies. ENTER SUMMARY Purpose Description Authentication We use cookies and similar technologies to recognize you when you visit our Services. If you’re signed into LinkedIn, these technologies help us show you the right information and personalize your experience in line with your settings. For example, cookies enable LinkedIn to identify you and verify your account. Security We use cookies and similar technologies to make your interactions with our Services faster and more secure. For example, we use cookies to enable and support our security features, keep your account safe and to help us detect malicious activity and violations of our User Agreement. Preferences, features and services We use cookies and similar technologies to enable the functionality of our Services, such as helping you to fill out forms on our Services more easily and providing you with features, insights and customized content in conjunction with our plugins. We also use these technologies to remember information about your browser and your preferences. For example, cookies can tell us which language you prefer and what your communications preferences are. We may also use local storage to speed up site functionality. Customized content We use cookies and similar technologies to customize your experience on our Services. For example, we may use cookies to remember previous searches so that when you return to our services, we can offer additional information that relates to your previous search. Plugins on and off LinkedIn We use cookies and similar technologies to enable LinkedIn plugins both on and off the LinkedIn sites. For example, our plugins, including the "Apply with LinkedIn" button or the "Share" button may be found on LinkedIn or third-party sites, such as the sites of our customers and partners. Our plugins use cookies and other technologies to provide analytics and recognize you on LinkedIn and third-party sites. If you interact with a plugin (for instance, by clicking "Apply"), the plugin will use cookies to identify you and initiate your request to apply. You can learn more about plugins in our Privacy Policy . Advertising Cookies and similar technologies help us show relevant advertising to you more effectively, both on and off our Services and to measure the performance of such ads. We use these technologies to learn whether content has been shown to you or whether someone who was presented with an ad later came back and took an action (e.g., downloaded a white paper or made a purchase) on another site. Similarly, our partners or service providers may use these technologies to determine whether we've shown an ad or a post and how it performed or provide us with information about how you interact with ads. We may also work with our customers and partners to show you an ad on or off LinkedIn, such as after you’ve visited a customer’s or partner’s site or application. These technologies help us provide aggregated information to our customers and partners. For further information regarding the use of cookies for advertising purposes, please see Sections 1.4 and 2.4 of the Privacy Policy . As noted in Section 1.4 of our Privacy Policy, outside Designated Countries , we also collect (or rely on others who collect) information about your device where you have not engaged with our Services (e.g., ad ID, IP address, operating system and browser information) so we can provide our Members with relevant ads and better understand their effectiveness. For further information, please see Section 1.4 of the Privacy Policy . Analytics and research Cookies and similar technologies help us learn more about how well our Services and plugins perform in different locations. We or our service providers use these technologies to understand, improve, and research products, features and services, including as you navigate through our sites or when you access LinkedIn from other sites, applications or devices. We or our service providers, use these technologies to determine and measure the performance of ads or posts on and off LinkedIn and to learn whether you have interacted with our websites, content or emails and provide analytics based on those interactions. We also use these technologies to provide aggregated information to our customers and partners as part of our Services. If you are a LinkedIn member but logged out of your account on a browser, LinkedIn may still continue to log your interaction with our Services on that browser until the expiration of the cookie in order to generate usage analytics for our Services. We may share these analytics in aggregate form with our customers. What third parties use these technologies in connection with our Services? Third parties such as our customers, partners and service providers may use cookies in connection with our Services. For example, third parties may use cookies in their LinkedIn pages, job posts and their advertisements on and off LinkedIn for their own marketing purposes. For an illustration, please visit LinkedIn’s Help Center . Third parties may also use cookies in connection with our off-site Services, such as LinkedIn ad services. Third parties may use cookies to help us to provide our Services. We may also work with third parties for our own marketing purposes and to enable us to analyze and research our Services. Your Choices You have choices on how LinkedIn uses cookies and similar technologies. Please note that if you limit the ability of LinkedIn to set cookies and similar technologies, you may worsen your overall user experience, since it may no longer be personalized to you. It may also stop you from saving customized settings like login information. Opt out of targeted advertising As described in Section 2.4 of the Privacy Policy , you have choices regarding the personalized ads you may see. LinkedIn Members can adjust their settings here . Visitor controls can be found here . Some mobile device operating systems such as Android provide the ability to control the use of mobile advertising IDs for ads personalization. You can learn how to use these controls by visiting the manufacturer’s website. We do not use iOS mobile advertising IDs for targeted advertising. Browser Controls Most browsers allow you to control cookies through their settings, which may be adapted to reflect your consent to the use of cookies. Further, most browsers also enable you to review and erase cookies, including LinkedIn cookies. To learn more about browser controls, please consult the documentation that your browser manufacturer provides. What is Do Not Track (DNT)? DNT is a concept that has been promoted by regulatory agencies such as the U.S. Federal Trade Commission (FTC), for the Internet industry to develop and implement a mechanism for allowing Internet users to control the tracking of their online activities across websites by using browser settings. As such, LinkedIn does not generally respond to “do not track” signals. Other helpful resources To learn more about advertisers’ use of cookies, please visit the following links: Internet Advertising Bureau (US) European Interactive Digital Advertising Alliance (EU) Internet Advertising Bureau (EU) LinkedIn © 2026 About Accessibility User Agreement Privacy Policy Cookie Policy Copyright Policy Brand Policy Guest Controls Community Guidelines العربية (Arabic) বাংলা (Bangla) Čeština (Czech) Dansk (Danish) Deutsch (German) Ελληνικά (Greek) English (English) Español (Spanish) فارسی (Persian) Suomi (Finnish) Français (French) हिंदी (Hindi) Magyar (Hungarian) Bahasa Indonesia (Indonesian) Italiano (Italian) עברית (Hebrew) 日本語 (Japanese) 한국어 (Korean) मराठी (Marathi) Bahasa Malaysia (Malay) Nederlands (Dutch) Norsk (Norwegian) ਪੰਜਾਬੀ (Punjabi) Polski (Polish) Português (Portuguese) Română (Romanian) Русский (Russian) Svenska (Swedish) తెలుగు (Telugu) ภาษาไทย (Thai) Tagalog (Tagalog) Türkçe (Turkish) Українська (Ukrainian) Tiếng Việt (Vietnamese) 简体中文 (Chinese (Simplified)) 正體中文 (Chinese (Traditional)) Language | 2026-01-13T08:48:28 |
https://stackoverflow.co/advertising/employer-branding/?utm_source=so-owned&utm_medium=blog&utm_campaign=nav-side-bar | Reach and engage developers - Stack Overflow Business Stack Internal Stack Data Licensing Stack Ads Partnerships Resources Learn Solution resources Stack Internal Stack Ads Blog Research insights Support Stack Internal Help Legal policies Talk to an expert 183 Unique communities to engage with Reach developers where it matters — in their daily workflow Stack Ads connects your brand to the world’s most trusted developer community. Why advertise on Stack Overflow? 82% of devs visit Stack Overflow multiple times per month (source) 62% of devs have an influence in the purchase of new technology (source) Millions of average monthly unique visitors across our platforms Reach developers. Speak their language. Cut through the noise. Stack Ads lets you run targeted campaigns based on skills, tags and interests — so you can reach more of the right people. Things to note Creative guidlines Advertising policy Reach the right devs (lots of them) With communities built around every interest and millions of monthly visitors, finding and targeting the right talent just got a little easier. Track what works, make it better No more broad ad channels, wasted spend or bad dev fits. We’ll give you tools to track engagement, fine-tune your approach and optimize your ROI. Build trust in your brand Show up in trusted, dev-first environments and earn the respect and recognition of discerning dev communities. How Stack Ads can help you Marketing teams Agencies Employee brand teams Talent teams Technology teams Marketing teams Find ad solutions to reach developers and technologists at scale. Run ads in the places where developers are switched-on, focused and open to new ideas. Grow your audience with interest-based targeting. Agencies Unlock the developer audience for your clients. Get discerning devs interested in your client’s story, product or service. Connect your clients to the best tech talent. Employee brand teams Millions of devs want to hear your story. We’ll help you tell it. Build a rich employer brand for devs already working for you – and devs who’ll want to. Build and strengthen your brand rep in the wider dev community. Talent teams Build a pipeline of high quality tech talent. Find devs with the skills and experience you’re looking for. Make your budget go further and speed up your hiring cycles. Give employees more reasons to care — and more reasons to stay. Technology teams Great developers are hard to find. We make it easier. Help your teams do their best work by adding the right skills to your stack. Strengthen your rep and show off your teams’ talents in a thriving dev-first community. Dedicated to your success Got specific goals you want to hit, or need help building a strategy to get there? Get in touch, and we'll figure it out together. Get in touch 01 Setting the strategy Your dedicated success manager will run a session to help define your goals — and then build a strategy to meet them. 02 Checking in Support doesn't stop at strategy. In regular check-ins your account manager will track your campaign, suggest tweaks, and look for ways to save you time and money. 03 Testing and learning Your account manager will tap into analytics, reports, and the knowledge of our entire dev marketing team, to help improve your campaign. Mix and match the tools you need Targeted advertising Our targeted advertising options allow you to get ads in front of developers in their workflow in a non-intrusive way. Banner advertising Topic Tag Sponsorship Dedicated company pages Build brand awareness with your own dedicated company pages & page ads which offer a compelling way for your company to stay top-of-mind with relevant developer and tech talent by telling your story. Company Pages Company Page Ads Sponsored media Premium media placements get your employer brand in front of the Stack Overflow community and help position your company as a thought leader and employer of choice. Podcast Advertising Sponsored Podcasts Newsletter Advertising Sponsored Blog Posts Companies already on Stack Overflow See more on stackoverflow.com American Express. London; Burgess Hill; Brighton Finance, Financial Services, Financial Technology Joining Amex Tech means discovering and shaping your contribution to something big. Here, you can work alongside talented tech teams and buil... java python hadoop Audible London; Berlin; Cambridge Agile Software Development, Content Marketing, Web Technology Imagine Your Possibilities at Audible.This is a place of invention and inspiration. For more than 25 years, we have been a leading creator and... java git jquery Ford Motor Company Dearborn; Palo Alto Automotive, Information Technology, Manufacturing Ford's engineering team is a global network of talented individuals dedicated to designing, developing, and manufacturing the next generation of Ford... angular-cli-v6 karma-runner file Capital One Cambridge; New York; Philadelphia Financial Services, Financial Technology We use real-time data at scale, AI and machine learning and the power of the cloud to solve challenging industry problems. javascript java cassandra Intuit London; Paris; Petah Tikva Computer Software, Financial Technology Intuit is the global technology platform that powers prosperity for the people and communities we serve with TurboTax, Credit Karma, QuickBooks, and... java kotlin scala New content Vanguard Malvern; Charlotte; Dallas Financial Services, Financial Technology, Information Technology kotlin sdk ios Frequently Asked Questions Q&A is our speciality, find out more about Stack Ads. Expand all What is Stack Ads? Stack Ads is a developer-first advertising solution that connects brands and employers to the world’s most trusted developer community, delivering unmatched engagement and measurable outcomes. What audience can I reach on Stack Overflow? Stack Overflow is the largest community of developers, technical decision-makers and technology enthusiasts with millions of monthly visitors. How do I advertise on Stack Overflow? Stack Ads solutions enable you to place ads and sponsored content directly within the developer workflow, using precision, skill-based targeting to reach the right technical buyers and decision-makers. What types of advertising formats are available? Stack Ads offers a wide range of native and display formats, including display ads, technical content sponsorships and company pages. What are the available targeting options? Stack Ads provides precision skill-based targeting, allowing you to reach developers based on specific tags that reflect skills and technologies. Furthermore, campaigns can be targeted using user intent, role, historical behavior, and technology-specific segmentation. Does Stack Overflow offer employer branding solutions? Yes. For talent acquisition leaders and employer branding teams that need to attract high-quality, hard-to-reach developers in a saturated market, Stack Ads connects your employer brand with developers where they go to learn, solve problems, and grow their careers. How do I get started with an advertising campaign on Stack Overflow? The best way to get started is by connecting with our team. CSM support is available for media ROI and content strategy, along with clear campaign dashboards to help define goals, manage budgets, and launch a developer marketing campaign efficiently. What are the pricing or minimum spend requirements? To receive information on pricing, minimum spends, and custom packages tailored to your B2B marketing or employer branding goals, please contact our team. Reach a global community of developers and technologists. Talk to sales Stay updated Subscribe to receive Stack Overflow Business content around knowledge sharing, collaboration, and AI. Receive updates Our Stack Stack Internal Features Customers Security Pricing Stack Data Licensing Stack Ads Partnerships Services Stack Overflow Company Leadership Press Careers Social Impact Support Contact Stack Overflow help Stack Internal help Terms Privacy policy Cookie policy Your Privacy Choices Elsewhere Blog Dev Newsletter Podcast Releases Dev Survey Site design / logo © 2025 Stack Exchange Inc. | 2026-01-13T08:48:28 |
https://dev.to/hoangleitvn/the-builds-that-last-manifesto-218c#maintenance-costs-more-than-building | The Builds That Last Manifesto - DEV Community Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account DEV Community Close Add reaction Like Unicorn Exploding Head Raised Hands Fire Jump to Comments Save Boost More... Copy link Copy link Copied to Clipboard Share to X Share to LinkedIn Share to Facebook Share to Mastodon Share Post via... Report Abuse Hoang Le Posted on Jan 11 The Builds That Last Manifesto # productivity # programming # architecture # career Originally published on Builds That Last . I've been building and leading engineering teams for 15 years. Over 50 projects. Startups, enterprises, legacy systems, greenfield builds. Same pattern every time. Teams ship fast. Then they slow down. Not because engineers got lazy. Because the foundation was never there. At my company, we maintain systems 20+ years old. No documentation. No standards. When we ask stakeholders about business logic, they say "read the code". My teams sometimes decompile binary files just to understand what's inside. Debug at runtime because that's the only way to see how things work. Previous teams deployed code to AWS without committing to source control. Gone. This is what engineering looks like for most of us. Not the AI demos. Not the apps shipped in a weekend. The gap between posts and reality You'll see posts about vibe coding, AI-augmented development, shipping apps in hours. I'm not saying AI isn't real. I use these tools every day. The productivity gains are real. But there's a gap between what people post and what I see in actual projects. The posts show demos that work. Reality is production systems that break. The posts celebrate shipping fast. Reality is teams spending months paying back technical debt. The demo works. The demo always works. It's what comes after that separates software that lasts from software that collapses. The iceberg problem What you see is 20% above water. The shiny demos. The fast shipping. Vibe coding, agentic AI, apps built in hours. What you don't see is the 80% below: → Maintenance → Technical debt → Engineers connecting systems never meant to work together → Data inconsistencies accumulated over years → Teams spending days understanding what the previous developer was thinking That 80% is where my teams spend most of our time. And it's where the real lessons are. The speed trap I see this pattern repeat. A team starts fast. AI tools, modern stack, motivated engineers. First version ships in weeks. Everyone celebrates. Then users show up. Edge cases appear. The payment flow breaks. Data sync fails silently. Features that worked in demo crash under real load. Suddenly the team that was "moving fast" spends months fixing things. Not building new features. Just paying back debt from shipping without foundation. Leadership gets frustrated. "Why is the team slow now?" The team isn't slow. They're doing work that should have been done upfront. Speed without foundation creates the illusion of progress. Then reality catches up. Maintenance costs more than building Here's something most people don't think about until it's too late. Maintaining software costs more than building it from scratch. Think about repairing a house. You don't just fix the broken part. You investigate the structure. Remove old materials. Work around things that can't be changed. Then build the new thing. Software is the same. When you inherit a system without documentation, without standards, every change becomes an archaeology project. You spend more time understanding than building. The time you "save" by skipping foundation gets paid back with interest during maintenance. The AI paradox AI makes code generation 10x faster. That's real. AI also increases cognitive load by 30-40%. When AI generates code, someone still needs to verify it's secure. Check for edge cases. Understand the logic before shipping. Maintain it when something breaks. AI doesn't eliminate this work. It changes who's responsible for catching problems. Anthropic's CEO said 90% of their internal code is now AI-generated. The follow-up: "We're not replacing engineers". The 10% humans handle? That's the leverage zone. Architecture decisions. Debugging complex problems. Understanding why something should work, not just what it should do. AI is a turbo, not a robot. Good foundation? AI makes you faster at building good software. Bad foundation? AI makes you faster at building bad software. What this means for engineers The fundamentals matter more than ever. Everyone has access to AI now. The differentiator isn't who prompts better. It's who understands what they're building deeply enough to know when AI helps and when it hurts. Own your code. "The AI wrote it" isn't an excuse when something breaks at 2am. You shipped it. You're responsible. Read the code. Understand the logic. Ship with confidence. The 80% below water is where you build real skills. Legacy systems, maintenance, debugging. Not glamorous. But it's where you learn how software actually behaves. Don't avoid it. Embrace it. What this means for leaders You're only seeing 20% of what your team deals with. The demos work. Sprint reports look fine. But your team might be drowning in the 80% you don't see. The legacy code. Missing documentation. Tribal knowledge that walks out when someone leaves. Buying tools is easy. Training is hard. Teams that succeed with AI invested in foundation first. Standards, process, documentation. Then added AI. Teams that struggle added tools to existing chaos. Now they have faster chaos. Remove friction before adding speed. When you want to go faster, the instinct is to add more. More tools, more people, more pressure. Usually, the answer is to remove things. Remove blockers. Remove unnecessary process. Remove friction slowing your team down. The bottom line Real speed comes from clarity, not from typing faster. In the AI era, shipping is easy. Building to last is what matters. Those legacy systems with no documentation? They taught me more than any greenfield project. Not because they were well-built. Because they showed what happens when foundation is missing. Every time I build something new, I think about the engineer maintaining it in 10 years. Will they understand our decisions? Can they change things confidently? Or will they be stuck doing archaeology? That's what foundation means. Building for the people who come after. What's your experience with the 80% below water? I write about foundation-first engineering at Builds That Last . Top comments (0) Subscribe Personal Trusted User Create template Templates let you quickly answer FAQs or store snippets for re-use. Submit Preview Dismiss Code of Conduct • Report abuse Are you sure you want to hide this comment? It will become hidden in your post, but will still be visible via the comment's permalink . Hide child comments as well Confirm For further actions, you may consider blocking this person and/or reporting abuse Hoang Le Follow Engineering leader. Founder @ INNOMIZE. Building cloud-native systems for startups. Writing about platform engineering and technical leadership at Builds that Last. Location Vietnam Education The Degree of Engineer Information Technology Work Co-Founder, CEO, CTO at INNOMIZE Joined Oct 26, 2019 Trending on DEV Community Hot If a problem can be solved without AI, does AI actually make it better? # ai # architecture # discuss Prompt Engineering Won’t Fix Your Architecture # discuss # career # ai # programming MAWA - El lenguaje simple en sintaxis como Python de bajo nivel. Parte 3, Condicionales. # programming # beginners # showdev # codenewbie 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV DEV Community — A space to discuss and keep up software development and manage your software career Home DEV++ Podcasts Videos DEV Education Tracks DEV Challenges DEV Help Advertise on DEV DEV Showcase About Contact Free Postgres Database Software comparisons Forem Shop Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . DEV Community © 2016 - 2026. We're a place where coders share, stay up-to-date and grow their careers. Log in Create account | 2026-01-13T08:48:28 |
https://stackoverflow.blog/2025/07/08/better-performance-smarter-workflows-what-s-new-in-stack-overflow-for-teams/ | Better performance, smarter workflows: What’s new in Stack Overflow for Teams - Stack Overflow Blog Loading… Everything Productivity AI/ML Open Source Business Hub Company Releases Podcast Newsletter Stack Overflow Business Stack Internal : the knowledge intelligence layer that powers enterprise AI. Stack Data Licensing : decades of verified, technical knowledge to boost AI performance and trust. Stack Ads : engage developers where it matters — in their daily workflow. July 8, 2025 Better performance, smarter workflows: What’s new in Stack Overflow for Teams Our July 2025 release focuses on stability, integration, and actionable insight—designed to help your teams stay informed, secure, and efficient as they scale. Our July 2025 release focuses on stability, integration, and actionable insight—designed to help your teams stay informed, secure, and efficient as they scale. Whether you're enabling AI-driven workflows, tightening access controls, or just looking for a smoother daily experience, this update brings meaningful improvements to how users interact with your knowledge base. Here’s what’s new in the 2025.5 Enterprise release. Microsoft Teams Personal Digests: Personalized insight, now in your DMs Following Slack personal and channel digests and Microsoft Teams channel digests, we’re rounding out the digest lineup with a final addition: personal digests delivered directly via Microsoft Teams direct messages. These weekly summaries surface what matters most to each user—their impact, key actions to follow up on, and trending content from the communities they care about. It’s a low-effort way to stay connected to your knowledge base, and it’s fully user-controlled: anyone can opt in or out from the Teams app settings under “Notifications.” With this addition, users across platforms can stay engaged and in the loop—without needing to check Stack Overflow daily. Better boundaries: Separate allow lists for API and UI access Enterprise customers often need tighter control over what can access their Stack Overflow for Teams instance. With this release, you can now configure separate IP allow lists for the application UI and the API endpoint. This added granularity means you can permit backend integrations to use the API from specific ranges—while restricting UI access to a different set. It reduces the risk of inadvertently blocking valid automation workflows while maintaining strong safeguards against unauthorized access. For security-conscious teams operating in regulated environments, this change brings welcome flexibility and control. Stack Overflow meets LangChain: A new document loader for AI agents As more customers build internal tooling powered by large language models, we’re making it easier to bring Stack Overflow knowledge into the mix. The new LangChain-compatible document loader offers a plug-and-play way to extract Stack Overflow for Teams content via our API v3. Whether you're building RAG apps, copilots, or internal search assistants, this reference implementation helps you skip the scaffolding and get straight to integration. It’s also a foundational step toward broader MCP use cases, where APIs drive deeper, smarter connections between your tools and your team’s knowledge. Improved visibility with /communities API enhancements Need to sync all your communities into an internal portal? Assign access policies by team or topic? Build governance or reporting workflows? We’ve updated our /communities API endpoint to return a complete, paginated list of all communities in your instance—accurately and reliably. This means better automation, less guesswork, and more confidence in the systems that depend on your knowledge structure. It’s a small change with big implications for teams operating at scale. And behind the scenes: Infrastructure and usability upgrades This release also represents a significant investment in the platform’s foundation. Over the past quarter, our teams have focused on resolving a backlog of long-standing usability issues and upgrading infrastructure for performance and reliability. You might not see these updates in a headline—but you’ll feel them in a smoother, faster experience, whether you’re browsing questions, updating tags, or toggling between communities. We’ll keep listening, iterating, and polishing—because your workflows deserve it. Ready to explore? All features in the 2025.5 release will be live in Enterprise environments by 12pm ET on July 9, 2025 . To learn more, visit the release notes , or reach out to your Customer Success partner with any questions. Thanks for continuing to build and learn with Stack Overflow for Teams. Author s Carrie Koos Staff Stack Internal Releases Stack Overflow Internal Where developers & technologists share private knowledge with coworkers. Learn more Latest releases January 5, 2026 What’s new at Stack Overflow: January 2026 December 16, 2025 Your 2025 Stacked: A year of knowledge, community, and impact December 1, 2025 What’s new at Stack Overflow: December 2025 November 12, 2025 2025.8 release introduces Stack Overflow Internal: The next generation of enterprise knowledge intelligence Add to the discussion Login with your stackoverflow.com account to take part in the discussion. Our Stack Stack Internal Features Customers Security Pricing Stack Data Licensing Stack Ads Partnerships Services Stack Overflow Company Leadership Press Careers Social Impact Support Contact Stack Overflow help Stack Internal help Terms Privacy policy Cookie policy Your Privacy Choices Elsewhere Blog Dev Newsletter Podcast Releases Dev Survey Site design / logo © 2026 Stack Exchange Inc. Light Dark Auto | 2026-01-13T08:48:28 |
https://support.apple.com/en-gb/105082 | Delete your Safari history, cache and cookies on iPhone – Apple Support (UK) Apple Store Mac iPad iPhone Watch Vision AirPods TV & Home Entertainment Accessories Support 0 + Delete your Safari history, cache and cookies on iPhone In your iPhone settings, you can choose to delete your Safari history, cookies, cache or a specific website from your history. You can also turn on content blockers. Delete your history, cache and cookies Clear your cookies and the cache, but keep your history Delete a website from your history Block cookies Use content blockers Delete history, cache and cookies Go to Settings > Apps > Safari. Scroll down and tap Clear History and Website Data. Confirm the timeframe you want to clear, then tap Clear History. This doesn’t change your AutoFill information. If this button is grey, there is either no data to clear, or you may need to check your web content restrictions in Screen Time . Clear your cookies and the cache, but keep your history Go to Settings > Apps > Safari > Advanced > Website Data. Tap Remove All Website Data. If this button is grey, there is either no data to clear, or you may need to check your web content restrictions in Screen Time . Tap Remove Now. This clears data that’s used for tracking, and by websites to save login information for faster browsing. Delete a website from your history Open the Safari app, then tap the More button . Tap Bookmarks. Tap the History button , then tap the More button again. Tap Select Websites, then select one or more websites to delete from your history. Tap the Bin button . Block cookies If you want to block cookies (data a site places on your device to remember you), go to Settings > Apps > Safari > Advanced. Turn on Block All Cookies. Tap Block All. This will remove all existing cookies and website data. Safari quits, and your tabs will be reloaded. If you block cookies, some web pages may not work. Here are some examples: You will likely not be able to sign in to a site, even when using your correct username and password. You may see a message that cookies are required or that your browser’s cookies are turned off. Some features on a site may not work. Use content blockers Go to the App Store and download a content blocking app (third-party apps and extensions that let Safari block cookies, images, resources, pop-ups and other content). Then tap Settings > Apps > Safari > Extensions. Tap to turn on a listed content blocker. You can use more than one content blocker. If you need help, contact the app developer . Information about products not manufactured by Apple, or independent websites not controlled or tested by Apple, is provided without recommendation or endorsement. Apple assumes no responsibility with regard to the selection, performance or use of third-party websites or products. Apple makes no representations regarding third-party website accuracy or reliability. Contact the vendor for additional information. Published Date: September 24, 2025 Helpful? Yes No Character limit: 250 Maximum character limit is 250. Please don’t include any personal information in your comment. Submit Thanks for your feedback. Related topics Apple Footer Apple Support Delete your Safari history, cache and cookies on iPhone UK Copyright © 2025 Apple Inc. All rights reserved. Privacy Policy Terms of Use Sales and Refunds Site Map Use of Cookies | 2026-01-13T08:48:28 |
https://dev.to/imranhashmi127/comment/22cbo#main-content | is there any way to get YouTube API Unlimited source ? - DEV Community Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account DEV Community Close Discussion on: Episode 1: APIs and Bikes Go Together Great View post Collapse Expand imranhashmi127 imranhashmi127 imranhashmi127 Follow Joined Oct 19, 2022 • Oct 19 '22 • Edited on Oct 26 • Edited Dropdown menu Copy link Hide is there any way to get YouTube API Unl i mited source ? Like comment: Like comment: 1 like Like Comment button Reply Code of Conduct • Report abuse Are you sure you want to hide this comment? It will become hidden in your post, but will still be visible via the comment's permalink . Hide child comments as well Confirm For further actions, you may consider blocking this person and/or reporting abuse 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV DEV Community — A space to discuss and keep up software development and manage your software career Home DEV++ Podcasts Videos DEV Education Tracks DEV Challenges DEV Help Advertise on DEV DEV Showcase About Contact Free Postgres Database Software comparisons Forem Shop Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . DEV Community © 2016 - 2026. We're a place where coders share, stay up-to-date and grow their careers. Log in Create account | 2026-01-13T08:48:28 |
https://dev.to/adventuresinangular/writing-clean-http-service-methods-with-walid-bouguima-aia-365#main-content | Writing Clean Http Service Methods With Walid Bouguima - AiA 365 - DEV Community Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account DEV Community Close Adventures in Angular Follow Writing Clean Http Service Methods With Walid Bouguima - AiA 365 Jan 12 '23 play Walid Bouguima is a Software Engineer at Hilti Group. He joins the show with Chuck, Lucas, and Subrat to discuss his article, " Angular Clean Http Service Methods: Handle Your Backend Communication With Ease". He explains his goals and reasons why he created this method and what advantages it may bring to developers in the Angular community. Moreover, the panel shares their own perspective and some tips about Walid's article. On YouTube Writing Clean Http Service Methods With Walid Bouguima - AiA 365 Sponsors Chuck's Resume Template Developer Book Club starting with Clean Architecture by Robert C. Martin Become a Top 1% Dev with a Top End Devs Membership Links Angular Clean Http Service Methods: Handle Your Backend Communication With Ease😎 axios - npm GraphQL NestJS lucaspaganini.com/web-animations unvoid.com Picks Charles - The Game | Board Game | BoardGameGeek Charles - RedCircle Charles - Disney Mirrorverse: Home Charles - Slack | Top End Devs Lucas - Reaper Lucas - For Perfectionists - Produce Live Content Subrat - Clean Code: A Handbook of Agile Software Craftsmanship Advertising Inquiries: https://redcircle.com/brands Privacy & Opt-Out: https://redcircle.com/privacy Episode source Personal Trusted User Create template Templates let you quickly answer FAQs or store snippets for re-use. Submit Preview Dismiss Your browser does not support the audio element. 1x initializing... × 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV DEV Community — A space to discuss and keep up software development and manage your software career Home DEV++ Podcasts Videos DEV Education Tracks DEV Challenges DEV Help Advertise on DEV DEV Showcase About Contact Free Postgres Database Software comparisons Forem Shop Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . DEV Community © 2016 - 2026. We're a place where coders share, stay up-to-date and grow their careers. Log in Create account | 2026-01-13T08:48:28 |
https://forem.com/t/programming/page/75 | Programming Page 75 - Forem Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account DEV Community Close Programming Follow Hide The magic behind computers. 💻 🪄 Create Post Older #programming posts 72 73 74 75 76 77 78 79 80 Posts Left menu 👋 Sign in for the ability to sort posts by relevant , latest , or top . Right menu Fixing the Fatal Flaw in Your AI Pipeline Malik Abualzait Malik Abualzait Malik Abualzait Follow Dec 18 '25 Fixing the Fatal Flaw in Your AI Pipeline # ai # tech # programming # tutorial Comments Add Comment 3 min read I built a privacy-first IP API and it's free. Arshvir Arshvir Arshvir Follow Dec 17 '25 I built a privacy-first IP API and it's free. # discuss # programming # webdev # opensource Comments Add Comment 1 min read Firehose and Iceberg Tables Evan Evan Evan Follow Dec 17 '25 Firehose and Iceberg Tables # programming # dataengineering # aws # awsdatalake Comments Add Comment 4 min read Why Version Control Exists: The Pendrive Problem Ritam Saha Ritam Saha Ritam Saha Follow Dec 30 '25 Why Version Control Exists: The Pendrive Problem # git # github # beginners # programming 1 reaction Comments 1 comment 7 min read Week 11: Prisma! Nikhil Sharma Nikhil Sharma Nikhil Sharma Follow Dec 17 '25 Week 11: Prisma! # webdev # programming # beginners # javascript Comments Add Comment 3 min read CSS Combinators Explained: A Practical Guide for Web Developers Satyam Gupta Satyam Gupta Satyam Gupta Follow Dec 17 '25 CSS Combinators Explained: A Practical Guide for Web Developers # css # webdev # programming # beginners Comments Add Comment 5 min read Main Branch: A Newsletter About Fundamentals First Always Andrea Liliana Griffiths Andrea Liliana Griffiths Andrea Liliana Griffiths Follow Dec 17 '25 Main Branch: A Newsletter About Fundamentals First Always # webdev # programming # javascript # github 1 reaction Comments Add Comment 2 min read Kibana – DevSecOps Tool Overview Kanishka L Kanishka L Kanishka L Follow Dec 18 '25 Kibana – DevSecOps Tool Overview # devops # webdev # programming # tutorial Comments Add Comment 2 min read CSS Pseudo-Elements Guide: Cleaner Code & Creative Styling Techniques Satyam Gupta Satyam Gupta Satyam Gupta Follow Dec 18 '25 CSS Pseudo-Elements Guide: Cleaner Code & Creative Styling Techniques # css # webdev # programming # beginners Comments Add Comment 6 min read Lessons From Debugging AI Reasoning Errors in Production Rohit Gavali Rohit Gavali Rohit Gavali Follow Dec 17 '25 Lessons From Debugging AI Reasoning Errors in Production # webdev # programming # ai Comments Add Comment 12 min read How Bf-Tree Executes Reads and Writes Using Mini-Pages Athreya aka Maneshwar Athreya aka Maneshwar Athreya aka Maneshwar Follow Dec 20 '25 How Bf-Tree Executes Reads and Writes Using Mini-Pages # webdev # programming # database # architecture 15 reactions Comments Add Comment 4 min read Compliance Levels rokoss21 rokoss21 rokoss21 Follow Dec 16 '25 Compliance Levels # webdev # programming # ai # architecture Comments Add Comment 3 min read FACET vs Existing Approaches rokoss21 rokoss21 rokoss21 Follow Dec 16 '25 FACET vs Existing Approaches # webdev # programming # ai # architecture Comments Add Comment 5 min read Week 1: My Android Learning Journey Vibhas Natekar Vibhas Natekar Vibhas Natekar Follow Dec 17 '25 Week 1: My Android Learning Journey # programming # android # java # androiddev Comments Add Comment 1 min read คุยกันเรื่อง Writing Better Go: Lessons from 10 Code Reviews Pallat Anchaleechamaikorn Pallat Anchaleechamaikorn Pallat Anchaleechamaikorn Follow Jan 9 คุยกันเรื่อง Writing Better Go: Lessons from 10 Code Reviews # codequality # go # learning # programming 1 reaction Comments Add Comment 1 min read Which AI Model Is Best for Coding and Why Farhad Rahimi Klie Farhad Rahimi Klie Farhad Rahimi Klie Follow Jan 10 Which AI Model Is Best for Coding and Why # ai # chatgpt # claude # programming Comments Add Comment 4 min read Kavia v1.0.9: Interactive agents, SCM onboarding, and persistent code context Kavita Kavita Kavita Follow Dec 17 '25 Kavia v1.0.9: Interactive agents, SCM onboarding, and persistent code context # programming # ai # softwareengineering # devtools Comments Add Comment 1 min read Why Hybrid and Multi Cloud Strategies Are Essential in 2026 Miran Sabir Miran Sabir Miran Sabir Follow Dec 17 '25 Why Hybrid and Multi Cloud Strategies Are Essential in 2026 # webdev # programming # ai # javascript Comments Add Comment 4 min read Functions in JavaScript Harini Harini Harini Follow Dec 17 '25 Functions in JavaScript # javascript # programming # beginners # basic 1 reaction Comments Add Comment 1 min read Building Your First MCP Server in Python OnlineProxy OnlineProxy OnlineProxy Follow Dec 16 '25 Building Your First MCP Server in Python # programming # ai # beginners # tutorial Comments Add Comment 7 min read O Renascimento das Linguagens de Sistemas: Rust e Go na Era da Eficiência (2025-2026) Kauê Matos Kauê Matos Kauê Matos Follow Jan 10 O Renascimento das Linguagens de Sistemas: Rust e Go na Era da Eficiência (2025-2026) # go # webdev # programming # rust 3 reactions Comments Add Comment 4 min read What Is an API? A Simple Way to Understand It Surhid Amatya Surhid Amatya Surhid Amatya Follow Dec 21 '25 What Is an API? A Simple Way to Understand It # webdev # programming # api Comments Add Comment 2 min read Complete Guide to JWT Authentication in Next.js 15: From Setup to Production sizan mahmud0 sizan mahmud0 sizan mahmud0 Follow Dec 21 '25 Complete Guide to JWT Authentication in Next.js 15: From Setup to Production # webdev # programming # nextjs # jwt 3 reactions Comments Add Comment 6 min read AI Powerhouses: How to Leverage Joint Neural Networks in Multimodal Apps Malik Abualzait Malik Abualzait Malik Abualzait Follow Dec 17 '25 AI Powerhouses: How to Leverage Joint Neural Networks in Multimodal Apps # ai # tech # programming # tutorial Comments Add Comment 3 min read The Modern Scrapy Developer's Guide (Part 3): Auto-Generating Page Objects with Web Scraping Co-pilot John Rooney John Rooney John Rooney Follow for Zyte Dec 16 '25 The Modern Scrapy Developer's Guide (Part 3): Auto-Generating Page Objects with Web Scraping Co-pilot # tutorial # scrapy # programming # webscraping Comments Add Comment 5 min read loading... 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV DEV Community — Your community HQ Home About Contact Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . DEV Community © 2016 - 2026. We're a blogging-forward open source social network where we learn from one another Log in Create account | 2026-01-13T08:48:28 |
https://www.linkedin.com/jobs/search?trk=guest_homepage-basic_guest_nav_menu_jobs | 3,664,000+ jobs in United States Skip to main content LinkedIn United States Expand search This button displays the currently selected search type. When expanded it provides a list of search options that will switch the search inputs to match the current selection. Jobs People Learning Clear text Clear text Clear text Clear text Clear text Sign in Create an account Any time Any time (3,532,065) Past month (2,420,839) Past week (1,180,962) Past 24 hours (197,652) Done Company Clear text Lensa (2,980) Jobgether (1,828) South Bromsgrove High Teaching School (441) Steve Madden (306) Blackbird Health (56) Done Job type Full-time (2,835,292) Part-time (565,382) Contract (104,821) Temporary (29,518) Volunteer (2,700) Done Experience level Internship (113,787) Entry level (1,914,735) Associate (110,986) Mid-Senior level (984,037) Director (89,050) Done Location Clear text New York, NY (84,639) Houston, TX (41,387) Atlanta, GA (29,075) Washington, DC (21,956) Phoenix, AZ (21,868) Done Salary $40,000+ (186,190) $60,000+ (148,714) $80,000+ (124,536) $100,000+ (102,486) $120,000+ (83,433) Done Remote On-site (2,986,675) Remote (332,800) Hybrid (305,874) Done 3,664,000+ Jobs in United States Marketing Assistant Marketing Assistant Steve Madden New York, NY Actively Hiring 6 hours ago Graphic Designer Graphic Designer The Fountain Group New York, NY Be an early applicant 6 hours ago Jr. Associate, People Operations Jr. Associate, People Operations Grubhub New York City Metropolitan Area Actively Hiring 4 hours ago **** ********* - ****** **** ********* - ****** ********* ****** ****** ****** 5 hours ago ********* ************ ********* ************ ****** *** ****, ** Actively Hiring +9 benefits 5 hours ago ********* ********* ********* ********* ********* *********** ****** ****** Be an early applicant 1 hour ago ** ********** *********** ** ********** *********** ********* ****** ****** Be an early applicant 50 minutes ago Sign in to view all job postings Sign in Welcome back Email or phone Password Show Forgot password? Sign in or By clicking Continue to join or sign in, you agree to LinkedIn’s User Agreement , Privacy Policy , and Cookie Policy . New to LinkedIn? Join now or By clicking Continue to join or sign in, you agree to LinkedIn’s User Agreement , Privacy Policy , and Cookie Policy . LinkedIn © 2026 About Accessibility User Agreement Privacy Policy Cookie Policy Copyright Policy Brand Policy Guest Controls Community Guidelines العربية (Arabic) বাংলা (Bangla) Čeština (Czech) Dansk (Danish) Deutsch (German) Ελληνικά (Greek) English (English) Español (Spanish) فارسی (Persian) Suomi (Finnish) Français (French) हिंदी (Hindi) Magyar (Hungarian) Bahasa Indonesia (Indonesian) Italiano (Italian) עברית (Hebrew) 日本語 (Japanese) 한국어 (Korean) मराठी (Marathi) Bahasa Malaysia (Malay) Nederlands (Dutch) Norsk (Norwegian) ਪੰਜਾਬੀ (Punjabi) Polski (Polish) Português (Portuguese) Română (Romanian) Русский (Russian) Svenska (Swedish) తెలుగు (Telugu) ภาษาไทย (Thai) Tagalog (Tagalog) Türkçe (Turkish) Українська (Ukrainian) Tiếng Việt (Vietnamese) 简体中文 (Chinese (Simplified)) 正體中文 (Chinese (Traditional)) Language Agree & Join LinkedIn By clicking Continue to join or sign in, you agree to LinkedIn’s User Agreement , Privacy Policy , and Cookie Policy . Sign in to view more jobs Sign in Welcome back Email or phone Password Show Forgot password? Sign in or By clicking Continue to join or sign in, you agree to LinkedIn’s User Agreement , Privacy Policy , and Cookie Policy . New to LinkedIn? Join now or New to LinkedIn? Join now By clicking Continue to join or sign in, you agree to LinkedIn’s User Agreement , Privacy Policy , and Cookie Policy . | 2026-01-13T08:48:28 |
https://dev.to/kolkov/why-i-rewrote-portage-in-go-introducing-grpm-v010-56j5 | Why I Rewrote Portage in Go: Introducing GRPM v0.1.0 - DEV Community Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account DEV Community Close Add reaction Like Unicorn Exploding Head Raised Hands Fire Jump to Comments Save Boost More... Copy link Copy link Copied to Clipboard Share to X Share to LinkedIn Share to Facebook Share to Mastodon Share Post via... Report Abuse Andrey Kolkov Posted on Jan 8 • Originally published at github.com Why I Rewrote Portage in Go: Introducing GRPM v0.1.0 # go # linux # opensource # programming October 2019, Gentoo Forums: Me: "I'd rather rewrite Portage on Golang." Reply: "We look forward to you having some work to show another 5 years from now." — forums.gentoo.org 6 years and ~60,000 lines of code later — here it is. If you've ever used Gentoo Linux, you know Portage. It's powerful, flexible, and... Python-based. For years — literally years — I had this persistent idea: what if Portage was written in Go? Fast compilation, single binary, no runtime dependencies, native concurrency. The idea kept coming back. Last spring, I finally decided to stop thinking and start coding. What began as "let's see how hard this is" turned into 8 months of intensive development and a complete reimplementation of a package manager. Today, I'm releasing GRPM v0.1.0 (Go Resource Package Manager) — a drop-in replacement for Portage with modern architecture and guaranteed conflict-free dependency resolution. The Problem with Traditional Package Managers Traditional dependency resolution algorithms work with heuristics. When they encounter conflicts, they often give up or make suboptimal choices. Portage's resolver is sophisticated, but it can still fail on complex dependency graphs with circular dependencies and slot conflicts. I wanted something mathematically guaranteed to find a solution if one exists. The Solution: SAT-Based Dependency Resolution GRPM uses a Boolean Satisfiability (SAT) solver at its core. Every package version becomes a Boolean variable, and every dependency becomes a logical clause: // internal/solver/gophersat_adapter.go type GophersatAdapter struct { clauses [][] int vars map [ string ] int // name@version -> var ID packages map [ string ][] * pkg . Package // name -> []versions } func ( g * GophersatAdapter ) AddPackage ( p * pkg . Package ) { key := p . Name + "@" + p . Version g . packages [ p . Name ] = append ( g . packages [ p . Name ], p ) g . getVarID ( key ) } Enter fullscreen mode Exit fullscreen mode This approach transforms dependency resolution into a well-studied mathematical problem. If a valid installation exists, the SAT solver will find it. Why SAT Solvers? Completeness : If a solution exists, it finds it Conflict handling : Multiple slot versions, blockers, USE flag constraints — all become SAT clauses Speed : Modern SAT solvers handle millions of variables GRPM uses gophersat , a pure Go SAT solver. No external dependencies, no CGO. Architecture: Clean Design with DDD GRPM follows Domain-Driven Design with a layered architecture: ┌─────────────────────────────────────┐ │ CLI / Daemon Layer │ ├─────────────────────────────────────┤ │ Application Layer │ ← Use cases ├─────────────────────────────────────┤ │ Domain Layer │ ← Business logic │ (pkg, solver) │ ├─────────────────────────────────────┤ │ Infrastructure Layer │ ← Repository, sync, install └─────────────────────────────────────┘ Enter fullscreen mode Exit fullscreen mode The domain layer knows nothing about Portage file formats or filesystem details. This makes the codebase testable and the architecture extensible. Key Features in v0.1.0 1. Full Binary Package Support GRPM supports both modern GPKG (.gpkg.tar) and legacy TBZ2 (.tbz2) formats: # Install from binary package sudo grpm install --binpkg www-servers/nginx # Build binary package from installed sudo grpm build app-misc/hello-2.10 Enter fullscreen mode Exit fullscreen mode The binary package subsystem handles: Multiple compression formats (zstd, xz, gzip, bzip2) Package signing (GPG, SSH, RSA) Remote binhost support 2. Source Building (Emerge Command) The emerge command executes full ebuild phases: # Build from source with 8 parallel jobs sudo grpm emerge --jobs 8 dev-lang/go # Show build plan first grpm emerge --pretend app-misc/hello Enter fullscreen mode Exit fullscreen mode Output: *** Dependency resolution (--pretend mode): [ebuild N ] sys-libs/zlib-1.2.13 [0] [ebuild N ] app-misc/hello-2.10 [0] Total: 2 package(s) Enter fullscreen mode Exit fullscreen mode GRPM implements all PMS phases: pkg_setup , src_unpack , src_prepare , src_configure , src_compile , src_install . 3. Native Repository Sync No external rsync binary required. GRPM uses gokrazy/rsync , a pure Go rsync implementation: # Auto-select best method sudo grpm sync # Use Git with GPG verification sudo grpm sync --method git # Native Go rsync (faster, no GPG) sudo grpm sync --method rsync Enter fullscreen mode Exit fullscreen mode 4. Daemon Architecture GRPM can run as a background service with gRPC and REST APIs: # Start daemon sudo grpm daemon # CLI auto-connects to daemon if running grpm status Enter fullscreen mode Exit fullscreen mode The daemon provides: gRPC on Unix socket ( /var/run/grpm.sock ) REST API on HTTP ( 127.0.0.1:8080 ) Job queue with conflict detection Parallel operation support 5. Transactional Updates On Btrfs or ZFS, GRPM automatically creates snapshots before package operations: # Snapshot created automatically sudo grpm install --snapshot-dir /.snapshots sys-libs/zlib Enter fullscreen mode Exit fullscreen mode If installation fails, you can roll back to the snapshot. Performance Optimization: 120x Faster Regex GRPM uses coregex instead of Go's standard regexp package. The performance difference is dramatic: Benchmark stdlib regexp coregex Speedup Compile 5,100 ns 23 ns 221x Match 185 ns 1.5 ns 123x All regex patterns are precompiled at package initialization: // internal/repo/ebuild_parser.go var ( ebuildVarRe = coregex . MustCompile ( `(?m)^([A-Z_][A-Z0-9_]*)="([^"]*)"` ) ebuildAtomVersionRe = coregex . MustCompile ( `^(.+?)-(\d.*)$` ) ) Enter fullscreen mode Exit fullscreen mode For a package manager parsing thousands of ebuilds, this optimization matters. CLI Reference GRPM provides a familiar interface for Portage users: Command Description grpm resolve Resolve dependencies with SAT solver grpm install Install packages (binary or source) grpm emerge Build packages from source grpm remove Remove installed packages grpm search Search for packages grpm info Display package information grpm sync Synchronize repository grpm update Update @world / @system packages grpm depclean Remove orphaned packages grpm status Show daemon status Pretend and Ask Modes Like Portage, GRPM supports dry-run and confirmation modes: # Show what would happen (dry-run) grpm install --pretend app-misc/hello # Ask for confirmation sudo grpm install --ask app-misc/hello Enter fullscreen mode Exit fullscreen mode Output with --ask : *** Installation plan: [ebuild N ] sys-libs/zlib-1.2.13 to / USE="..." [ebuild N ] app-misc/hello-2.10 to / USE="..." Total: 2 package(s) Would you like to merge these packages? [Yes/No] Enter fullscreen mode Exit fullscreen mode Quick Start Installation # Download wget https://github.com/grpmsoft/grpm/releases/download/v0.1.0/grpm_0.1.0_linux_x86_64.tar.gz # Extract and install tar -xzf grpm_0.1.0_linux_x86_64.tar.gz sudo install -m 0755 grpm /usr/bin/grpm # Verify grpm -V Enter fullscreen mode Exit fullscreen mode Basic Workflow # Sync repository sudo grpm sync # Search for packages grpm search firefox # Show package info grpm info dev-lang/go # Build from source sudo grpm emerge --pretend app-misc/hello sudo grpm emerge app-misc/hello # Install from binary sudo grpm install --binpkg app-misc/hello Enter fullscreen mode Exit fullscreen mode Technical Details Language : Go 1.25+ License : Apache-2.0 Platforms : Linux (x86_64, arm64, armv7, armv6, i386) Codebase : ~60,000 lines of Go Test Coverage : ~70% Dependencies GRPM uses carefully selected dependencies: Dependency Purpose gophersat SAT solver for dependency resolution cobra CLI framework grpc Daemon communication gokrazy/rsync Native rsync implementation modernc.org/sqlite Pure Go SQLite for caching coregex High-performance regex All dependencies are pure Go — no CGO required. Known Limitations GRPM v0.1.0 is a foundation release. Current limitations: Ebuild execution limited to autotools workflow (./configure && make) Limited eclass support (toolchain-funcs, eutils, multilib) No EAPI 8 features CMake/Meson build systems not supported These will be addressed in future releases. What's Next Development continues with iterative v0.x.x releases: Full EAPI 8 support CMake/Meson build system support Extended eclass support Performance optimization for large dependency graphs Community testing on real Gentoo systems v1.0.0 will come after community validation and API stabilization — no fixed timeline, quality over deadlines. Why Build This? Three reasons: Learning : Package managers are fascinating systems. Building one from scratch teaches you about dependency graphs, constraint solving, filesystem operations, and system integration. Performance : Go's performance characteristics — fast compilation, efficient memory usage, excellent concurrency — make it ideal for system tools. Community : Gentoo deserves modern tooling. If GRPM helps even a few users, the effort is worthwhile. Try It Out Repository : github.com/grpmsoft/grpm Releases : github.com/grpmsoft/grpm/releases Documentation : CLI Reference Contributions are welcome! Whether it's bug reports, feature requests, or code contributions — every bit helps. Have you tried building your own package manager? Or have experience with SAT solvers in other domains? I'd love to hear about it in the comments. Top comments (0) Subscribe Personal Trusted User Create template Templates let you quickly answer FAQs or store snippets for re-use. Submit Preview Dismiss Code of Conduct • Report abuse Are you sure you want to hide this comment? It will become hidden in your post, but will still be visible via the comment's permalink . Hide child comments as well Confirm For further actions, you may consider blocking this person and/or reporting abuse Andrey Kolkov Follow Full Stack Developer specializing in Pure Go (no CGO) & Modern Angular 1040+ ⭐ across 30+ projects | Available for consulting Joined Nov 21, 2019 More from Andrey Kolkov GRPM v0.5.0: 75% Gentoo Coverage — Rapid Development Complete # go # linux # opensource # packagemanager GxPDF v0.1.0: 100% Table Extraction Accuracy in Pure Go # go # pdf # opensource # database FURSY: The First Type-Safe HTTP Router for Go - 10M req/s with Zero Runtime Errors # go # webdev # api # opensource 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV DEV Community — A space to discuss and keep up software development and manage your software career Home DEV++ Podcasts Videos DEV Education Tracks DEV Challenges DEV Help Advertise on DEV DEV Showcase About Contact Free Postgres Database Software comparisons Forem Shop Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . DEV Community © 2016 - 2026. We're a place where coders share, stay up-to-date and grow their careers. Log in Create account | 2026-01-13T08:48:28 |
https://www.linkedin.com/legal/privacy-policy?trk=content_footer-privacy-policy | LinkedIn Privacy Policy Skip to main content User Agreement Summary of User Agreement Privacy Policy Professional Community Policies Cookie Policy Copyright Policy Regional Info EU Notice California Privacy Disclosure U.S. State Privacy Laws User Agreement Summary of User Agreement Privacy Policy Professional Community Policies Cookie Policy Copyright Policy Regional Info EU Notice California Privacy Disclosure U.S. State Privacy Laws Privacy Policy Effective November 3, 2025 Your Privacy Matters LinkedIn’s mission is to connect the world’s professionals to allow them to be more productive and successful. Central to this mission is our commitment to be transparent about the data we collect about you, how it is used and with whom it is shared. This Privacy Policy applies when you use our Services (described below). We offer our users choices about the data we collect, use and share as described in this Privacy Policy, Cookie Policy , Settings and our Help Center. Key Terms Choices Settings are available to Members of LinkedIn and Visitors are provided separate controls. Learn More . Table of Contents Data We Collect How We Use Your Data How We Share Information Your Choices and Obligations Other Important Information Introduction We are a social network and online platform for professionals. People use our Services to find and be found for business opportunities, to connect with others and find information. Our Privacy Policy applies to any Member or Visitor to our Services. Our registered users (“Members”) share their professional identities, engage with their network, exchange knowledge and professional insights, post and view relevant content, learn and develop skills, and find business and career opportunities. Content and data on some of our Services is viewable to non-Members (“Visitors”). We use the term “Designated Countries” to refer to countries in the European Union (EU), European Economic Area (EEA), and Switzerland. Members and Visitors located in the Designated Countries or the UK can review additional information in our European Regional Privacy Notice . Services This Privacy Policy, including our Cookie Policy applies to your use of our Services. This Privacy Policy applies to LinkedIn.com, LinkedIn-branded apps, and other LinkedIn-branded sites, apps, communications and services offered by LinkedIn (“Services”), including off-site Services, such as our ad services and the “Apply with LinkedIn” and “Share with LinkedIn” plugins, but excluding services that state that they are offered under a different privacy policy. For California residents, additional disclosures required by California law may be found in our California Privacy Disclosure . Data Controllers and Contracting Parties If you are in the “Designated Countries”, LinkedIn Ireland Unlimited Company (“LinkedIn Ireland”) will be the controller of your personal data provided to, or collected by or for, or processed in connection with our Services. If you are outside of the Designated Countries, LinkedIn Corporation will be the controller of (or business responsible for) your personal data provided to, or collected by or for, or processed in connection with our Services. As a Visitor or Member of our Services, the collection, use and sharing of your personal data is subject to this Privacy Policy and other documents referenced in this Privacy Policy, as well as updates. Change Changes to the Privacy Policy apply to your use of our Services after the “effective date.” LinkedIn (“we” or “us”) can modify this Privacy Policy, and if we make material changes to it, we will provide notice through our Services, or by other means, to provide you the opportunity to review the changes before they become effective. If you object to any changes, you may close your account. You acknowledge that your continued use of our Services after we publish or send a notice about our changes to this Privacy Policy means that the collection, use and sharing of your personal data is subject to the updated Privacy Policy, as of its effective date. 1. Data We Collect 1.1 Data You Provide To Us You provide data to create an account with us. Registration To create an account you need to provide data including your name, email address and/or mobile number, general location (e.g., city), and a password. If you register for a premium Service, you will need to provide payment (e.g., credit card) and billing information. You create your LinkedIn profile (a complete profile helps you get the most from our Services). Profile You have choices about the information on your profile, such as your education, work experience, skills, photo, city or area , endorsements, and optional verifications of information on your profile (such as verifications of your identity or workplace). You don’t have to provide additional information on your profile; however, profile information helps you to get more from our Services, including helping recruiters and business opportunities find you. It’s your choice whether to include sensitive information on your profile and to make that sensitive information public. Please do not post or add personal data to your profile that you would not want to be publicly available. You may give other data to us, such as by syncing your calendar. Posting and Uploading We collect personal data from you when you provide, post or upload it to our Services, such as when you fill out a form, (e.g., with demographic data or salary), respond to a survey, or submit a resume or fill out a job application on our Services. If you sync your calendars with our Services, we will collect your calendar meeting information to keep growing your network by suggesting connections for you and others, and by providing information about events, e.g. times, places, attendees and contacts. You don’t have to post or upload personal data; though if you don’t, it may limit your ability to grow and engage with your network over our Services. 1.2 Data From Others Others may post or write about you. Content and News You and others may post content that includes information about you (as part of articles, posts, comments, videos) on our Services. We also may collect public information about you, such as professional-related news and accomplishments, and make it available as part of our Services, including, as permitted by your settings, in notifications to others of mentions in the news . Others may sync their calendar with our Services Contact and Calendar Information We receive personal data (including contact information) about you when others import or sync their calendar with our Services, associate their contacts with Member profiles, scan and upload business cards, or send messages using our Services (including invites or connection requests). If you or others opt-in to sync email accounts with our Services, we will also collect “email header” information that we can associate with Member profiles. Customers and partners may provide data to us. Partners We receive personal data (e.g., your job title and work email address) about you when you use the services of our customers and partners, such as employers or prospective employers and applicant tracking systems providing us job application data. Related Companies and Other Services We receive data about you when you use some of the other services provided by us or our Affiliates , including Microsoft. For example, you may choose to send us information about your contacts in Microsoft apps and services, such as Outlook, for improved professional networking activities on our Services or we may receive information from Microsoft about your engagement with their sites and services. 1.3 Service Use We log your visits and use of our Services, including mobile apps. We log usage data when you visit or otherwise use our Services, including our sites, app and platform technology, such as when you view or click on content (e.g., learning video) or ads (on or off our sites and apps), perform a search, install or update one of our mobile apps, share articles or apply for jobs. We use log-ins, cookies, device information and internet protocol (“IP”) addresses to identify you and log your use. 1.4 Cookies and Similar Technologies We collect data through cookies and similar technologies. As further described in our Cookie Policy , we use cookies and similar technologies (e.g., pixels and ad tags) to collect data (e.g., device IDs) to recognize you and your device(s) on, off and across different services and devices where you have engaged with our Services. We also allow some others to use cookies as described in our Cookie Policy. If you are outside the Designated Countries, we also collect (or rely on others, including Microsoft, who collect) information about your device where you have not engaged with our Services (e.g., ad ID, IP address, operating system and browser information) so we can provide our Members with relevant ads and better understand their effectiveness. Learn more . You can opt out from our use of data from cookies and similar technologies that track your behavior on the sites of others for ad targeting and other ad-related purposes. For Visitors, the controls are here . 1.5 Your Device and Location We receive data through cookies and similar technologies When you visit or leave our Services (including some plugins and our cookies or similar technology on the sites of others), we receive the URL of both the site you came from and the one you go to and the time of your visit. We also get information about your network and device (e.g., IP address, proxy server, operating system, web browser and add-ons, device identifier and features, cookie IDs and/or ISP, or your mobile carrier). If you use our Services from a mobile device, that device will send us data about your location based on your phone settings. We will ask you to opt-in before we use GPS or other tools to identify your precise location. 1.6 Communications If you communicate through our Services, we learn about that. We collect information about you when you communicate with others through our Services (e.g., when you send, receive, or engage with messages, events, or connection requests, including our marketing communications). This may include information that indicates who you are communicating with and when. We also use automated systems to support and protect our site. For example, we use such systems to suggest possible responses to messages and to manage or block content that violates our User Agreement or Professional Community Policies . 1.7 Workplace and School Provided Information When your organization (e.g., employer or school) buys a premium Service for you to use, they give us data about you. Others buying our Services for your use, such as your employer or your school, provide us with personal data about you and your eligibility to use the Services that they purchase for use by their workers, students or alumni. For example, we will get contact information for “ LinkedIn Page ” (formerly Company Page) administrators and for authorizing users of our premium Services, such as our recruiting, sales or learning products. 1.8 Sites and Services of Others We get data when you visit sites that include our ads, cookies or plugins or when you log-in to others’ services with your LinkedIn account. We receive information about your visits and interaction with services provided by others when you log-in with LinkedIn or visit others’ services that include some of our plugins (such as “Apply with LinkedIn”) or our ads, cookies or similar technologies. 1.9 Other We are improving our Services, which means we get new data and create new ways to use data. Our Services are dynamic, and we often introduce new features, which may require the collection of new information. If we collect materially different personal data or materially change how we collect, use or share your data, we will notify you and may also modify this Privacy Policy. Key Terms Affiliates Affiliates are companies controlling, controlled by or under common control with us, including, for example, LinkedIn Ireland, LinkedIn Corporation, LinkedIn Singapore and Microsoft Corporation or any of its subsidiaries (e.g., GitHub, Inc.). 2. How We Use Your Data We use your data to provide, support, personalize and develop our Services. How we use your personal data will depend on which Services you use, how you use those Services and the choices you make in your settings . We may use your personal data to improve, develop, and provide products and Services, develop and train artificial intelligence (AI) models, develop, provide, and personalize our Services, and gain insights with the help of AI, automated systems, and inferences, so that our Services can be more relevant and useful to you and others. You can review LinkedIn's Responsible AI principles here and learn more about our approach to generative AI here . Learn more about the inferences we may make, including as to your age and gender and how we use them. 2.1 Services Our Services help you connect with others, find and be found for work and business opportunities, stay informed, get training and be more productive. We use your data to authorize access to our Services and honor your settings. Stay Connected Our Services allow you to stay in touch and up to date with colleagues, partners, clients, and other professional contacts. To do so, you can “connect” with the professionals who you choose, and who also wish to “connect” with you. Subject to your and their settings , when you connect with other Members, you will be able to search each others’ connections in order to exchange professional opportunities. We use data about you (such as your profile, profiles you have viewed or data provided through address book uploads or partner integrations) to help others find your profile, suggest connections for you and others (e.g. Members who share your contacts or job experiences) and enable you to invite others to become a Member and connect with you. You can also opt-in to allow us to use your precise location or proximity to others for certain tasks (e.g. to suggest other nearby Members for you to connect with, calculate the commute to a new job, or notify your connections that you are at a professional event). It is your choice whether to invite someone to our Services, send a connection request, or allow another Member to become your connection. When you invite someone to connect with you, your invitation will include your network and basic profile information (e.g., name, profile photo, job title, region). We will send invitation reminders to the person you invited. You can choose whether or not to share your own list of connections with your connections. Visitors have choices about how we use their data. Stay Informed Our Services allow you to stay informed about news, events and ideas regarding professional topics you care about, and from professionals you respect. Our Services also allow you to improve your professional skills, or learn new ones. We use the data we have about you (e.g., data you provide, data we collect from your engagement with our Services and inferences we make from the data we have about you), to personalize our Services for you, such as by recommending or ranking relevant content and conversations on our Services. We also use the data we have about you to suggest skills you could add to your profile and skills that you might need to pursue your next opportunity. So, if you let us know that you are interested in a new skill (e.g., by watching a learning video), we will use this information to personalize content in your feed, suggest that you follow certain Members on our site, or suggest related learning content to help you towards that new skill. We use your content, activity and other data, including your name and photo, to provide notices to your network and others. For example, subject to your settings , we may notify others that you have updated your profile, posted content, took a social action , used a feature, made new connections or were mentioned in the news . Career Our Services allow you to explore careers, evaluate educational opportunities, and seek out, and be found for, career opportunities. Your profile can be found by those looking to hire (for a job or a specific task ) or be hired by you. We will use your data to recommend jobs and show you and others relevant professional contacts (e.g., who work at a company, in an industry, function or location or have certain skills and connections). You can signal that you are interested in changing jobs and share information with recruiters. We will use your data to recommend jobs to you and you to recruiters. We may use automated systems to provide content and recommendations to help make our Services more relevant to our Members, Visitors and customers. Keeping your profile accurate and up-to-date may help you better connect to others and to opportunities through our Services. Productivity Our Services allow you to collaborate with colleagues, search for potential clients, customers, partners and others to do business with. Our Services allow you to communicate with other Members and schedule and prepare meetings with them. If your settings allow, we scan messages to provide “bots” or similar tools that facilitate tasks such as scheduling meetings, drafting responses, summarizing messages or recommending next steps. Learn more . 2.2 Premium Services Our premium Services help paying users to search for and contact Members through our Services, such as searching for and contacting job candidates, sales leads and co-workers, manage talent and promote content. We sell premium Services that provide our customers and subscribers with customized-search functionality and tools (including messaging and activity alerts) as part of our talent, marketing and sales solutions. Customers can export limited information from your profile, such as name, headline, current company, current title, and general location (e.g., Dublin), such as to manage sales leads or talent, unless you opt-out . We do not provide contact information to customers as part of these premium Services without your consent. Premium Services customers can store information they have about you in our premium Services, such as a resume or contact information or sales history. The data stored about you by these customers is subject to the policies of those customers. Other enterprise Services and features that use your data include TeamLink and LinkedIn Pages (e.g., content analytics and followers). 2.3 Communications We contact you and enable communications between Members. We offer settings to control what messages you receive and how often you receive some types of messages. We will contact you through email, mobile phone, notices posted on our websites or apps, messages to your LinkedIn inbox, and other ways through our Services, including text messages and push notifications. We will send you messages about the availability of our Services, security, or other service-related issues. We also send messages about how to use our Services, network updates, reminders, job suggestions and promotional messages from us and our partners. You may change your communication preferences at any time. Please be aware that you cannot opt out of receiving service messages from us, including security and legal notices. We also enable communications between you and others through our Services, including for example invitations , InMail , groups and messages between connections. 2.4 Advertising We serve you tailored ads both on and off our Services. We offer you choices regarding personalized ads, but you cannot opt-out of seeing non-personalized ads. We target (and measure the performance of) ads to Members, Visitors and others both on and off our Services directly or through a variety of partners, using the following data, whether separately or combined: Data collected by advertising technologies on and off our Services using pixels, ad tags (e.g., when an advertiser installs a LinkedIn tag on their website), cookies, and other device identifiers; Member-provided information (e.g., profile, contact information, title and industry); Data from your use of our Services (e.g., search history, feed, content you read, who you follow or is following you, connections, groups participation, page visits, videos you watch, clicking on an ad, etc.), including as described in Section 1.3; Information from advertising partners , vendors and publishers ; and Information inferred from data described above (e.g., using job titles from a profile to infer industry, seniority, and compensation bracket; using graduation dates to infer age or using first names or pronoun usage to infer gender; using your feed activity to infer your interests; or using device data to recognize you as a Member). Learn more about the inferences we make and how they may be used for advertising. Learn more about the ad technologies we use and our advertising services and partners. You can learn more about our compliance with laws in the Designated Countries or the UK in our European Regional Privacy Notice . We will show you ads called sponsored content which look similar to non-sponsored content, except that they are labeled as advertising (e.g., as “ad” or “sponsored”). If you take a social action (such as like, comment or share) on these ads, your action is associated with your name and viewable by others, including the advertiser. Subject to your settings , if you take a social action on the LinkedIn Services, that action may be mentioned with related ads. For example, when you like a company we may include your name and photo when their sponsored content is shown. Ad Choices You have choices regarding our uses of certain categories of data to show you more relevant ads. Member settings can be found here . For Visitors, the setting is here . Info to Ad Providers We do not share your personal data with any non-Affiliated third-party advertisers or ad networks except for: (i) hashed IDs or device identifiers (to the extent they are personal data in some countries); (ii) with your separate permission (e.g., in a lead generation form) or (iii) data already visible to any users of the Services (e.g., profile). However, if you view or click on an ad on or off our Services, the ad provider will get a signal that someone visited the page that displayed the ad, and they may, through the use of mechanisms such as cookies, determine it is you. Advertising partners can associate personal data collected by the advertiser directly from you with hashed IDs or device identifiers received from us. We seek to contractually require such advertising partners to obtain your explicit, opt-in consent before doing so where legally required, and in such instances, we take steps to ensure that consent has been provided before processing data from them. 2.5 Marketing We promote our Services to you and others. In addition to advertising our Services, we use Members’ data and content for invitations and communications promoting membership and network growth, engagement and our Services, such as by showing your connections that you have used a feature on our Services. 2.6 Developing Services and Research We develop our Services and conduct research Service Development We use data, including public feedback, to conduct research and development for our Services in order to provide you and others with a better, more intuitive and personalized experience, drive membership growth and engagement on our Services, and help connect professionals to each other and to economic opportunity. Other Research We seek to create economic opportunity for Members of the global workforce and to help them be more productive and successful. We use the personal data available to us to research social, economic and workplace trends, such as jobs availability and skills needed for these jobs and policies that help bridge the gap in various industries and geographic areas. In some cases, we work with trusted third parties to perform this research, under controls that are designed to protect your privacy. We may also make public data available to researchers to enable assessment of the safety and legal compliance of our Services. We publish or allow others to publish economic insights, presented as aggregated data rather than personal data. Surveys Polls and surveys are conducted by us and others through our Services. You are not obligated to respond to polls or surveys, and you have choices about the information you provide. You may opt-out of survey invitations. 2.7 Customer Support We use data to help you and fix problems. We use data (which can include your communications) to investigate, respond to and resolve complaints and for Service issues (e.g., bugs). 2.8 Insights That Do Not Identify You We use data to generate insights that do not identify you. We use your data to perform analytics to produce and share insights that do not identify you. For example, we may use your data to generate statistics about our Members, their profession or industry, to calculate ad impressions served or clicked on (e.g., for basic business reporting to support billing and budget management or, subject to your settings , for reports to advertisers who may use them to inform their advertising campaigns), to show Members' information about engagement with a post or LinkedIn Page , to publish visitor demographics for a Service or create demographic workforce insights, or to understand usage of our services. 2.9 Security and Investigations We use data for security, fraud prevention and investigations. We and our Affiliates, including Microsoft, may use your data (including your communications) for security purposes or to prevent or investigate possible fraud or other violations of the law, our User Agreement and/or attempts to harm our Members, Visitors, company, Affiliates, or others. Key Terms Social Action E.g. like, comment, follow, share Partners Partners include ad networks, exchanges and others 3. How We Share Information 3.1 Our Services Any data that you include on your profile and any content you post or social action (e.g., likes, follows, comments, shares) you take on our Services will be seen by others, consistent with your settings. Profile Your profile is fully visible to all Members and customers of our Services. Subject to your settings , it can also be visible to others on or off of our Services (e.g., Visitors to our Services or users of third-party search tools). As detailed in our Help Center , your settings, degree of connection with the viewing Member, the subscriptions they may have, their usage of our Services , access channels and search types (e.g., by name or by keyword) impact the availability of your profile and whether they can view certain fields in your profile. Posts, Likes, Follows, Comments, Messages Our Services allow viewing and sharing information including through posts, likes, follows and comments. When you share an article or a post (e.g., an update, image, video or article) publicly it can be viewed by everyone and re-shared anywhere (subject to your settings ). Members, Visitors and others will be able to find and see your publicly-shared content, including your name (and photo if you have provided one). In a group , posts are visible to others according to group type. For example, posts in private groups are visible to others in the group and posts in public groups are visible publicly. Your membership in groups is public and part of your profile, but you can change visibility in your settings . Any information you share through companies’ or other organizations’ pages on our Services will be viewable by those organizations and others who view those pages' content. When you follow a person or organization, you are visible to others and that “page owner” as a follower. We let senders know when you act on their message, subject to your settings where applicable. Subject to your settings , we let a Member know when you view their profile. We also give you choices about letting organizations know when you've viewed their Page. When you like or re-share or comment on another’s content (including ads), others will be able to view these “social actions” and associate it with you (e.g., your name, profile and photo if you provided it). Your employer can see how you use Services they provided for your work (e.g. as a recruiter or sales agent) and related information. We will not show them your job searches or personal messages. Enterprise Accounts Your employer may offer you access to our enterprise Services such as Recruiter, Sales Navigator, LinkedIn Learning or our advertising Campaign Manager. Your employer can review and manage your use of such enterprise Services. Depending on the enterprise Service, before you use such Service, we will ask for permission to share with your employer relevant data from your profile or use of our non-enterprise Services. For example, users of Sales Navigator will be asked to share their “social selling index”, a score calculated in part based on their personal account activity. We understand that certain activities such as job hunting and personal messages are sensitive, and so we do not share those with your employer unless you choose to share it with them through our Services (for example, by applying for a new position in the same company or mentioning your job hunting in a message to a co-worker through our Services). Subject to your settings , when you use workplace tools and services (e.g., interactive employee directory tools) certain of your data may also be made available to your employer or be connected with information we receive from your employer to enable these tools and services. 3.2 Communication Archival Regulated Members may need to store communications outside of our Service. Some Members (or their employers) need, for legal or professional compliance, to archive their communications and social media activity, and will use services of others to provide these archival services. We enable archiving of messages by and to those Members outside of our Services. For example, a financial advisor needs to archive communications with her clients through our Services in order to maintain her professional financial advisor license. 3.3 Others’ Services You may link your account with others’ services so that they can look up your contacts’ profiles, post your shares on such platforms, or enable you to start conversations with your connections on such platforms. Excerpts from your profile will also appear on the services of others. Subject to your settings , other services may look up your profile. When you opt to link your account with other services, personal data (e.g., your name, title, and company) will become available to them. The sharing and use of that personal data will be described in, or linked to, a consent screen when you opt to link the accounts. For example, you may link your Twitter or WeChat account to share content from our Services into these other services, or your email provider may give you the option to upload your LinkedIn contacts into its own service. Third-party services have their own privacy policies, and you may be giving them permission to use your data in ways we would not. You may revoke the link with such accounts. The information you make available to others in our Services (e.g., information from your profile, your posts, your engagement with the posts, or message to Pages) may be available to them on other services . For example, search tools, mail and calendar applications, or talent and lead managers may show a user limited profile data (subject to your settings ), and social media management tools or other platforms may display your posts. The information retained on these services may not reflect updates you make on LinkedIn. 3.4 Related Services We share your data across our different Services and LinkedIn affiliated entities. We will share your personal data with our Affiliates to provide and develop our Services. For example, we may refer a query to Bing in some instances, such as where you'd benefit from a more up to date response in a chat experience. Subject to our European Regional Privacy Notice , we may also share with our Affiliates, including Microsoft, your (1) publicly-shared content (such as your public LinkedIn posts) to provide or develop their services and (2) personal data to improve, provide or develop their advertising services. Where allowed , we may combine information internally across the different Services covered by this Privacy Policy to help our Services be more relevant and useful to you and others. For example, we may personalize your feed or job recommendations based on your learning history. 3.5 Service Providers We may use others to help us with our Services. We use others to help us provide our Services (e.g., maintenance, analysis, audit, payments, fraud detection, customer support, marketing and development). They will have access to your information (e.g., the contents of a customer support request) as reasonably necessary to perform these tasks on our behalf and are obligated not to disclose or use it for other purposes. If you purchase a Service from us, we may use a payments service provider who may separately collect information about you (e.g., for fraud prevention or to comply with legal obligations). 3.6 Legal Disclosures We may need to share your data when we believe it’s required by law or to help protect the rights and safety of you, us or others. It is possible that we will need to disclose information about you when required by law, subpoena, or other legal process or if we have a good faith belief that disclosure is reasonably necessary to (1) investigate, prevent or take action regarding suspected or actual illegal activities or to assist government enforcement agencies; (2) enforce our agreements with you; (3) investigate and defend ourselves against any third-party claims or allegations; (4) protect the security or integrity of our Services or the products or services of our Affiliates (such as by sharing with companies facing similar threats); or (5) exercise or protect the rights and safety of LinkedIn, our Members, personnel or others. We attempt to notify Members about legal demands for their personal data when appropriate in our judgment, unless prohibited by law or court order or when the request is an emergency. We may dispute such demands when we believe, in our discretion, that the requests are overbroad, vague or lack proper authority, but we do not promise to challenge every demand. To learn more see our Data Request Guidelines and Transparency Report . 3.7 Change in Control or Sale We may share your data when our business is sold to others, but it must continue to be used in accordance with this Privacy Policy. We can also share your personal data as part of a sale, merger or change in control, or in preparation for any of these events. Any other entity which buys us or part of our business will have the right to continue to use your data, but only in the manner set out in this Privacy Policy unless you agree otherwise. 4. Your Choices & Obligations 4.1 Data Retention We keep most of your personal data for as long as your account is open. We generally retain your personal data as long as you keep your account open or as needed to provide you Services. This includes data you or others provided to us and data generated or inferred from your use of our Services. Even if you only use our Services when looking for a new job every few years, we will retain your information and keep your profile open, unless you close your account. In some cases we choose to retain certain information (e.g., insights about Services use) in a depersonalized or aggregated form. 4.2 Rights to Access and Control Your Personal Data You can access or delete your personal data. You have many choices about how your data is collected, used and shared. We provide many choices about the collection, use and sharing of your data, from deleting or correcting data you include in your profile and controlling the visibility of your posts to advertising opt-outs and communication controls. We offer you settings to control and manage the personal data we have about you. For personal data that we have about you, you can: Delete Data : You can ask us to erase or delete all or some of your personal data (e.g., if it is no longer necessary to provide Services to you). Change or Correct Data : You can edit some of your personal data through your account. You can also ask us to change, update or fix your data in certain cases, particularly if it’s inaccurate. Object to, or Limit or Restrict, Use of Data : You can ask us to stop using all or some of your personal data (e.g., if we have no legal right to keep using it) or to limit our use of it (e.g., if your personal data is inaccurate or unlawfully held). Right to Access and/or Take Your Data : You can ask us for a copy of your personal data and can ask for a copy of personal data you provided in machine readable form. Visitors can learn more about how to make these requests here . You may also contact us using the contact information below, and we will consider your request in accordance with applicable laws. Residents in the Designated Countries and the UK , and other regions , may have additional rights under their laws. 4.3 Account Closure We keep some of your data even after you close your account. If you choose to close your LinkedIn account, your personal data will generally stop being visible to others on our Services within 24 hours. We generally delete closed account information within 30 days of account closure, except as noted below. We retain your personal data even after you have closed your account if reasonably necessary to comply with our legal obligations (including law enforcement requests), meet regulatory requirements, resolve disputes, maintain security, prevent fraud and abuse (e.g., if we have restricted your account for breach of our Professional Community Policies ), enforce our User Agreement, or fulfill your request to "unsubscribe" from further messages from us. We will retain de-personalized information after your account has been closed. Information you have shared with others (e.g., through InMail, updates or group posts) will remain visible after you close your account or delete the information from your own profile or mailbox, and we do not control data that other Members have copied out of our Services. Groups content and ratings or review content associated with closed accounts will show an unknown user as the source. Your profile may continue to be displayed in the services of others (e.g., search tools) until they refresh their cache. 5. Other Important Information 5.1. Security We monitor for and try to prevent security breaches. Please use the security features available through our Services. We implement security safeguards designed to protect your data, such as HTTPS. We regularly monitor our systems for possible vulnerabilities and attacks. However, we cannot warrant the security of any information that you send us. There is no guarantee that data may not be accessed, disclosed, altered, or destroyed by breach of any of our physical, technical, or managerial safeguards. 5.2. Cross-Border Data Transfers We store and use your data outside your country. We process data both inside and outside of the United States and rely on legally-provided mechanisms to lawfully transfer data across borders. Learn more . Countries where we process data may have laws which are different from, and potentially not as protective as, the laws of your own country. 5.3 Lawful Bases for Processing We have lawful bases to collect, use and share data about you. You have choices about our use of your data. At any time, you can withdraw consent you have provided by going to settings. We will only collect and process personal data about you where we have lawful bases. Lawful bases include consent (where you have given consent), contract (where processing is necessary for the performance of a contract with you (e.g., to deliver the LinkedIn Services you have requested) and “legitimate interests.” Learn more . Where we rely on your consent to process personal data, you have the right to withdraw or decline your consent at any time and where we rely on legitimate interests, you have the right to object. Learn More . If you have any questions about the lawful bases upon which we collect and use your personal data, please contact our Data Protection Officer here . If you're located in one of the Designated Countries or the UK, you can learn more about our lawful bases for processing in our European Regional Privacy Notice . 5.4. Direct Marketing and Do Not Track Signals Our statements regarding direct marketing and “do not track” signals. We currently do not share personal data with third parties for their direct marketing purposes without your permission. Learn more about this and about our response to “do not track” signals. 5.5. Contact Information You can contact us or use other options to resolve any complaints. If you have questions or complaints regarding this Policy, please first contact LinkedIn online. You can also reach us by physical mail . If contacting us does not resolve your complaint, you have more options . Residents in the Designated Countries and other regions may also have the right to contact our Data Protection Officer here . If this does not resolve your complaint, Residents in the Designated Countries and other regions may have more options under their laws. Key Terms Consent Where we process data based on consent, we will ask for your explicit consent. You may withdraw your consent at any time, but that will not affect the lawfulness of the processing of your personal data prior to such withdrawal. Where we rely on contract, we will ask that you agree to the processing of personal data that is necessary for entering into or performance of your contract with us. We will rely on legitimate interests as a basis for data processing where the processing of your data is not overridden by your interests or fundamental rights and freedoms. LinkedIn © 2026 About Accessibility User Agreement Privacy Policy Cookie Policy Copyright Policy Brand Policy Guest Controls Community Guidelines العربية (Arabic) বাংলা (Bangla) Čeština (Czech) Dansk (Danish) Deutsch (German) Ελληνικά (Greek) English (English) Español (Spanish) فارسی (Persian) Suomi (Finnish) Français (French) हिंदी (Hindi) Magyar (Hungarian) Bahasa Indonesia (Indonesian) Italiano (Italian) עברית (Hebrew) 日本語 (Japanese) 한국어 (Korean) मराठी (Marathi) Bahasa Malaysia (Malay) Nederlands (Dutch) Norsk (Norwegian) ਪੰਜਾਬੀ (Punjabi) Polski (Polish) Português (Portuguese) Română (Romanian) Русский (Russian) Svenska (Swedish) తెలుగు (Telugu) ภาษาไทย (Thai) Tagalog (Tagalog) Türkçe (Turkish) Українська (Ukrainian) Tiếng Việt (Vietnamese) 简体中文 (Chinese (Simplified)) 正體中文 (Chinese (Traditional)) Language | 2026-01-13T08:48:28 |
https://dev.to/ngxp/s3e2-shaundai-person-on-becoming-unstoppable-devlife#main-content | S3E2 - Shaundai Person on Becoming Unstoppable - Dev.Life - DEV Community Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account DEV Community Close Angular Experience Follow S3E2 - Shaundai Person on Becoming Unstoppable - Dev.Life Sep 19 '22 play In this episode of the Dev.Life, we have an open conversation with Shaundai Person about her non-traditional path from having a successful career in sales to becoming a Senior Software Engineer at Netflix, a sought out conference speaker, a meetup organizer, and a dynamic course creator as well. Shaundai talks about not only the barriers and challenges she faced as she changed careers, but also the ups and downs she’s encountered and deals with now that she’s in the field. To wrap things up, Shaundai shares thoughts and ideas on how diversity of backgrounds can add to the power behind your team and also how developers at any stage in their career can work through feelings of wanting to give up to finding happiness and success instead. LINKS: https://twitter.com/shaundai https://www.reactrobins.com/ https://egghead.io/q/resources-by-shaundai-person https://www.tsforjs.com/ CONNECT WITH US: Shaundai Person @Shaundai Brooke Avery @JediBravery Erik Slack @erik_slack Episode source Personal Trusted User Create template Templates let you quickly answer FAQs or store snippets for re-use. Submit Preview Dismiss Your browser does not support the audio element. 1x initializing... × 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV DEV Community — A space to discuss and keep up software development and manage your software career Home DEV++ Podcasts Videos DEV Education Tracks DEV Challenges DEV Help Advertise on DEV DEV Showcase About Contact Free Postgres Database Software comparisons Forem Shop Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . DEV Community © 2016 - 2026. We're a place where coders share, stay up-to-date and grow their careers. Log in Create account | 2026-01-13T08:48:28 |
https://developer.x.com/developer-terms/policy#5-a | Developer Policy – X Developers | X Developer Platform <g> <g> <defs> <rect id="SVGID_1_" x="-468" y="-1360" width="1440" height="3027" /> </defs> <clippath id="SVGID_2_"> <use xlink:href="#SVGID_1_" style="overflow:visible;" /> </clippath> </g> </g> <rect x="-468" y="-1360" class="st0" width="1440" height="3027" style="fill:rgb(0,0,0,0);stroke-width:3;stroke:rgb(0,0,0)" /> <path d="M13.4,12l5.8-5.8c0.4-0.4,0.4-1,0-1.4c-0.4-0.4-1-0.4-1.4,0L12,10.6L6.2,4.8c-0.4-0.4-1-0.4-1.4,0c-0.4,0.4-0.4,1,0,1.4 l5.8,5.8l-5.8,5.8c-0.4,0.4-0.4,1,0,1.4c0.2,0.2,0.4,0.3,0.7,0.3s0.5-0.1,0.7-0.3l5.8-5.8l5.8,5.8c0.2,0.2,0.5,0.3,0.7,0.3 s0.5-0.1,0.7-0.3c0.4-0.4,0.4-1,0-1.4L13.4,12z" /> </svg>" data-icon-chevron-right="<svg xmlns="http://www.w3.org/2000/svg" width="24" height="24" viewbox="0 0 24 24" aria-hidden="true" focusable="false" role="none" class="twtr-icon"> <path opacity="0" d="M0 0h24v24H0z" /> <path d="M17.207 11.293l-7.5-7.5c-.39-.39-1.023-.39-1.414 0s-.39 1.023 0 1.414L15.086 12l-6.793 6.793c-.39.39-.39 1.023 0 1.414.195.195.45.293.707.293s.512-.098.707-.293l7.5-7.5c.39-.39.39-1.023 0-1.414z" /> </svg>" data-icon-chevron-down="<svg xmlns="http://www.w3.org/2000/svg" width="24" height="24" viewbox="0 0 24 24" aria-hidden="true" focusable="false" role="none" class="twtr-icon"> <path opacity="0" d="M0 0h24v24H0z" /> <path d="M20.207 7.043c-.39-.39-1.023-.39-1.414 0L12 13.836 5.207 7.043c-.39-.39-1.023-.39-1.414 0s-.39 1.023 0 1.414l7.5 7.5c.195.195.45.293.707.293s.512-.098.707-.293l7.5-7.5c.39-.39.39-1.023 0-1.414z" /> </svg>" data-icon-arrow-left="<svg width="28px" height="28px" viewbox="0 0 28 28" version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" aria-hidden="true" focusable="false" role="none" class="twtr-icon u01-meganav__icon-arrow-left"> <g stroke="none" stroke-width="1" fill="none" fill-rule="evenodd" stroke-linecap="round"> <g transform="translate(-1216.000000, -298.000000)" stroke-width="2.25"> <g transform="translate(1200.000000, 282.000000)"> <g transform="translate(17.000000, 17.000000)"> <path d="M0.756410256,12.8589744 L25.7179487,12.8589744"></path> <path d="M13.2371795,25.3397436 L25.7179487,12.8589744"></path> <path d="M13.2371795,12.4807692 L25.3397436,0.378205128" transform="translate(19.288462, 6.429487) rotate(-90.000000) translate(-19.288462, -6.429487) "></path> </g> </g> </g> </g> </svg>" data-left-nav-items="[{"isActive":false,"hasActiveChild":false,"children":[{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"X API","linkDisabled":false,"title":"X API","path":"https://developer.x.com/en/products/twitter-api"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"X Ads API","linkDisabled":false,"title":"X Ads API","path":"https://developer.x.com/en/products/x-ads-api"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"X for websites","linkDisabled":false,"title":"X for websites","path":"https://developer.x.com/en/products/x-for-websites"}],"overviewTitle":"Products","linkDisabled":true,"title":"Products","path":"https://developer.x.com/en/products"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Docs","linkDisabled":false,"title":"Docs","path":"https://docs.x.com/"},{"isActive":false,"hasActiveChild":false,"children":[{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Build for business","linkDisabled":false,"title":"Build for business","path":"https://developer.x.com/en/use-cases/build-for-businesses"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Build for the public","linkDisabled":false,"title":"Build for the public","path":"https://developer.x.com/en/use-cases/build-for-consumers"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Do research","linkDisabled":false,"title":"Do research","path":"https://developer.x.com/en/use-cases/do-research"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Teach \u0026 learn","linkDisabled":false,"title":"Teach \u0026 learn","path":"https://developer.x.com/en/use-cases/teach-and-learn"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Build for good","linkDisabled":false,"title":"Build for good","path":"https://developer.x.com/en/use-cases/build-for-good"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Build for fun","linkDisabled":false,"title":"Build for fun","path":"https://developer.x.com/en/use-cases/build-for-fun"}],"overviewTitle":"Use Cases","linkDisabled":true,"title":"Use Cases","path":"https://developer.x.com/en/navigation/left-nav-items/use-cases"},{"isActive":false,"hasActiveChild":false,"children":[{"isActive":false,"hasActiveChild":false,"children":[{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Changelog","linkDisabled":false,"title":"Changelog","path":"https://docs.x.com/updates/changelog"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Blog","linkDisabled":false,"title":"Blog","path":"https://developer.x.com/en/blog"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Newsletter","linkDisabled":false,"title":"Newsletter","path":"https://developer.x.com/en/updates/stay-informed"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"YouTube","linkDisabled":false,"title":"YouTube","path":"https://www.youtube.com/c/twitterdev"}],"linkDisabled":true,"title":"Stay informed","path":"https://developer.x.com/"},{"isActive":false,"hasActiveChild":false,"children":[{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Forums","linkDisabled":false,"title":"Forums","path":"https://twittercommunity.com/"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Events","linkDisabled":false,"title":"Events","path":"https://twitterdev.bevylabs.com/"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Insiders","linkDisabled":false,"title":"Insiders","path":"https://developer.twitter.com/en/community/insiders"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Community leaders","linkDisabled":false,"title":"Community leaders","path":"https://developer.x.com/en/community/leaders"}],"linkDisabled":true,"title":"Connect","path":"https://developer.x.com/"}],"overviewTitle":"Community","linkDisabled":false,"menuType":"multiCategory","title":"Community","path":"https://developer.x.com/en/community"}]" data-right-nav-items="[{"isActive":false,"hasActiveChild":false,"children":[{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Policies","linkDisabled":false,"title":"Policies","path":"https://developer.x.com/en/developer-terms"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Developer agreement","linkDisabled":false,"title":"Developer agreement","path":"https://developer.x.com/en/developer-terms/agreement-and-policy/source"}],"overviewTitle":"Support","linkDisabled":false,"title":"Support","path":"https://developer.x.com/en/support"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Developer Portal","linkDisabled":false,"title":"Developer Portal","path":"https://developer.twitter.com/en/portal/petition/essential/basic-info"}]" data-cta-enabled="true" data-profile-enabled="true" data-cta-link-new-tab="false" data-root-page-title="Developer Platform"> Developer terms Developer Policy Let's get started X + Developers Using this policy X + Developers Using this policy X + Developers X loves developers. We’re delighted and amazed by the tools and services this community creates by harnessing the power of X data. As part of our commitment to this community, we aim to provide data access that is open and fair for developers, safe for people on X, and beneficial for the X platform as a whole. To further these goals we’ve crafted the Developer Policy as a guide to help people understand our rules and expectations about appropriate API and X Content usage. This Developer Policy (“ Policy ”) provides rules and guidelines for developers who interact with X’s ecosystem of applications, services, website, web pages and content. It is part of your contract with X governing access to and use of the X API and X Content (either as part of the Developer Agreement or other written agreement with X). Policy violations are considered violations of your agreement. This Policy may be changed from time to time without notice. Capitalized terms used in this Policy, which are not defined in this Policy, will have the respective meanings ascribed to them in the Developer Agreement or the Master License Agreement. Using this policy We’ve structured this policy to make it as easy to follow as possible. Please keep information from the following policy sections top of mind as you use the X API and X Content: 1. Set Yourself Up for Success - You are responsible for complying with all X policies. It’s important that you review and understand this Policy, as well as the policies we link to in this document, before you access the X API and X Content. The time spent reviewing our policies may save you hours of rework down the road. 2. Privacy and Control are Essential - Protecting and defending the privacy of people on X is built into the core DNA of our company. As such, we prohibit the use of X data in any way that would be inconsistent with people’s reasonable expectations of privacy. By building on the X API or accessing X Content, you have a special role to play in safeguarding this commitment, most importantly by respecting people’s privacy and providing them with transparency and control over how their data is used. 3. Follow the Platform Usage Guidelines - Getting approved to access the X API and X Content is just the first step. Our Platform Usage Guidelines should be your first stop anytime you have questions about how to ensure policy compliance for your planned use of the X platform. We’ve provided a lot more detail on what each of these three key sections mean below. Please review them carefully to ensure that your usage of the X API and X Content is consistent with our policies. If we believe you are in violation of this Policy (or any other X policy), we may suspend or permanently revoke your access to the X API and X Content. Finally, please note that X may monitor your use of the X API to improve the X Applications, to examine any commercial use, and to ensure your compliance with your approved use case and this Policy. Thanks for reading, and thank you for building with us! We look forward to seeing what you create! Chapter 1 Set yourself up for success Set yourself up for success Set yourself up for success Set yourself up for success You can avoid many potential pitfalls while using the X API by ensuring that your service has been built the right way from day 1. This section of the Developer Policy contains rules that all developers must follow before using the X API or X Content. The Free, Basic, and Pro plans (as described at developer.x.com/en ) are designed for hobbyists, commercial prototyping, early-stage X product integrations, and supporting applications with limited end-users. If you use the X API and X Content beyond this scope, then you must apply (or already subscribe to) an Enterprise plan (as described at developer.x.com/en ). We review all proposed uses of the X developer platform to verify policy compliance — so you’re required to disclose (and update, as applicable) your planned use of the X API and X Content in order to be granted and to maintain access. All new developers must apply for a developer account to access the X API. Current developers without an approved developer account must apply for one as directed to do so by X. As part of this process, you’ll need to provide us with a written description of your intended uses of the X API and X Content. Your use case description is binding on you, and any substantive deviation from it may constitute a violation of our rules and result in enforcement action. You must notify us of any substantive modification to your use case and receive approval before you may begin using X Content for that new purpose. Failure to do so may result in suspension and termination of your API and data access. By building on the X API or accessing X Content, you must comply with ALL X policies. These include this Developer Policy , the Automation Rules , the Display Requirements , the API Restricted Uses Rules , the X Rules , and the X Brand Resources , as well as any other agreements you enter into with X relating to your use of the X API or X Content, including but not limited to the Developer Agreement or a Master Licensing Agreement or Order (as applicable). You must also comply with any modifications to these policies and any new policies launched by X. It is your responsibility to monitor the use of your service and to design your service to prevent violations of X policy by people who use it. Failure to do so may result in suspension or termination of your API and X Content access. You may not register multiple applications for a single use case or substantially similar or overlapping use cases. In this context, a “use case” is a consistent set of analyses, displays, or actions performed via an application. "White label" versions of a tool or service are not permissible. If you plan to “white label” versions of your application, you must notify and receive separate approval from us. As a single exception to these rules, you may create and use a maximum of 3 applications for development, staging, and production instances of the same service. These apps must be registered to a single account, and should be clearly identified (in the name and description) as dev, staging, and prod instances of a single service. You may not use development or staging applications for production purposes. You must keep all API keys or other access credentials private. You may not use, and may not encourage or facilitate others to use, API keys or other access credentials owned by others. Your license agreement with X limits your use of the X API and X Content. Among other things, the X API has rate limits which help to ensure fair data usage and to combat spam on the platform. You may not exceed or circumvent rate limits, or any other limitations or restrictions described in this Policy or your agreement with X, listed on the Developer Site , or communicated to you by X. You may not remove or alter any proprietary notices or marks on X Content received via the X API. This helps to make sure that people know where X Content is coming from, and who it belongs to. For data integrity and platform health reasons, you may not interfere with, intercept, disrupt, or disable any features of the X API or the X service. In other words, use the APIs as intended and documented on developer.x.com . Refer to our HackerOne guidelines for more details about acceptable use. Chapter 2 Privacy and control are essential Privacy and control are essential Consent & permissions Content compliance Off-X matching Your privacy policy Using geo-data X passwords Privacy and control are essential Consent & permissions Content compliance Off-X matching Your privacy policy Using geo-data X passwords Privacy and control are essential X takes privacy seriously, and we expect everyone using X Content and the X API to do the same. Any use of the X developer platform, X API, or X Content in a manner that is inconsistent with peoples’ reasonable expectations of privacy may be subject to enforcement action, which can include suspension and termination of API and X Content access. Your commitment to privacy and control must extend to all uses of X Content and all aspects of the service that you build using our API. To that end, the people using your service must understand and consent to how you use their data, and how you access X on their behalf. This can be accomplished through providing people with a clear, comprehensive, and transparent privacy policy, as well as ensuring that you get express and informed consent from each person using your service before taking any action on their behalf. Please note that a person authenticating into your service does not by itself constitute consent. Consent & permissions In particular, you must get express and informed consent from people before doing any of the following: Taking any actions on their behalf. This includes (but is not limited to): Posting content to X Following/unfollowing accounts Modifying profile or account information Adding hashtags or any other content to Posts Republishing content accessed by means other than via the X API or other X tools Using someone’s X Content to promote a product or service Storing non-public content such as Direct Messages (DMs), or any other private or confidential information Sharing or publishing protected content, or any other private or confidential information If your service allows people to post content to X you must do the following before publishing: Show exactly what will be published Make it clear to people using your service what geo information (if any) will be added to the content If your service allows people to post content to both your service and X, you must do the following before publishing: Obtain permission to post the content Explain where you will post the content You must respect the protected and blocked status of all X Content. You may not serve content obtained using one person’s authentication token to a different person who is not authorized to view that content. Protected accounts: A protected account ’s content is only available to people who have been approved by the owner to follow that account. So, if you run a service that accesses protected accounts, you may only do so to serve such content to the specific people with permission to view that content. Blocked accounts: People on X are able to block access to their accounts for any reason they choose. Commingling information obtained from tokens (or any other API-based action) to bypass this choice is not permitted. As Direct Messages (DMs) are non-public in nature, services that provide DM features must take extra steps to safeguard personal privacy. You may not serve DM content to people who are not authorized to view that content. If your service provides DM functionality you must also: Notify people if you send read receipt events for DMs. You can do this by providing a notice directly in your service, or by displaying read receipts from other participants in a conversation. Get consent before configuring media to be sent in a DM as "shared" (i.e. reusable across multiple DMs). If you do allow media in a DM to be “shared,” you must provide a clear notice that this content will be accessible to anyone with the media’s URL. Content compliance If you store X Content offline, you must keep it up to date with the current state of that content on X. Specifically, you must delete or modify any content you have if it is deleted or modified on X. This must be done as soon as reasonably possible, or within 24 hours after receiving a request to do so by X or the applicable X account owner, or as otherwise required by your agreement with X or applicable law. This must be done unless otherwise prohibited by law, and only then with the express written permission of X. Modified content can take various forms. This includes (but is not limited to): Content that has been made private or gained protected status Content that has been suspended from the platform Content that has had geotags removed from it Content that has been withheld or removed from X Off-X matching We limit the circumstances under which you may match a person on X to information obtained or stored off-X. Off-X matching involves associating X Content, including a X @handle or user ID, with a person, household, device, browser, or other off-X identifier. You may only do this if you have express opt-in consent from the person before making the association, or as described below. In situations in which you don’t have a person’s express, opt-in consent to link their Xidentity to an off-X identifier, we require that any connection you draw be based only on information that someone would reasonably expect to be used for that purpose. In addition, absent a person’s express opt-in consent you may only attempt to match your records about someone to a X identity based on: Information provided directly to you by the person. Note that records about individuals with whom you have no prior relationship, including data about individuals obtained from third parties, do not meet this standard; and/or Public data. “Public data” in this context refers to: Information about a person that you obtained from a public, generally-available resource (such as a directory of members of a professional association) Information on X about a person that is publicly available, including: Posts Profile information, including an account bio and publicly-stated location Display name and @handle Your privacy policy You must display your service’s privacy policy to people before they are permitted to download, install, or sign up to your service. It must disclose at least the following information: The information that you collect from people who use your service How you use and share that information (including with X) How people can contact you with inquiries and requests regarding their information Your privacy policy must be consistent with all applicable laws, and be no less protective of people than X’s Privacy Policy and the privacy policy of our other services and corporate affiliates . You must cease your access to the X API and the use of all X Content if you are unable to comply with your and/or X’s Privacy Policy. Using geo-data Use of geo data comes with additional restrictions due to the sensitive nature of this information. If your service adds location information to Posts, you must disclose to people: When you add location information Whether you add location information as a geotag or annotations data Whether your location information is listed as a place, or as geographic coordinates If your application allows people to post with their location you must comply with X’s geo guidelines in full. Any use of location data or geographic information on a standalone basis is prohibited. You may not (and may not permit others to) store, aggregate, or cache location data and other geographic information contained in X Content, except as part of a Post. For example, you may not separate location data or geographic information out from Posts to show where individuals have been over time. Heat maps and related tools that show aggregated geo activity (e.g., the number of people in a city using a hashtag) are permitted. X passwords You may not store X passwords, or request that people provide their X password, account credentials, or developer application information (including consumer key) to you directly. We suggest the use of Sign-in with X as the authentication tool to link your service and people on X. Chapter 3 Platform usage guidelines Platform usage guidelines Spam, bots, and automation X performance benchmarking Public display of Posts Content redistribution Pay to engage Service authenticy X name, logo, and likeness Advertising on X Platform usage guidelines Spam, bots, and automation X performance benchmarking Public display of Posts Content redistribution Pay to engage Service authenticy X name, logo, and likeness Advertising on X Platform usage guidelines Have you taken care to review X’s policies and set up your API access the right way? Does your service follow X’s privacy and control guidelines? If you can answer yes to these two questions, then you are ready to start using the X API and X Content. X’s Platform Usage Guidelines provide the assistance needed to ensure that your use of X Content is compliant from day 1 throughout the lifecycle of your service. We suggest reviewing these rules on a regular basis to make sure that your integration is operating in a way that is safe and beneficial to people on X and the X platform as a whole. Spam, bots, and automation The use of the X API and developer products to create spam, or engage in any form of platform manipulation, is prohibited. You should review the X Rules on platform manipulation and spam , and ensure that your service does not, and does not enable people to, violate our policies. Services that perform write actions, including posting Posts, following accounts, or sending Direct Messages, must follow the Automation Rules . In particular, you should: Always get explicit consent before sending people automated replies or Direct Messages Immediately respect requests to opt-out of being contacted by you Never perform bulk, aggressive, or spammy actions, including bulk following Never post identical or substantially similar content across multiple accounts If you’re operating an API-based bot account you must clearly indicate what the account is and who is responsible for it. You should never mislead or confuse people about whether your account is or is not a bot. A good way to do this is by including a statement that the account is a bot in the profile bio. X performance benchmarking You may not use the X API to measure the availability, performance, functionality, or usage of X for benchmarking, competitive, or commercial purposes. For example, you should never use the X API to: Calculate aggregate X metrics, such as the total number of Monthly Actives (MAs) or Daily Actives (DAs) Calculate aggregate X Post metrics, such as the total number of Posts posted per day, or the number of account engagements Measure or analyze the responsiveness of X Measure or analyze spam or security on X, except as permitted below We support research that helps improve conversational health on X. You may not publicly disclose any research or findings concerning, or develop, create, or offer services using, the X API or X Content that measure, analyze, or attempt to identify behaviors or content which violate X policies without express written permission from X. DSA Researchers: If you need to contact X relating to access under Art. 40 of the Digital Services Act, please contact EU-Questions@X.com . If you wish to apply for researcher access, please submit an application . Public display of Posts You must maintain the integrity of all X Content that you display publicly or to people who use your service. If you don’t use X for Websites to display content, then you must use the X API to retrieve the most current version available for display. If displayed content ceases to be available through the X API, then you must remove it from your service as soon as reasonably possible, or within 24 hours after the receipt of a removal request from X, or the applicable X account owner, or as otherwise required by applicable law. There are specific rules you must follow if you display X Content offline. Follow the guidelines for using Posts in broadcast if you display Posts offline. If you embed or display Posts, you must contact us about your X API access if your site exceeds 10 million daily impressions. X reserves the right to require additional terms as a condition to your use of the X API. Additional restrictions on X for Websites developer use include: Embedded Posts and/or embedded timelines You must provide people with legally sufficient notice that fully discloses X’s collection and use of data about browsing activities on your website, including for interest-based advertising and personalization. You must also obtain legally sufficient consent from people for such collection and use You must provide legally sufficient instructions on how people can opt out of X’s interest-based advertising and personalization as described here X for Websites widgets You must ensure that people are provided with clear and comprehensive information about, and consent to, the storing and accessing of cookies or other information on their devices as described in X’s cookie use , where providing such information and obtaining such consent is required by law Services targeted to children under 13 Services targeted to children under 13 must opt out of tailoring X in any embedded Post and/or embedded timelines by setting the opt-out parameter to be ‘true’ as described here Content redistribution The best place to get X Content is directly from X. Consequently, we restrict the redistribution of X Content to third parties. If you provide X Content to third parties, including downloadable datasets or via an API, you may only distribute Post IDs, Direct Message IDs, and/or User IDs (except as described below). In total, you may not distribute more than 1,500,000 Post IDs to any entity (inclusive of multiple individuals associated with a single entity) within any 30 day period unless you have received written permission from X. In addition, developers may provide up to 500 public Posts Objects and/or User Objects to each person who uses your service on a daily basis if this is done via non-automated means (e.g., download of spreadsheets or PDFs). Academic researchers are permitted to distribute Post IDs and/or User IDs solely for the purposes of non-commercial research on behalf of an academic institution, and that has been approved by X in writing, or peer review or validation of such research. Only as many Post IDs or User IDs that is necessary for such research, and has been approved by X may be used. Any X Content provided to third parties remains subject to this Policy, and those third parties must agree to the X Terms of Service , Privacy Policy , Developer Agreement , and Developer Policy before receiving such downloads. You may not enable any entity to circumvent any other limitations or restrictions on the distribution of X Content as contained in this Policy , the Developer Agreement , or any other agreement with X. Note: This Section does not apply to researchers with X API access via Art. 40 of the EU Digital Services Act (2022) (“ DSA ”), who are instead subject to the procedures and restrictions set forth in the DSA and the Developer Agreement. Pay to engage Your service shouldn’t compensate people to take actions on X, as that results in inauthentic engagement that degrades the health of the platform. As you use the X API you may not sell or receive monetary or virtual compensation for any X actions. This includes, but is not limited to, Posts, follows, unfollows, reposts, likes, comments, and replies. Service authenticity You must clearly identify your service so that people can understand its source and purpose. Don’t use names, logos, or URLs that mask your service’s identity and features, or that falsely imply an affiliation with X or third parties. Note that creating applications for the purpose of selling names, or to prevent others from using names, is prohibited. You may not use any URL (including shortened URLs) for your service that directs people to: A site that is unrelated to your service A spam or malware site A site that encourages people to violate X policy X name, logo, and likeness You may only use and display the X name and logo to identify X as the source of X Content. You should never use the X name and logo, the X Official Partner Program badge, or any other similar marks or names in a manner that creates a false sense of endorsement, sponsorship, or association with X. The X Brand Resources contain detailed information to help you use the X brand in the right way. You may only use the X Verified Account badge and any other enhanced account categorization as it is reported to you by X through the API. This helps people know that the content your service displays is equivalent to that shown on X. Advertising on X There are restrictions regarding how and where you are allowed to advertise around X Content. To start, your advertisements can’t resemble or reasonably be confused by people as a Post. Other rules on advertising include: There must be a clear separation between X Content and your advertisements. You may not place any advertisements within the X timeline other than X Ads. X reserves the right to serve advertising via the X API. If you decide to serve X Ads once we start delivering them via the API, we will share a portion of advertising revenue with you in accordance with the relevant terms and conditions. You may not use X Content, or information obtained from the X API to target people with advertising outside of the X platform. Chapter 4 Rules for specific X services or features X login X Cards Definitions X login X Cards Definitions The following additional rules apply for any use of the X services or features listed below: X login You must present people with easy to find options to log into and out of X, for example via the OAuth protocol. The Sign in with X option must be displayed at least as prominently as any other sign-up or sign-in feature on your service. You must also provide people without a X account the opportunity to create one via X. Once someone on your service authenticates via Sign in with X you must clearly display their X identity. X identity includes the person’s current X @handle, avatar, and X logo. Any display of someone’s X followers on your service must clearly show that the relationship is associated with X. X Cards To ensure a quality experience you must develop your Card to render across all platforms where Cards are displayed. Additional rules that you must follow when using Cards include: You must mark your Post as ‘true’ for sensitive media if you plan to display such media within a Card You must use HTTPS for hosting all assets within your Card. Your Card should never generate active mixed content browser warnings Audio and video content should include stop or pause controls, and default to ‘sound off’ for videos that automatically play content You may not exceed or circumvent X’s limitations placed on any Cards, including the Card’s intended use. Additional restrictions on Cards use include: You may not place third-party sponsored content within Cards without X’s approval You may not attach monetary incentives (including virtual currency) within your Card or on X from your Card You may not include content or actions within your Card that are misleading or not contextually relevant, such as URLs and media You may only attach an App Card to a Post when someone is explicitly promoting or referring to the app in the Post Definitions X Content ‒ Posts, Post IDs, X end user profile information, and any other data and information made available to you through the X API or by any other means authorized by X, and any copies and derivative works thereof. Developer Site ‒ X’s developer site located at https://developer.x.com . Services ‒ Your websites, applications and other offerings that display X Content or otherwise use the Licensed Material as explicitly approved by X. Post ID ‒ A unique identification number generated for each Post. Post ‒ A posting made on X Applications. “X” ‒ Means (a) X Corp. (865 FM 1209, Building 2, Bastrop, TX 78602, USA) if your principal place of business is outside the European Union, EFTA States, and the United Kingdom; or (b) X Internet Unlimited Company (One Cumberland Place, Fenian Street, Dublin 2, D02 AX07, Ireland) if your principal place of business is in the European Union, EFTA States, or the United Kingdom. Direct Message - A message that is privately sent on X Applications by one end user to one or more specific end user(s) using X’s Direct Message function. X API ‒ The X Application Programming Interface (“API”), Software Development Kit (“SDK”) and/or the related documentation, data, code, and other materials provided by X with the API, as updated from time to time, including without limitation through the Developer Site. X Applications ‒ X’s consumer facing products, services, applications, websites, web pages, platforms, and other offerings, including without limitation, those offered via https://x.com and X's mobile applications. Developer policy and terms Follow @XDevelopers Subscribe to developer news X platform X.com Status Accessibility Embed a post Privacy Center Transparency Center Download the X app Try Grok.com X Corp. About the company Company news Brand toolkit Jobs and internships Investors Help Help Center Using X X for creators Ads Help Center Managing your account Email Preference Center Rules and policies Contact us Developer resources Developer home Documentation Forums Communities Developer blog Engineering blog Developer terms Business resources Advertise X for business Resources and guides X for marketers Marketing insights Brand inspiration X Ads Academy © 2026 X Corp. Cookies Privacy Terms and conditions Did someone say … cookies? X and its partners use cookies to provide you with a better, safer and faster service and to support our business. Some cookies are necessary to use our services, improve our services, and make sure they work properly. Show more about your choices . Accept all cookies Refuse non-essential cookies | 2026-01-13T08:48:28 |
https://dev.to/hoangleitvn/the-builds-that-last-manifesto-218c#main-content | The Builds That Last Manifesto - DEV Community Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account DEV Community Close Add reaction Like Unicorn Exploding Head Raised Hands Fire Jump to Comments Save Boost More... Copy link Copy link Copied to Clipboard Share to X Share to LinkedIn Share to Facebook Share to Mastodon Share Post via... Report Abuse Hoang Le Posted on Jan 11 The Builds That Last Manifesto # productivity # programming # architecture # career Originally published on Builds That Last . I've been building and leading engineering teams for 15 years. Over 50 projects. Startups, enterprises, legacy systems, greenfield builds. Same pattern every time. Teams ship fast. Then they slow down. Not because engineers got lazy. Because the foundation was never there. At my company, we maintain systems 20+ years old. No documentation. No standards. When we ask stakeholders about business logic, they say "read the code". My teams sometimes decompile binary files just to understand what's inside. Debug at runtime because that's the only way to see how things work. Previous teams deployed code to AWS without committing to source control. Gone. This is what engineering looks like for most of us. Not the AI demos. Not the apps shipped in a weekend. The gap between posts and reality You'll see posts about vibe coding, AI-augmented development, shipping apps in hours. I'm not saying AI isn't real. I use these tools every day. The productivity gains are real. But there's a gap between what people post and what I see in actual projects. The posts show demos that work. Reality is production systems that break. The posts celebrate shipping fast. Reality is teams spending months paying back technical debt. The demo works. The demo always works. It's what comes after that separates software that lasts from software that collapses. The iceberg problem What you see is 20% above water. The shiny demos. The fast shipping. Vibe coding, agentic AI, apps built in hours. What you don't see is the 80% below: → Maintenance → Technical debt → Engineers connecting systems never meant to work together → Data inconsistencies accumulated over years → Teams spending days understanding what the previous developer was thinking That 80% is where my teams spend most of our time. And it's where the real lessons are. The speed trap I see this pattern repeat. A team starts fast. AI tools, modern stack, motivated engineers. First version ships in weeks. Everyone celebrates. Then users show up. Edge cases appear. The payment flow breaks. Data sync fails silently. Features that worked in demo crash under real load. Suddenly the team that was "moving fast" spends months fixing things. Not building new features. Just paying back debt from shipping without foundation. Leadership gets frustrated. "Why is the team slow now?" The team isn't slow. They're doing work that should have been done upfront. Speed without foundation creates the illusion of progress. Then reality catches up. Maintenance costs more than building Here's something most people don't think about until it's too late. Maintaining software costs more than building it from scratch. Think about repairing a house. You don't just fix the broken part. You investigate the structure. Remove old materials. Work around things that can't be changed. Then build the new thing. Software is the same. When you inherit a system without documentation, without standards, every change becomes an archaeology project. You spend more time understanding than building. The time you "save" by skipping foundation gets paid back with interest during maintenance. The AI paradox AI makes code generation 10x faster. That's real. AI also increases cognitive load by 30-40%. When AI generates code, someone still needs to verify it's secure. Check for edge cases. Understand the logic before shipping. Maintain it when something breaks. AI doesn't eliminate this work. It changes who's responsible for catching problems. Anthropic's CEO said 90% of their internal code is now AI-generated. The follow-up: "We're not replacing engineers". The 10% humans handle? That's the leverage zone. Architecture decisions. Debugging complex problems. Understanding why something should work, not just what it should do. AI is a turbo, not a robot. Good foundation? AI makes you faster at building good software. Bad foundation? AI makes you faster at building bad software. What this means for engineers The fundamentals matter more than ever. Everyone has access to AI now. The differentiator isn't who prompts better. It's who understands what they're building deeply enough to know when AI helps and when it hurts. Own your code. "The AI wrote it" isn't an excuse when something breaks at 2am. You shipped it. You're responsible. Read the code. Understand the logic. Ship with confidence. The 80% below water is where you build real skills. Legacy systems, maintenance, debugging. Not glamorous. But it's where you learn how software actually behaves. Don't avoid it. Embrace it. What this means for leaders You're only seeing 20% of what your team deals with. The demos work. Sprint reports look fine. But your team might be drowning in the 80% you don't see. The legacy code. Missing documentation. Tribal knowledge that walks out when someone leaves. Buying tools is easy. Training is hard. Teams that succeed with AI invested in foundation first. Standards, process, documentation. Then added AI. Teams that struggle added tools to existing chaos. Now they have faster chaos. Remove friction before adding speed. When you want to go faster, the instinct is to add more. More tools, more people, more pressure. Usually, the answer is to remove things. Remove blockers. Remove unnecessary process. Remove friction slowing your team down. The bottom line Real speed comes from clarity, not from typing faster. In the AI era, shipping is easy. Building to last is what matters. Those legacy systems with no documentation? They taught me more than any greenfield project. Not because they were well-built. Because they showed what happens when foundation is missing. Every time I build something new, I think about the engineer maintaining it in 10 years. Will they understand our decisions? Can they change things confidently? Or will they be stuck doing archaeology? That's what foundation means. Building for the people who come after. What's your experience with the 80% below water? I write about foundation-first engineering at Builds That Last . Top comments (0) Subscribe Personal Trusted User Create template Templates let you quickly answer FAQs or store snippets for re-use. Submit Preview Dismiss Code of Conduct • Report abuse Are you sure you want to hide this comment? It will become hidden in your post, but will still be visible via the comment's permalink . Hide child comments as well Confirm For further actions, you may consider blocking this person and/or reporting abuse Hoang Le Follow Engineering leader. Founder @ INNOMIZE. Building cloud-native systems for startups. Writing about platform engineering and technical leadership at Builds that Last. Location Vietnam Education The Degree of Engineer Information Technology Work Co-Founder, CEO, CTO at INNOMIZE Joined Oct 26, 2019 Trending on DEV Community Hot If a problem can be solved without AI, does AI actually make it better? # ai # architecture # discuss Prompt Engineering Won’t Fix Your Architecture # discuss # career # ai # programming MAWA - El lenguaje simple en sintaxis como Python de bajo nivel. Parte 3, Condicionales. # programming # beginners # showdev # codenewbie 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV DEV Community — A space to discuss and keep up software development and manage your software career Home DEV++ Podcasts Videos DEV Education Tracks DEV Challenges DEV Help Advertise on DEV DEV Showcase About Contact Free Postgres Database Software comparisons Forem Shop Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . DEV Community © 2016 - 2026. We're a place where coders share, stay up-to-date and grow their careers. Log in Create account | 2026-01-13T08:48:28 |
https://stackoverflow.blog/author/isaac-lyman/ | Isaac Lyman - Stack Overflow Blog Loading… Everything Productivity AI/ML Open Source Business Hub Company Releases Podcast Newsletter Stack Overflow Business Stack Internal : the knowledge intelligence layer that powers enterprise AI. Stack Data Licensing : decades of verified, technical knowledge to boost AI performance and trust. Stack Ads : engage developers where it matters — in their daily workflow. Isaac Lyman January 1, 2026 Documents: The architect’s programming language Senior developers know how to deploy code to systems made of code. Architects know how to deploy ideas to systems made of people. Isaac Lyman 2 comment s architecture documentation August 13, 2024 Navigating cities of code with Norris Numbers Settling down in a new city (or codebase) is a marathon, not a sprint. Isaac Lyman 1 comment coding contributed December 25, 2023 Is software getting worse? With all the advancements in software development, apps could be much better. Why aren't they? Isaac Lyman 83 comment s Code for a Living software development contributed December 11, 2023 Three types of AI-assisted programmers What matters isn’t just whether you use it, but how. Isaac Lyman 26 comment s Code for a Living AI career development contributed May 1, 2023 AI isn't the app, it's the UI A realistic understanding of generative AI can guide us to its ideal use case: not a decision-maker or unsupervised agent tucked away from the end user, but an interface between humans and machines. Isaac Lyman 13 comment s AI Code for a Living generative AI contributed October 31, 2022 Flutter vs. React Native: Which is the right cross-platform framework for you? Building traditional native apps often requires maintaining two or more codebases. Let's look at two frameworks that let you keep your code unified. Isaac Lyman 17 comment s Code for a Living flutter react native contributed August 15, 2022 How to interrogate unfamiliar code Readable code is great, but not all code will be immediately readable. That's when you get your interrogation tools. Isaac Lyman 12 comment s Code for a Living reading code contributed June 15, 2022 C#: IEnumerable, yield return, and lazy evaluation Don't hate, iterate. Isaac Lyman 13 comment s .net C# Code for a Living IEnumerable contributed May 23, 2022 The science of interviewing developers All those CEOs on LinkedIn claiming they can find the right candidate in a five-minute conversation? Wrong. Science shows us how we can do better. Isaac Lyman 26 comment s Code for a Living job interviews contributed October 18, 2021 Code quality: a concern for businesses, bottom lines, and empathetic programmers Code quality affects the mental state of a programmer, communication within their team, and the incentives attached to their work. Improve your code and you can improve your organizational health and competence as a whole. Isaac Lyman 25 comment s Code for a Living code quality software engineering tech debt December 7, 2020 Can developer productivity be measured? Defining and measuring programmer productivity is one of the most difficult parts of an engineering manager or CTO’s job description. When everything you do is intangible, how should you measure it? Can it be measured at all? Isaac Lyman 23 comment s Code for a Living management measurement Productivity Our Stack Stack Internal Features Customers Security Pricing Stack Data Licensing Stack Ads Partnerships Services Stack Overflow Company Leadership Press Careers Social Impact Support Contact Stack Overflow help Stack Internal help Terms Privacy policy Cookie policy Your Privacy Choices Elsewhere Blog Dev Newsletter Podcast Releases Dev Survey Site design / logo © 2026 Stack Exchange Inc. Light Dark Auto | 2026-01-13T08:48:28 |
https://www.coursera.org/account/accomplishments/verify/ZG6ZF3SW9RMG?trk=public_profile_certification-title | Coursera | Online Courses & Credentials From Top Educators. Join for Free | Coursera For Individuals For Businesses For Universities For Governments Explore Degrees ​ Log In Join for Free Join for Free Course Certificate Neural Networks and Deep Learning Completed by Daniel Bourke December 12, 2017 24 hours (approximately) Daniel Bourke's account is verified. Coursera certifies their successful completion of Neural Networks and Deep Learning Neural Networks and Deep Learning DeepLearning.AI Filled Star Filled Star Filled Star Filled Star Filled Star 4.9 (123,604 ratings) | 1,497,865 already enrolled Enroll for Free Skills you will gain Applied Machine Learning Supervised Learning Calculus Python Programming Linear Algebra Convolutional Neural Networks Recurrent Neural Networks (RNNs) Deep Learning Artificial Neural Networks Coursera Footer Skills Artificial Intelligence (AI) Cybersecurity Data Analytics Digital Marketing English Speaking Generative AI (GenAI) Microsoft Excel Microsoft Power BI Project Management Python Certificates & Programs Google Cybersecurity Certificate Google Data Analytics Certificate Google IT Support Certificate Google Project Management Certificate Google UX Design Certificate IBM Data Analyst Certificate IBM Data Science Certificate Machine Learning Certificate Microsoft Power BI Data Analyst Certificate UI / UX Design Certificate Industries & Careers Business Computer Science Data Science Education & Teaching Engineering Finance Healthcare Human Resources (HR) Information Technology (IT) Marketing Career Resources Career Aptitude Test Examples of Strengths and Weaknesses for Job Interviews High-Income Skills to Learn How Does Cryptocurrency Work? How to Highlight Duplicates in Google Sheets How to Learn Artificial Intelligence Popular Cybersecurity Certifications Preparing for the PMP Certification Signs You Will Get the Job After an Interview What Is Artificial Intelligence? Coursera About What We Offer Leadership Careers Catalog Coursera Plus Professional Certificates MasterTrack® Certificates Degrees For Enterprise For Government For Campus Become a Partner Social Impact Free Courses Share your Coursera learning story Community Learners Partners Beta Testers Blog The Coursera Podcast Tech Blog More Press Investors Terms Privacy Help Accessibility Contact Articles Directory Affiliates Modern Slavery Statement Cookies Preference Center Learn Anywhere © 2026 Coursera Inc. All rights reserved. | 2026-01-13T08:48:28 |
https://dev.to/hoangleitvn/the-builds-that-last-manifesto-218c#the-ai-paradox | The Builds That Last Manifesto - DEV Community Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account DEV Community Close Add reaction Like Unicorn Exploding Head Raised Hands Fire Jump to Comments Save Boost More... Copy link Copy link Copied to Clipboard Share to X Share to LinkedIn Share to Facebook Share to Mastodon Share Post via... Report Abuse Hoang Le Posted on Jan 11 The Builds That Last Manifesto # productivity # programming # architecture # career Originally published on Builds That Last . I've been building and leading engineering teams for 15 years. Over 50 projects. Startups, enterprises, legacy systems, greenfield builds. Same pattern every time. Teams ship fast. Then they slow down. Not because engineers got lazy. Because the foundation was never there. At my company, we maintain systems 20+ years old. No documentation. No standards. When we ask stakeholders about business logic, they say "read the code". My teams sometimes decompile binary files just to understand what's inside. Debug at runtime because that's the only way to see how things work. Previous teams deployed code to AWS without committing to source control. Gone. This is what engineering looks like for most of us. Not the AI demos. Not the apps shipped in a weekend. The gap between posts and reality You'll see posts about vibe coding, AI-augmented development, shipping apps in hours. I'm not saying AI isn't real. I use these tools every day. The productivity gains are real. But there's a gap between what people post and what I see in actual projects. The posts show demos that work. Reality is production systems that break. The posts celebrate shipping fast. Reality is teams spending months paying back technical debt. The demo works. The demo always works. It's what comes after that separates software that lasts from software that collapses. The iceberg problem What you see is 20% above water. The shiny demos. The fast shipping. Vibe coding, agentic AI, apps built in hours. What you don't see is the 80% below: → Maintenance → Technical debt → Engineers connecting systems never meant to work together → Data inconsistencies accumulated over years → Teams spending days understanding what the previous developer was thinking That 80% is where my teams spend most of our time. And it's where the real lessons are. The speed trap I see this pattern repeat. A team starts fast. AI tools, modern stack, motivated engineers. First version ships in weeks. Everyone celebrates. Then users show up. Edge cases appear. The payment flow breaks. Data sync fails silently. Features that worked in demo crash under real load. Suddenly the team that was "moving fast" spends months fixing things. Not building new features. Just paying back debt from shipping without foundation. Leadership gets frustrated. "Why is the team slow now?" The team isn't slow. They're doing work that should have been done upfront. Speed without foundation creates the illusion of progress. Then reality catches up. Maintenance costs more than building Here's something most people don't think about until it's too late. Maintaining software costs more than building it from scratch. Think about repairing a house. You don't just fix the broken part. You investigate the structure. Remove old materials. Work around things that can't be changed. Then build the new thing. Software is the same. When you inherit a system without documentation, without standards, every change becomes an archaeology project. You spend more time understanding than building. The time you "save" by skipping foundation gets paid back with interest during maintenance. The AI paradox AI makes code generation 10x faster. That's real. AI also increases cognitive load by 30-40%. When AI generates code, someone still needs to verify it's secure. Check for edge cases. Understand the logic before shipping. Maintain it when something breaks. AI doesn't eliminate this work. It changes who's responsible for catching problems. Anthropic's CEO said 90% of their internal code is now AI-generated. The follow-up: "We're not replacing engineers". The 10% humans handle? That's the leverage zone. Architecture decisions. Debugging complex problems. Understanding why something should work, not just what it should do. AI is a turbo, not a robot. Good foundation? AI makes you faster at building good software. Bad foundation? AI makes you faster at building bad software. What this means for engineers The fundamentals matter more than ever. Everyone has access to AI now. The differentiator isn't who prompts better. It's who understands what they're building deeply enough to know when AI helps and when it hurts. Own your code. "The AI wrote it" isn't an excuse when something breaks at 2am. You shipped it. You're responsible. Read the code. Understand the logic. Ship with confidence. The 80% below water is where you build real skills. Legacy systems, maintenance, debugging. Not glamorous. But it's where you learn how software actually behaves. Don't avoid it. Embrace it. What this means for leaders You're only seeing 20% of what your team deals with. The demos work. Sprint reports look fine. But your team might be drowning in the 80% you don't see. The legacy code. Missing documentation. Tribal knowledge that walks out when someone leaves. Buying tools is easy. Training is hard. Teams that succeed with AI invested in foundation first. Standards, process, documentation. Then added AI. Teams that struggle added tools to existing chaos. Now they have faster chaos. Remove friction before adding speed. When you want to go faster, the instinct is to add more. More tools, more people, more pressure. Usually, the answer is to remove things. Remove blockers. Remove unnecessary process. Remove friction slowing your team down. The bottom line Real speed comes from clarity, not from typing faster. In the AI era, shipping is easy. Building to last is what matters. Those legacy systems with no documentation? They taught me more than any greenfield project. Not because they were well-built. Because they showed what happens when foundation is missing. Every time I build something new, I think about the engineer maintaining it in 10 years. Will they understand our decisions? Can they change things confidently? Or will they be stuck doing archaeology? That's what foundation means. Building for the people who come after. What's your experience with the 80% below water? I write about foundation-first engineering at Builds That Last . Top comments (0) Subscribe Personal Trusted User Create template Templates let you quickly answer FAQs or store snippets for re-use. Submit Preview Dismiss Code of Conduct • Report abuse Are you sure you want to hide this comment? It will become hidden in your post, but will still be visible via the comment's permalink . Hide child comments as well Confirm For further actions, you may consider blocking this person and/or reporting abuse Hoang Le Follow Engineering leader. Founder @ INNOMIZE. Building cloud-native systems for startups. Writing about platform engineering and technical leadership at Builds that Last. Location Vietnam Education The Degree of Engineer Information Technology Work Co-Founder, CEO, CTO at INNOMIZE Joined Oct 26, 2019 Trending on DEV Community Hot If a problem can be solved without AI, does AI actually make it better? # ai # architecture # discuss Prompt Engineering Won’t Fix Your Architecture # discuss # career # ai # programming MAWA - El lenguaje simple en sintaxis como Python de bajo nivel. Parte 3, Condicionales. # programming # beginners # showdev # codenewbie 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV DEV Community — A space to discuss and keep up software development and manage your software career Home DEV++ Podcasts Videos DEV Education Tracks DEV Challenges DEV Help Advertise on DEV DEV Showcase About Contact Free Postgres Database Software comparisons Forem Shop Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . DEV Community © 2016 - 2026. We're a place where coders share, stay up-to-date and grow their careers. Log in Create account | 2026-01-13T08:48:28 |
https://dev.to/hoangleitvn/the-builds-that-last-manifesto-218c#the-iceberg-problem | The Builds That Last Manifesto - DEV Community Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account DEV Community Close Add reaction Like Unicorn Exploding Head Raised Hands Fire Jump to Comments Save Boost More... Copy link Copy link Copied to Clipboard Share to X Share to LinkedIn Share to Facebook Share to Mastodon Share Post via... Report Abuse Hoang Le Posted on Jan 11 The Builds That Last Manifesto # productivity # programming # architecture # career Originally published on Builds That Last . I've been building and leading engineering teams for 15 years. Over 50 projects. Startups, enterprises, legacy systems, greenfield builds. Same pattern every time. Teams ship fast. Then they slow down. Not because engineers got lazy. Because the foundation was never there. At my company, we maintain systems 20+ years old. No documentation. No standards. When we ask stakeholders about business logic, they say "read the code". My teams sometimes decompile binary files just to understand what's inside. Debug at runtime because that's the only way to see how things work. Previous teams deployed code to AWS without committing to source control. Gone. This is what engineering looks like for most of us. Not the AI demos. Not the apps shipped in a weekend. The gap between posts and reality You'll see posts about vibe coding, AI-augmented development, shipping apps in hours. I'm not saying AI isn't real. I use these tools every day. The productivity gains are real. But there's a gap between what people post and what I see in actual projects. The posts show demos that work. Reality is production systems that break. The posts celebrate shipping fast. Reality is teams spending months paying back technical debt. The demo works. The demo always works. It's what comes after that separates software that lasts from software that collapses. The iceberg problem What you see is 20% above water. The shiny demos. The fast shipping. Vibe coding, agentic AI, apps built in hours. What you don't see is the 80% below: → Maintenance → Technical debt → Engineers connecting systems never meant to work together → Data inconsistencies accumulated over years → Teams spending days understanding what the previous developer was thinking That 80% is where my teams spend most of our time. And it's where the real lessons are. The speed trap I see this pattern repeat. A team starts fast. AI tools, modern stack, motivated engineers. First version ships in weeks. Everyone celebrates. Then users show up. Edge cases appear. The payment flow breaks. Data sync fails silently. Features that worked in demo crash under real load. Suddenly the team that was "moving fast" spends months fixing things. Not building new features. Just paying back debt from shipping without foundation. Leadership gets frustrated. "Why is the team slow now?" The team isn't slow. They're doing work that should have been done upfront. Speed without foundation creates the illusion of progress. Then reality catches up. Maintenance costs more than building Here's something most people don't think about until it's too late. Maintaining software costs more than building it from scratch. Think about repairing a house. You don't just fix the broken part. You investigate the structure. Remove old materials. Work around things that can't be changed. Then build the new thing. Software is the same. When you inherit a system without documentation, without standards, every change becomes an archaeology project. You spend more time understanding than building. The time you "save" by skipping foundation gets paid back with interest during maintenance. The AI paradox AI makes code generation 10x faster. That's real. AI also increases cognitive load by 30-40%. When AI generates code, someone still needs to verify it's secure. Check for edge cases. Understand the logic before shipping. Maintain it when something breaks. AI doesn't eliminate this work. It changes who's responsible for catching problems. Anthropic's CEO said 90% of their internal code is now AI-generated. The follow-up: "We're not replacing engineers". The 10% humans handle? That's the leverage zone. Architecture decisions. Debugging complex problems. Understanding why something should work, not just what it should do. AI is a turbo, not a robot. Good foundation? AI makes you faster at building good software. Bad foundation? AI makes you faster at building bad software. What this means for engineers The fundamentals matter more than ever. Everyone has access to AI now. The differentiator isn't who prompts better. It's who understands what they're building deeply enough to know when AI helps and when it hurts. Own your code. "The AI wrote it" isn't an excuse when something breaks at 2am. You shipped it. You're responsible. Read the code. Understand the logic. Ship with confidence. The 80% below water is where you build real skills. Legacy systems, maintenance, debugging. Not glamorous. But it's where you learn how software actually behaves. Don't avoid it. Embrace it. What this means for leaders You're only seeing 20% of what your team deals with. The demos work. Sprint reports look fine. But your team might be drowning in the 80% you don't see. The legacy code. Missing documentation. Tribal knowledge that walks out when someone leaves. Buying tools is easy. Training is hard. Teams that succeed with AI invested in foundation first. Standards, process, documentation. Then added AI. Teams that struggle added tools to existing chaos. Now they have faster chaos. Remove friction before adding speed. When you want to go faster, the instinct is to add more. More tools, more people, more pressure. Usually, the answer is to remove things. Remove blockers. Remove unnecessary process. Remove friction slowing your team down. The bottom line Real speed comes from clarity, not from typing faster. In the AI era, shipping is easy. Building to last is what matters. Those legacy systems with no documentation? They taught me more than any greenfield project. Not because they were well-built. Because they showed what happens when foundation is missing. Every time I build something new, I think about the engineer maintaining it in 10 years. Will they understand our decisions? Can they change things confidently? Or will they be stuck doing archaeology? That's what foundation means. Building for the people who come after. What's your experience with the 80% below water? I write about foundation-first engineering at Builds That Last . Top comments (0) Subscribe Personal Trusted User Create template Templates let you quickly answer FAQs or store snippets for re-use. Submit Preview Dismiss Code of Conduct • Report abuse Are you sure you want to hide this comment? It will become hidden in your post, but will still be visible via the comment's permalink . Hide child comments as well Confirm For further actions, you may consider blocking this person and/or reporting abuse Hoang Le Follow Engineering leader. Founder @ INNOMIZE. Building cloud-native systems for startups. Writing about platform engineering and technical leadership at Builds that Last. Location Vietnam Education The Degree of Engineer Information Technology Work Co-Founder, CEO, CTO at INNOMIZE Joined Oct 26, 2019 Trending on DEV Community Hot If a problem can be solved without AI, does AI actually make it better? # ai # architecture # discuss Prompt Engineering Won’t Fix Your Architecture # discuss # career # ai # programming MAWA - El lenguaje simple en sintaxis como Python de bajo nivel. Parte 3, Condicionales. # programming # beginners # showdev # codenewbie 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV DEV Community — A space to discuss and keep up software development and manage your software career Home DEV++ Podcasts Videos DEV Education Tracks DEV Challenges DEV Help Advertise on DEV DEV Showcase About Contact Free Postgres Database Software comparisons Forem Shop Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . DEV Community © 2016 - 2026. We're a place where coders share, stay up-to-date and grow their careers. Log in Create account | 2026-01-13T08:48:28 |
https://developer.x.com/developer-terms/policy#4-h | Developer Policy – X Developers | X Developer Platform <g> <g> <defs> <rect id="SVGID_1_" x="-468" y="-1360" width="1440" height="3027" /> </defs> <clippath id="SVGID_2_"> <use xlink:href="#SVGID_1_" style="overflow:visible;" /> </clippath> </g> </g> <rect x="-468" y="-1360" class="st0" width="1440" height="3027" style="fill:rgb(0,0,0,0);stroke-width:3;stroke:rgb(0,0,0)" /> <path d="M13.4,12l5.8-5.8c0.4-0.4,0.4-1,0-1.4c-0.4-0.4-1-0.4-1.4,0L12,10.6L6.2,4.8c-0.4-0.4-1-0.4-1.4,0c-0.4,0.4-0.4,1,0,1.4 l5.8,5.8l-5.8,5.8c-0.4,0.4-0.4,1,0,1.4c0.2,0.2,0.4,0.3,0.7,0.3s0.5-0.1,0.7-0.3l5.8-5.8l5.8,5.8c0.2,0.2,0.5,0.3,0.7,0.3 s0.5-0.1,0.7-0.3c0.4-0.4,0.4-1,0-1.4L13.4,12z" /> </svg>" data-icon-chevron-right="<svg xmlns="http://www.w3.org/2000/svg" width="24" height="24" viewbox="0 0 24 24" aria-hidden="true" focusable="false" role="none" class="twtr-icon"> <path opacity="0" d="M0 0h24v24H0z" /> <path d="M17.207 11.293l-7.5-7.5c-.39-.39-1.023-.39-1.414 0s-.39 1.023 0 1.414L15.086 12l-6.793 6.793c-.39.39-.39 1.023 0 1.414.195.195.45.293.707.293s.512-.098.707-.293l7.5-7.5c.39-.39.39-1.023 0-1.414z" /> </svg>" data-icon-chevron-down="<svg xmlns="http://www.w3.org/2000/svg" width="24" height="24" viewbox="0 0 24 24" aria-hidden="true" focusable="false" role="none" class="twtr-icon"> <path opacity="0" d="M0 0h24v24H0z" /> <path d="M20.207 7.043c-.39-.39-1.023-.39-1.414 0L12 13.836 5.207 7.043c-.39-.39-1.023-.39-1.414 0s-.39 1.023 0 1.414l7.5 7.5c.195.195.45.293.707.293s.512-.098.707-.293l7.5-7.5c.39-.39.39-1.023 0-1.414z" /> </svg>" data-icon-arrow-left="<svg width="28px" height="28px" viewbox="0 0 28 28" version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" aria-hidden="true" focusable="false" role="none" class="twtr-icon u01-meganav__icon-arrow-left"> <g stroke="none" stroke-width="1" fill="none" fill-rule="evenodd" stroke-linecap="round"> <g transform="translate(-1216.000000, -298.000000)" stroke-width="2.25"> <g transform="translate(1200.000000, 282.000000)"> <g transform="translate(17.000000, 17.000000)"> <path d="M0.756410256,12.8589744 L25.7179487,12.8589744"></path> <path d="M13.2371795,25.3397436 L25.7179487,12.8589744"></path> <path d="M13.2371795,12.4807692 L25.3397436,0.378205128" transform="translate(19.288462, 6.429487) rotate(-90.000000) translate(-19.288462, -6.429487) "></path> </g> </g> </g> </g> </svg>" data-left-nav-items="[{"isActive":false,"hasActiveChild":false,"children":[{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"X API","linkDisabled":false,"title":"X API","path":"https://developer.x.com/en/products/twitter-api"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"X Ads API","linkDisabled":false,"title":"X Ads API","path":"https://developer.x.com/en/products/x-ads-api"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"X for websites","linkDisabled":false,"title":"X for websites","path":"https://developer.x.com/en/products/x-for-websites"}],"overviewTitle":"Products","linkDisabled":true,"title":"Products","path":"https://developer.x.com/en/products"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Docs","linkDisabled":false,"title":"Docs","path":"https://docs.x.com/"},{"isActive":false,"hasActiveChild":false,"children":[{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Build for business","linkDisabled":false,"title":"Build for business","path":"https://developer.x.com/en/use-cases/build-for-businesses"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Build for the public","linkDisabled":false,"title":"Build for the public","path":"https://developer.x.com/en/use-cases/build-for-consumers"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Do research","linkDisabled":false,"title":"Do research","path":"https://developer.x.com/en/use-cases/do-research"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Teach \u0026 learn","linkDisabled":false,"title":"Teach \u0026 learn","path":"https://developer.x.com/en/use-cases/teach-and-learn"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Build for good","linkDisabled":false,"title":"Build for good","path":"https://developer.x.com/en/use-cases/build-for-good"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Build for fun","linkDisabled":false,"title":"Build for fun","path":"https://developer.x.com/en/use-cases/build-for-fun"}],"overviewTitle":"Use Cases","linkDisabled":true,"title":"Use Cases","path":"https://developer.x.com/en/navigation/left-nav-items/use-cases"},{"isActive":false,"hasActiveChild":false,"children":[{"isActive":false,"hasActiveChild":false,"children":[{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Changelog","linkDisabled":false,"title":"Changelog","path":"https://docs.x.com/updates/changelog"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Blog","linkDisabled":false,"title":"Blog","path":"https://developer.x.com/en/blog"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Newsletter","linkDisabled":false,"title":"Newsletter","path":"https://developer.x.com/en/updates/stay-informed"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"YouTube","linkDisabled":false,"title":"YouTube","path":"https://www.youtube.com/c/twitterdev"}],"linkDisabled":true,"title":"Stay informed","path":"https://developer.x.com/"},{"isActive":false,"hasActiveChild":false,"children":[{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Forums","linkDisabled":false,"title":"Forums","path":"https://twittercommunity.com/"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Events","linkDisabled":false,"title":"Events","path":"https://twitterdev.bevylabs.com/"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Insiders","linkDisabled":false,"title":"Insiders","path":"https://developer.twitter.com/en/community/insiders"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Community leaders","linkDisabled":false,"title":"Community leaders","path":"https://developer.x.com/en/community/leaders"}],"linkDisabled":true,"title":"Connect","path":"https://developer.x.com/"}],"overviewTitle":"Community","linkDisabled":false,"menuType":"multiCategory","title":"Community","path":"https://developer.x.com/en/community"}]" data-right-nav-items="[{"isActive":false,"hasActiveChild":false,"children":[{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Policies","linkDisabled":false,"title":"Policies","path":"https://developer.x.com/en/developer-terms"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Developer agreement","linkDisabled":false,"title":"Developer agreement","path":"https://developer.x.com/en/developer-terms/agreement-and-policy/source"}],"overviewTitle":"Support","linkDisabled":false,"title":"Support","path":"https://developer.x.com/en/support"},{"isActive":false,"hasActiveChild":false,"children":[],"overviewTitle":"Developer Portal","linkDisabled":false,"title":"Developer Portal","path":"https://developer.twitter.com/en/portal/petition/essential/basic-info"}]" data-cta-enabled="true" data-profile-enabled="true" data-cta-link-new-tab="false" data-root-page-title="Developer Platform"> Developer terms Developer Policy Let's get started X + Developers Using this policy X + Developers Using this policy X + Developers X loves developers. We’re delighted and amazed by the tools and services this community creates by harnessing the power of X data. As part of our commitment to this community, we aim to provide data access that is open and fair for developers, safe for people on X, and beneficial for the X platform as a whole. To further these goals we’ve crafted the Developer Policy as a guide to help people understand our rules and expectations about appropriate API and X Content usage. This Developer Policy (“ Policy ”) provides rules and guidelines for developers who interact with X’s ecosystem of applications, services, website, web pages and content. It is part of your contract with X governing access to and use of the X API and X Content (either as part of the Developer Agreement or other written agreement with X). Policy violations are considered violations of your agreement. This Policy may be changed from time to time without notice. Capitalized terms used in this Policy, which are not defined in this Policy, will have the respective meanings ascribed to them in the Developer Agreement or the Master License Agreement. Using this policy We’ve structured this policy to make it as easy to follow as possible. Please keep information from the following policy sections top of mind as you use the X API and X Content: 1. Set Yourself Up for Success - You are responsible for complying with all X policies. It’s important that you review and understand this Policy, as well as the policies we link to in this document, before you access the X API and X Content. The time spent reviewing our policies may save you hours of rework down the road. 2. Privacy and Control are Essential - Protecting and defending the privacy of people on X is built into the core DNA of our company. As such, we prohibit the use of X data in any way that would be inconsistent with people’s reasonable expectations of privacy. By building on the X API or accessing X Content, you have a special role to play in safeguarding this commitment, most importantly by respecting people’s privacy and providing them with transparency and control over how their data is used. 3. Follow the Platform Usage Guidelines - Getting approved to access the X API and X Content is just the first step. Our Platform Usage Guidelines should be your first stop anytime you have questions about how to ensure policy compliance for your planned use of the X platform. We’ve provided a lot more detail on what each of these three key sections mean below. Please review them carefully to ensure that your usage of the X API and X Content is consistent with our policies. If we believe you are in violation of this Policy (or any other X policy), we may suspend or permanently revoke your access to the X API and X Content. Finally, please note that X may monitor your use of the X API to improve the X Applications, to examine any commercial use, and to ensure your compliance with your approved use case and this Policy. Thanks for reading, and thank you for building with us! We look forward to seeing what you create! Chapter 1 Set yourself up for success Set yourself up for success Set yourself up for success Set yourself up for success You can avoid many potential pitfalls while using the X API by ensuring that your service has been built the right way from day 1. This section of the Developer Policy contains rules that all developers must follow before using the X API or X Content. The Free, Basic, and Pro plans (as described at developer.x.com/en ) are designed for hobbyists, commercial prototyping, early-stage X product integrations, and supporting applications with limited end-users. If you use the X API and X Content beyond this scope, then you must apply (or already subscribe to) an Enterprise plan (as described at developer.x.com/en ). We review all proposed uses of the X developer platform to verify policy compliance — so you’re required to disclose (and update, as applicable) your planned use of the X API and X Content in order to be granted and to maintain access. All new developers must apply for a developer account to access the X API. Current developers without an approved developer account must apply for one as directed to do so by X. As part of this process, you’ll need to provide us with a written description of your intended uses of the X API and X Content. Your use case description is binding on you, and any substantive deviation from it may constitute a violation of our rules and result in enforcement action. You must notify us of any substantive modification to your use case and receive approval before you may begin using X Content for that new purpose. Failure to do so may result in suspension and termination of your API and data access. By building on the X API or accessing X Content, you must comply with ALL X policies. These include this Developer Policy , the Automation Rules , the Display Requirements , the API Restricted Uses Rules , the X Rules , and the X Brand Resources , as well as any other agreements you enter into with X relating to your use of the X API or X Content, including but not limited to the Developer Agreement or a Master Licensing Agreement or Order (as applicable). You must also comply with any modifications to these policies and any new policies launched by X. It is your responsibility to monitor the use of your service and to design your service to prevent violations of X policy by people who use it. Failure to do so may result in suspension or termination of your API and X Content access. You may not register multiple applications for a single use case or substantially similar or overlapping use cases. In this context, a “use case” is a consistent set of analyses, displays, or actions performed via an application. "White label" versions of a tool or service are not permissible. If you plan to “white label” versions of your application, you must notify and receive separate approval from us. As a single exception to these rules, you may create and use a maximum of 3 applications for development, staging, and production instances of the same service. These apps must be registered to a single account, and should be clearly identified (in the name and description) as dev, staging, and prod instances of a single service. You may not use development or staging applications for production purposes. You must keep all API keys or other access credentials private. You may not use, and may not encourage or facilitate others to use, API keys or other access credentials owned by others. Your license agreement with X limits your use of the X API and X Content. Among other things, the X API has rate limits which help to ensure fair data usage and to combat spam on the platform. You may not exceed or circumvent rate limits, or any other limitations or restrictions described in this Policy or your agreement with X, listed on the Developer Site , or communicated to you by X. You may not remove or alter any proprietary notices or marks on X Content received via the X API. This helps to make sure that people know where X Content is coming from, and who it belongs to. For data integrity and platform health reasons, you may not interfere with, intercept, disrupt, or disable any features of the X API or the X service. In other words, use the APIs as intended and documented on developer.x.com . Refer to our HackerOne guidelines for more details about acceptable use. Chapter 2 Privacy and control are essential Privacy and control are essential Consent & permissions Content compliance Off-X matching Your privacy policy Using geo-data X passwords Privacy and control are essential Consent & permissions Content compliance Off-X matching Your privacy policy Using geo-data X passwords Privacy and control are essential X takes privacy seriously, and we expect everyone using X Content and the X API to do the same. Any use of the X developer platform, X API, or X Content in a manner that is inconsistent with peoples’ reasonable expectations of privacy may be subject to enforcement action, which can include suspension and termination of API and X Content access. Your commitment to privacy and control must extend to all uses of X Content and all aspects of the service that you build using our API. To that end, the people using your service must understand and consent to how you use their data, and how you access X on their behalf. This can be accomplished through providing people with a clear, comprehensive, and transparent privacy policy, as well as ensuring that you get express and informed consent from each person using your service before taking any action on their behalf. Please note that a person authenticating into your service does not by itself constitute consent. Consent & permissions In particular, you must get express and informed consent from people before doing any of the following: Taking any actions on their behalf. This includes (but is not limited to): Posting content to X Following/unfollowing accounts Modifying profile or account information Adding hashtags or any other content to Posts Republishing content accessed by means other than via the X API or other X tools Using someone’s X Content to promote a product or service Storing non-public content such as Direct Messages (DMs), or any other private or confidential information Sharing or publishing protected content, or any other private or confidential information If your service allows people to post content to X you must do the following before publishing: Show exactly what will be published Make it clear to people using your service what geo information (if any) will be added to the content If your service allows people to post content to both your service and X, you must do the following before publishing: Obtain permission to post the content Explain where you will post the content You must respect the protected and blocked status of all X Content. You may not serve content obtained using one person’s authentication token to a different person who is not authorized to view that content. Protected accounts: A protected account ’s content is only available to people who have been approved by the owner to follow that account. So, if you run a service that accesses protected accounts, you may only do so to serve such content to the specific people with permission to view that content. Blocked accounts: People on X are able to block access to their accounts for any reason they choose. Commingling information obtained from tokens (or any other API-based action) to bypass this choice is not permitted. As Direct Messages (DMs) are non-public in nature, services that provide DM features must take extra steps to safeguard personal privacy. You may not serve DM content to people who are not authorized to view that content. If your service provides DM functionality you must also: Notify people if you send read receipt events for DMs. You can do this by providing a notice directly in your service, or by displaying read receipts from other participants in a conversation. Get consent before configuring media to be sent in a DM as "shared" (i.e. reusable across multiple DMs). If you do allow media in a DM to be “shared,” you must provide a clear notice that this content will be accessible to anyone with the media’s URL. Content compliance If you store X Content offline, you must keep it up to date with the current state of that content on X. Specifically, you must delete or modify any content you have if it is deleted or modified on X. This must be done as soon as reasonably possible, or within 24 hours after receiving a request to do so by X or the applicable X account owner, or as otherwise required by your agreement with X or applicable law. This must be done unless otherwise prohibited by law, and only then with the express written permission of X. Modified content can take various forms. This includes (but is not limited to): Content that has been made private or gained protected status Content that has been suspended from the platform Content that has had geotags removed from it Content that has been withheld or removed from X Off-X matching We limit the circumstances under which you may match a person on X to information obtained or stored off-X. Off-X matching involves associating X Content, including a X @handle or user ID, with a person, household, device, browser, or other off-X identifier. You may only do this if you have express opt-in consent from the person before making the association, or as described below. In situations in which you don’t have a person’s express, opt-in consent to link their Xidentity to an off-X identifier, we require that any connection you draw be based only on information that someone would reasonably expect to be used for that purpose. In addition, absent a person’s express opt-in consent you may only attempt to match your records about someone to a X identity based on: Information provided directly to you by the person. Note that records about individuals with whom you have no prior relationship, including data about individuals obtained from third parties, do not meet this standard; and/or Public data. “Public data” in this context refers to: Information about a person that you obtained from a public, generally-available resource (such as a directory of members of a professional association) Information on X about a person that is publicly available, including: Posts Profile information, including an account bio and publicly-stated location Display name and @handle Your privacy policy You must display your service’s privacy policy to people before they are permitted to download, install, or sign up to your service. It must disclose at least the following information: The information that you collect from people who use your service How you use and share that information (including with X) How people can contact you with inquiries and requests regarding their information Your privacy policy must be consistent with all applicable laws, and be no less protective of people than X’s Privacy Policy and the privacy policy of our other services and corporate affiliates . You must cease your access to the X API and the use of all X Content if you are unable to comply with your and/or X’s Privacy Policy. Using geo-data Use of geo data comes with additional restrictions due to the sensitive nature of this information. If your service adds location information to Posts, you must disclose to people: When you add location information Whether you add location information as a geotag or annotations data Whether your location information is listed as a place, or as geographic coordinates If your application allows people to post with their location you must comply with X’s geo guidelines in full. Any use of location data or geographic information on a standalone basis is prohibited. You may not (and may not permit others to) store, aggregate, or cache location data and other geographic information contained in X Content, except as part of a Post. For example, you may not separate location data or geographic information out from Posts to show where individuals have been over time. Heat maps and related tools that show aggregated geo activity (e.g., the number of people in a city using a hashtag) are permitted. X passwords You may not store X passwords, or request that people provide their X password, account credentials, or developer application information (including consumer key) to you directly. We suggest the use of Sign-in with X as the authentication tool to link your service and people on X. Chapter 3 Platform usage guidelines Platform usage guidelines Spam, bots, and automation X performance benchmarking Public display of Posts Content redistribution Pay to engage Service authenticy X name, logo, and likeness Advertising on X Platform usage guidelines Spam, bots, and automation X performance benchmarking Public display of Posts Content redistribution Pay to engage Service authenticy X name, logo, and likeness Advertising on X Platform usage guidelines Have you taken care to review X’s policies and set up your API access the right way? Does your service follow X’s privacy and control guidelines? If you can answer yes to these two questions, then you are ready to start using the X API and X Content. X’s Platform Usage Guidelines provide the assistance needed to ensure that your use of X Content is compliant from day 1 throughout the lifecycle of your service. We suggest reviewing these rules on a regular basis to make sure that your integration is operating in a way that is safe and beneficial to people on X and the X platform as a whole. Spam, bots, and automation The use of the X API and developer products to create spam, or engage in any form of platform manipulation, is prohibited. You should review the X Rules on platform manipulation and spam , and ensure that your service does not, and does not enable people to, violate our policies. Services that perform write actions, including posting Posts, following accounts, or sending Direct Messages, must follow the Automation Rules . In particular, you should: Always get explicit consent before sending people automated replies or Direct Messages Immediately respect requests to opt-out of being contacted by you Never perform bulk, aggressive, or spammy actions, including bulk following Never post identical or substantially similar content across multiple accounts If you’re operating an API-based bot account you must clearly indicate what the account is and who is responsible for it. You should never mislead or confuse people about whether your account is or is not a bot. A good way to do this is by including a statement that the account is a bot in the profile bio. X performance benchmarking You may not use the X API to measure the availability, performance, functionality, or usage of X for benchmarking, competitive, or commercial purposes. For example, you should never use the X API to: Calculate aggregate X metrics, such as the total number of Monthly Actives (MAs) or Daily Actives (DAs) Calculate aggregate X Post metrics, such as the total number of Posts posted per day, or the number of account engagements Measure or analyze the responsiveness of X Measure or analyze spam or security on X, except as permitted below We support research that helps improve conversational health on X. You may not publicly disclose any research or findings concerning, or develop, create, or offer services using, the X API or X Content that measure, analyze, or attempt to identify behaviors or content which violate X policies without express written permission from X. DSA Researchers: If you need to contact X relating to access under Art. 40 of the Digital Services Act, please contact EU-Questions@X.com . If you wish to apply for researcher access, please submit an application . Public display of Posts You must maintain the integrity of all X Content that you display publicly or to people who use your service. If you don’t use X for Websites to display content, then you must use the X API to retrieve the most current version available for display. If displayed content ceases to be available through the X API, then you must remove it from your service as soon as reasonably possible, or within 24 hours after the receipt of a removal request from X, or the applicable X account owner, or as otherwise required by applicable law. There are specific rules you must follow if you display X Content offline. Follow the guidelines for using Posts in broadcast if you display Posts offline. If you embed or display Posts, you must contact us about your X API access if your site exceeds 10 million daily impressions. X reserves the right to require additional terms as a condition to your use of the X API. Additional restrictions on X for Websites developer use include: Embedded Posts and/or embedded timelines You must provide people with legally sufficient notice that fully discloses X’s collection and use of data about browsing activities on your website, including for interest-based advertising and personalization. You must also obtain legally sufficient consent from people for such collection and use You must provide legally sufficient instructions on how people can opt out of X’s interest-based advertising and personalization as described here X for Websites widgets You must ensure that people are provided with clear and comprehensive information about, and consent to, the storing and accessing of cookies or other information on their devices as described in X’s cookie use , where providing such information and obtaining such consent is required by law Services targeted to children under 13 Services targeted to children under 13 must opt out of tailoring X in any embedded Post and/or embedded timelines by setting the opt-out parameter to be ‘true’ as described here Content redistribution The best place to get X Content is directly from X. Consequently, we restrict the redistribution of X Content to third parties. If you provide X Content to third parties, including downloadable datasets or via an API, you may only distribute Post IDs, Direct Message IDs, and/or User IDs (except as described below). In total, you may not distribute more than 1,500,000 Post IDs to any entity (inclusive of multiple individuals associated with a single entity) within any 30 day period unless you have received written permission from X. In addition, developers may provide up to 500 public Posts Objects and/or User Objects to each person who uses your service on a daily basis if this is done via non-automated means (e.g., download of spreadsheets or PDFs). Academic researchers are permitted to distribute Post IDs and/or User IDs solely for the purposes of non-commercial research on behalf of an academic institution, and that has been approved by X in writing, or peer review or validation of such research. Only as many Post IDs or User IDs that is necessary for such research, and has been approved by X may be used. Any X Content provided to third parties remains subject to this Policy, and those third parties must agree to the X Terms of Service , Privacy Policy , Developer Agreement , and Developer Policy before receiving such downloads. You may not enable any entity to circumvent any other limitations or restrictions on the distribution of X Content as contained in this Policy , the Developer Agreement , or any other agreement with X. Note: This Section does not apply to researchers with X API access via Art. 40 of the EU Digital Services Act (2022) (“ DSA ”), who are instead subject to the procedures and restrictions set forth in the DSA and the Developer Agreement. Pay to engage Your service shouldn’t compensate people to take actions on X, as that results in inauthentic engagement that degrades the health of the platform. As you use the X API you may not sell or receive monetary or virtual compensation for any X actions. This includes, but is not limited to, Posts, follows, unfollows, reposts, likes, comments, and replies. Service authenticity You must clearly identify your service so that people can understand its source and purpose. Don’t use names, logos, or URLs that mask your service’s identity and features, or that falsely imply an affiliation with X or third parties. Note that creating applications for the purpose of selling names, or to prevent others from using names, is prohibited. You may not use any URL (including shortened URLs) for your service that directs people to: A site that is unrelated to your service A spam or malware site A site that encourages people to violate X policy X name, logo, and likeness You may only use and display the X name and logo to identify X as the source of X Content. You should never use the X name and logo, the X Official Partner Program badge, or any other similar marks or names in a manner that creates a false sense of endorsement, sponsorship, or association with X. The X Brand Resources contain detailed information to help you use the X brand in the right way. You may only use the X Verified Account badge and any other enhanced account categorization as it is reported to you by X through the API. This helps people know that the content your service displays is equivalent to that shown on X. Advertising on X There are restrictions regarding how and where you are allowed to advertise around X Content. To start, your advertisements can’t resemble or reasonably be confused by people as a Post. Other rules on advertising include: There must be a clear separation between X Content and your advertisements. You may not place any advertisements within the X timeline other than X Ads. X reserves the right to serve advertising via the X API. If you decide to serve X Ads once we start delivering them via the API, we will share a portion of advertising revenue with you in accordance with the relevant terms and conditions. You may not use X Content, or information obtained from the X API to target people with advertising outside of the X platform. Chapter 4 Rules for specific X services or features X login X Cards Definitions X login X Cards Definitions The following additional rules apply for any use of the X services or features listed below: X login You must present people with easy to find options to log into and out of X, for example via the OAuth protocol. The Sign in with X option must be displayed at least as prominently as any other sign-up or sign-in feature on your service. You must also provide people without a X account the opportunity to create one via X. Once someone on your service authenticates via Sign in with X you must clearly display their X identity. X identity includes the person’s current X @handle, avatar, and X logo. Any display of someone’s X followers on your service must clearly show that the relationship is associated with X. X Cards To ensure a quality experience you must develop your Card to render across all platforms where Cards are displayed. Additional rules that you must follow when using Cards include: You must mark your Post as ‘true’ for sensitive media if you plan to display such media within a Card You must use HTTPS for hosting all assets within your Card. Your Card should never generate active mixed content browser warnings Audio and video content should include stop or pause controls, and default to ‘sound off’ for videos that automatically play content You may not exceed or circumvent X’s limitations placed on any Cards, including the Card’s intended use. Additional restrictions on Cards use include: You may not place third-party sponsored content within Cards without X’s approval You may not attach monetary incentives (including virtual currency) within your Card or on X from your Card You may not include content or actions within your Card that are misleading or not contextually relevant, such as URLs and media You may only attach an App Card to a Post when someone is explicitly promoting or referring to the app in the Post Definitions X Content ‒ Posts, Post IDs, X end user profile information, and any other data and information made available to you through the X API or by any other means authorized by X, and any copies and derivative works thereof. Developer Site ‒ X’s developer site located at https://developer.x.com . Services ‒ Your websites, applications and other offerings that display X Content or otherwise use the Licensed Material as explicitly approved by X. Post ID ‒ A unique identification number generated for each Post. Post ‒ A posting made on X Applications. “X” ‒ Means (a) X Corp. (865 FM 1209, Building 2, Bastrop, TX 78602, USA) if your principal place of business is outside the European Union, EFTA States, and the United Kingdom; or (b) X Internet Unlimited Company (One Cumberland Place, Fenian Street, Dublin 2, D02 AX07, Ireland) if your principal place of business is in the European Union, EFTA States, or the United Kingdom. Direct Message - A message that is privately sent on X Applications by one end user to one or more specific end user(s) using X’s Direct Message function. X API ‒ The X Application Programming Interface (“API”), Software Development Kit (“SDK”) and/or the related documentation, data, code, and other materials provided by X with the API, as updated from time to time, including without limitation through the Developer Site. X Applications ‒ X’s consumer facing products, services, applications, websites, web pages, platforms, and other offerings, including without limitation, those offered via https://x.com and X's mobile applications. Developer policy and terms Follow @XDevelopers Subscribe to developer news X platform X.com Status Accessibility Embed a post Privacy Center Transparency Center Download the X app Try Grok.com X Corp. About the company Company news Brand toolkit Jobs and internships Investors Help Help Center Using X X for creators Ads Help Center Managing your account Email Preference Center Rules and policies Contact us Developer resources Developer home Documentation Forums Communities Developer blog Engineering blog Developer terms Business resources Advertise X for business Resources and guides X for marketers Marketing insights Brand inspiration X Ads Academy © 2026 X Corp. Cookies Privacy Terms and conditions Did someone say … cookies? X and its partners use cookies to provide you with a better, safer and faster service and to support our business. Some cookies are necessary to use our services, improve our services, and make sure they work properly. Show more about your choices . Accept all cookies Refuse non-essential cookies | 2026-01-13T08:48:28 |
https://dev.to/hoangleitvn/the-builds-that-last-manifesto-218c#what-this-means-for-engineers | The Builds That Last Manifesto - DEV Community Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account DEV Community Close Add reaction Like Unicorn Exploding Head Raised Hands Fire Jump to Comments Save Boost More... Copy link Copy link Copied to Clipboard Share to X Share to LinkedIn Share to Facebook Share to Mastodon Share Post via... Report Abuse Hoang Le Posted on Jan 11 The Builds That Last Manifesto # productivity # programming # architecture # career Originally published on Builds That Last . I've been building and leading engineering teams for 15 years. Over 50 projects. Startups, enterprises, legacy systems, greenfield builds. Same pattern every time. Teams ship fast. Then they slow down. Not because engineers got lazy. Because the foundation was never there. At my company, we maintain systems 20+ years old. No documentation. No standards. When we ask stakeholders about business logic, they say "read the code". My teams sometimes decompile binary files just to understand what's inside. Debug at runtime because that's the only way to see how things work. Previous teams deployed code to AWS without committing to source control. Gone. This is what engineering looks like for most of us. Not the AI demos. Not the apps shipped in a weekend. The gap between posts and reality You'll see posts about vibe coding, AI-augmented development, shipping apps in hours. I'm not saying AI isn't real. I use these tools every day. The productivity gains are real. But there's a gap between what people post and what I see in actual projects. The posts show demos that work. Reality is production systems that break. The posts celebrate shipping fast. Reality is teams spending months paying back technical debt. The demo works. The demo always works. It's what comes after that separates software that lasts from software that collapses. The iceberg problem What you see is 20% above water. The shiny demos. The fast shipping. Vibe coding, agentic AI, apps built in hours. What you don't see is the 80% below: → Maintenance → Technical debt → Engineers connecting systems never meant to work together → Data inconsistencies accumulated over years → Teams spending days understanding what the previous developer was thinking That 80% is where my teams spend most of our time. And it's where the real lessons are. The speed trap I see this pattern repeat. A team starts fast. AI tools, modern stack, motivated engineers. First version ships in weeks. Everyone celebrates. Then users show up. Edge cases appear. The payment flow breaks. Data sync fails silently. Features that worked in demo crash under real load. Suddenly the team that was "moving fast" spends months fixing things. Not building new features. Just paying back debt from shipping without foundation. Leadership gets frustrated. "Why is the team slow now?" The team isn't slow. They're doing work that should have been done upfront. Speed without foundation creates the illusion of progress. Then reality catches up. Maintenance costs more than building Here's something most people don't think about until it's too late. Maintaining software costs more than building it from scratch. Think about repairing a house. You don't just fix the broken part. You investigate the structure. Remove old materials. Work around things that can't be changed. Then build the new thing. Software is the same. When you inherit a system without documentation, without standards, every change becomes an archaeology project. You spend more time understanding than building. The time you "save" by skipping foundation gets paid back with interest during maintenance. The AI paradox AI makes code generation 10x faster. That's real. AI also increases cognitive load by 30-40%. When AI generates code, someone still needs to verify it's secure. Check for edge cases. Understand the logic before shipping. Maintain it when something breaks. AI doesn't eliminate this work. It changes who's responsible for catching problems. Anthropic's CEO said 90% of their internal code is now AI-generated. The follow-up: "We're not replacing engineers". The 10% humans handle? That's the leverage zone. Architecture decisions. Debugging complex problems. Understanding why something should work, not just what it should do. AI is a turbo, not a robot. Good foundation? AI makes you faster at building good software. Bad foundation? AI makes you faster at building bad software. What this means for engineers The fundamentals matter more than ever. Everyone has access to AI now. The differentiator isn't who prompts better. It's who understands what they're building deeply enough to know when AI helps and when it hurts. Own your code. "The AI wrote it" isn't an excuse when something breaks at 2am. You shipped it. You're responsible. Read the code. Understand the logic. Ship with confidence. The 80% below water is where you build real skills. Legacy systems, maintenance, debugging. Not glamorous. But it's where you learn how software actually behaves. Don't avoid it. Embrace it. What this means for leaders You're only seeing 20% of what your team deals with. The demos work. Sprint reports look fine. But your team might be drowning in the 80% you don't see. The legacy code. Missing documentation. Tribal knowledge that walks out when someone leaves. Buying tools is easy. Training is hard. Teams that succeed with AI invested in foundation first. Standards, process, documentation. Then added AI. Teams that struggle added tools to existing chaos. Now they have faster chaos. Remove friction before adding speed. When you want to go faster, the instinct is to add more. More tools, more people, more pressure. Usually, the answer is to remove things. Remove blockers. Remove unnecessary process. Remove friction slowing your team down. The bottom line Real speed comes from clarity, not from typing faster. In the AI era, shipping is easy. Building to last is what matters. Those legacy systems with no documentation? They taught me more than any greenfield project. Not because they were well-built. Because they showed what happens when foundation is missing. Every time I build something new, I think about the engineer maintaining it in 10 years. Will they understand our decisions? Can they change things confidently? Or will they be stuck doing archaeology? That's what foundation means. Building for the people who come after. What's your experience with the 80% below water? I write about foundation-first engineering at Builds That Last . Top comments (0) Subscribe Personal Trusted User Create template Templates let you quickly answer FAQs or store snippets for re-use. Submit Preview Dismiss Code of Conduct • Report abuse Are you sure you want to hide this comment? It will become hidden in your post, but will still be visible via the comment's permalink . Hide child comments as well Confirm For further actions, you may consider blocking this person and/or reporting abuse Hoang Le Follow Engineering leader. Founder @ INNOMIZE. Building cloud-native systems for startups. Writing about platform engineering and technical leadership at Builds that Last. Location Vietnam Education The Degree of Engineer Information Technology Work Co-Founder, CEO, CTO at INNOMIZE Joined Oct 26, 2019 Trending on DEV Community Hot If a problem can be solved without AI, does AI actually make it better? # ai # architecture # discuss Prompt Engineering Won’t Fix Your Architecture # discuss # career # ai # programming MAWA - El lenguaje simple en sintaxis como Python de bajo nivel. Parte 3, Condicionales. # programming # beginners # showdev # codenewbie 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV DEV Community — A space to discuss and keep up software development and manage your software career Home DEV++ Podcasts Videos DEV Education Tracks DEV Challenges DEV Help Advertise on DEV DEV Showcase About Contact Free Postgres Database Software comparisons Forem Shop Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . DEV Community © 2016 - 2026. We're a place where coders share, stay up-to-date and grow their careers. Log in Create account | 2026-01-13T08:48:28 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.