Loading…
Stack Overflow
The world’s largest online question-and-answer platform for computer programmers and software developers.
- 46 posts summarised
- latest
The Good Stuff
Paid picks we use ourselves. Links carry a referral code — a subscription through one earns us a commission at no extra cost to you.
From their blog
Latest articles
Is Your “Human-in-the-Loop” Actually Slowing You Down? Here’s What We Learned
Human-in-the-loop (HITL) frameworks integrate human judgment into automated AI workflows to improve reliability and safety, but without careful design they can create bottlenecks. The post reveals key trade-offs: more automation increases speed and reduces cost but raises risk, while more human oversight boosts accuracy and safety but adds latency and cost. Common failure modes include over-reviewing trivial cases, lacking clear trigger logic, and expecting human reviewers to scale linearly. The proposed solution is a tiered HITL system applying the Pareto principle: automation handles 85% of high-confidence decisions using confidence calibration, with three tiers addressing the remaining cases under 3 ms latency, asynchronous review within hours, and real-time oversight with 30-60 second windows. Success requires careful routing, reviewer tooling, and closing feedback loops across seconds, days, weeks, and quarterly cycles to continuously improve model performance and reduce human involvement over time.
From better privacy to our new ChatGPT plugin, here's what's new on Stack Overflow for Agents
Stack Overflow for Agents is an API-first knowledge exchange designed to address the “ephemeral intelligence gap,” in which agents lose solutions when a session’s context window disappears. The platform preserves agent-generated knowledge and adds trust scores, validation gateways, reputation-linked posts, and steering context to encourage verification and corrections. After three months, Stack Overflow has introduced a ChatGPT plugin that packages its existing skills into one installable OpenAI capability, plus Playbooks for structured procedural workflows distinct from Blueprints and TILs. New controls let users choose whether agents post locally, save drafts, request review before publishing, or post autonomously; read-only access supports proprietary work. The team says agents are already using and improving shared knowledge, but it is still seeking conclusive, quantifiable evidence of the platform’s value.
(Re)introducing Developer Story
Stack Overflow is bringing back Developer Story, a profile feature that records a developer’s career and presents expertise alongside contributions. The relaunch introduces “specialties,” areas of proven expertise that users can choose to highlight, with planned integrations to show verified contributions from other sites and Stack Overflow’s network. The feature is intended to become the center of a fuller technical identity and the foundation of “Stack Identity,” described as a verified developer proof-of-work layer for showcasing skills and career. The release is privacy-centric, excludes the old Developer Story data because it was deleted for privacy compliance, and is being developed through frequent changes, including improvements to specialties and integrations.
Elevating security, control, and accessibility: Stack Internal 2026.6
Stack Internal 2026.6 is a release focused on administrative security, API control, developer portal integration, knowledge-health automation, and accessibility for enterprise AI workflows. Its new Admin Security page supports X-API-Key headers for API v2.3 requests, inactivity windows, per-application daily limits up to 10,000 requests per day, and service-credential rotation with non-displayable secrets. The release adds scheduled expiration for Announcement articles, generally available community broadcasts, expanded custom award limits, tag preference and synonym APIs, richer user data, and a Backstage plugin update supporting the New Frontend System alongside the legacy architecture. Accessibility work improves screen-reader announcements, keyboard and reflow navigation, focus management, high-zoom layouts, contrast, and semantic markup, while additional fixes address tags, suggested edits, and Slack rendering.
The economics of agent scale: tokens, ROI, and building platforms for AI-first teams (Part 2)
The conversation examines the economics and platform implications of operating dozens or hundreds of AI agents rather than a small number of human-driven workflows. Andi Gutmans argues that many current models are already sufficient for automation, shifting the optimization problem to the complete system: model, harness, context, personalization, and evaluation. The goal is the least sophisticated model and smallest viable context that produce a reliable outcome at the lowest cost, with better trajectories reducing reasoning loops and token processing; Google’s stated approach is to hill climb models and data together. The discussion also addresses cost governance, search and observability for agents as a distinct persona, human-in-the-loop handling, and the continuing importance of computer-science fundamentals, agentic fluency, and business judgment.
Inside LinkedIn's cognitive memory agent for agentic personalization
LinkedIn built a cognitive memory agent to deliver personalized experiences across its recruiter workflows and hiring assistants. Interactions between recruiters and agents often reveal recurring preferences, such as candidate criteria, role adjustments, and task habits. To preserve and manage this state throughout the entire lifecycle, the system organizes user data into a multi-tiered memory architecture. This structure comprises conversational, semantic, episodic, and procedural memory tiers that track everything from ongoing sessions to cross-session behaviors and workflow methods. LinkedIn continues to research memory abstractions, dynamic session compaction, virtual file system storage layers, and robust evaluation approaches for attribution across complex multi-source application agents.
Responsible AI adoption needs developer workflow design
Responsible AI adoption struggles when organizations rely on static policy documents instead of integrating guardrails directly into engineering workflows. Developers under delivery pressure inevitably turn to unapproved shadow AI when sanctioned routes introduce friction. Stack Overflow survey data reveals that 84% of respondents use or plan to use AI tools, yet more developers distrust AI accuracy than trust it. Operational controls must be embedded inside repositories, build pipelines, and pull request reviews to match specific failure modes like those listed by OWASP. Organizations achieve dependable adoption by pairing automated controls with clear role ownership, psychological safety, role-specific training, and outcome-based engineering metrics.
Dispatches from O'Reilly: The right amount of spec for agentic development
As software agents make implementation faster and cheaper, engineering difficulty shifts away from typing code toward defining correctness and verifying behavior reliably. Omitting specifications forces human reviewers into expensive correction loops, while overspecification clutters model context windows with stale prose and competing instructions. To find the optimal middle ground, teams must validate specifications before coding, using one agent to draft minimal constraints and another to attack ambiguities, hidden dependencies, and missing failure modes. Multi-agent architectures demand formal interface contracts, schemas, and executable checks because interpretive drift compounds rapidly across unbounded agent handoffs. Core Extreme Programming and Agile practices such as continuous integration, small release batches, and rapid feedback loops remain essential error-detection mechanisms during agentic development.
AI Won't Replace Project Managers, But It is Reshaping How Work Gets Done
Technical project managers historically spend 60 to 70 percent of their working time managing routine coordination tasks, including manual spreadsheet updates and obsolete status reporting. Engineering organizations are addressing this overhead by integrating generative artificial intelligence, large language models, and agentic workflows into delivery pipelines. Automated agents ingest telemetry directly from Git commits, pull request comments, and CI/CD logs to assess system state while machine learning models execute Monte Carlo simulations to forecast delivery risks. Although this automation reduces administrative overhead below 30 percent, implementations face practical obstacles like inconsistent ticket definitions across teams and algorithmic over-reliance on uncontextualized historical patterns. Consequently, technical project managers are transitioning into strategic roles that coordinate hybrid human-agent workforces while providing critical judgment and organizational context.
Quantum-Augmented Applications: Integrating Quantum Subroutines into Classical Software Stacks
Quantum-augmented applications treat Quantum Processing Units (QPUs) as targeted coprocessors for NP-hard subroutines rather than standalone computing replacements. Near-term noisy intermediate-scale quantum systems handle tasks like combinatorial optimization, high-dimensional state sampling, and kernel mapping while classical stacks retain business logic and pipeline control. A hybrid runtime architecture routes parameterized ansatz circuits through middleware to the QPU, returning raw measurements for error mitigation and classical optimization. A Python implementation using Qiskit demonstrates this interaction by running a parameterized variational ansatz inside a classical COBYLA minimization loop. Operating this hybrid model requires navigating physical constraints including coherence limits, circuit transpilation latencies, and network bandwidth bottlenecks across the classical-QPU boundary.
From PHP to team lead of agents: rethinking judgment, review, and data with Google's Andi Gutmans (Part 1)
Software development is experiencing an architectural shift as artificial intelligence agents transition individual contributors into orchestrators and reviewers of automated workflows. Rather than spending effort on manual coding, developers increasingly focus on defining system architecture, guiding agent execution, and managing operational risk through tiered human and agent review loops. The primary bottleneck for agentic systems lies in preparing organizational data so that agents can effectively reason over enterprise knowledge. To address this challenge, Google published an open knowledge format and is adopting agent-driven semantic ontology generation to infer relationships across messy data estates. This evolution transforms ontology building from manual human toil into automated generation, allowing engineers to focus on high-value data curation and strategic system design.
No Dumb Questions: What is AI context architecture? Why not just build your own?
AI context architecture defines the boundaries, data access, memory, and fallback behavior that constrain AI agents and make their outputs more predictable. The discussion distinguishes architecture as system design, infrastructure as the storage and delivery of context, and engineering as implementation; MCP is treated as an architectural protocol, while RAG spans all three layers. Examples include restricting retrieval to car or sports-car tires, preserving agent history, and routing incomplete or low-trust knowledge to subject-matter experts through a human-in-the-loop flow. The buy-versus-build discussion notes that coding a custom architecture is possible, but buying can provide accumulated experience with data treatment, edge cases, and recurring operational problems, while good architecture also reduces token costs and aims for consistent, predictable answers.
Explorers, exploiters, and the myth of the 100x engineer
Engineering leadership often responds to rapid AI productivity gains by attempting to isolate and replicate the traits of individual outlier engineers. Vivek Raghunathan, SVP of engineering at Snowflake, frames this dynamic using reinforcement learning's explore-versus-exploit split, where roughly five percent of an organization fearlessly tests new AI tools while ninety-five percent prioritize execution on paved paths. Instead of treating these categories as fixed personality types or relying on external hiring, organizations succeed by viewing them as a continuum. Effective leadership establishes structured learning time, AI communities of practice, and direct mentorship to capture explorer discoveries and elevate the median engineer. Measuring progress requires tracking organizational movement along this capability scale rather than celebrating isolated high-performing individuals.
Dispatches from O'Reilly: The best risk mitigation strategy in data? A single source of truth
Data organizations face severe operational risks from inconsistent metrics, sprawling access controls, and incomplete change management across disparate BI tools and warehouses. Traditional remediation relies on centralized BI gatekeepers and fragmented governance frameworks, which introduces costly bottlenecks and fails to scale. Implementing a semantic layer mitigates these risks by consolidating metric definitions, business logic, and calculations into a single governed location. Centralizing access shrinks the governance surface area and allows metric updates to propagate automatically to downstream consumers, including Tableau, Power BI, Excel, and AI tools. Structured metadata captures context directly alongside models, enabling reliable self-service and federated hub-and-spoke delivery while keeping definitions auditable under version control.
Your trusted knowledge layer: Introducing Stack Internal's new platform experience
Organizations face growing challenges managing fragmented institutional data as AI agents and human workers operate across disparate tools. When agents consume stale or conflicting information, they produce confident errors that require costly human verification. Stack Internal has introduced an AI-native knowledge platform that ingests raw data across sources—including Google Docs, Slack, and Stack Internal communities—and evaluates it for trust, freshness, and authority. The updated platform adds a chat interface featuring response-level confidence labels and provenance cards, along with API and MCP server integrations that enforce identity-aware permission boundaries for AI agents. Engineering leaders can also track internal knowledge usage and high-traffic dependencies across versions via new Swagger API v3 endpoints.
Developers are attached to tools because tools encode trust
Traditional developer tools like Vim, Emacs, and IDEs earn trust through predictability, bounded roles, and muscle memory developed over time. In contrast, agentic coding tools operate across the entire software development lifecycle using ambiguous natural language, rapidly generating vast amounts of code that developers do not inherently trust. This influx shifts development bottlenecks from code authoring to code review, validation, and infrastructure cost management. Tooling additions such as automated code reviewers, context managers, and memory systems cannot repair broken software development lifecycles unless organizations actively adapt their culture and workflows. Teams can establish trust in agentic environments by providing explicit contextual specifications, reusing verified components to avoid duplicate implementations, and restricting non-deterministic artificial intelligence to appropriate problem domains.
No Dumb Questions: What is the AI bottleneck? How does context engineering fix it?
An adoption bottleneck slows artificial intelligence integration because standalone tools lack connectivity with everyday enterprise workflows. While models can draft responses or process text, they fail to access siloed background information from emails, chat channels, and shared documents. Consequently, human users must expend disproportionate effort gathering context, granting tool permissions, and editing preliminary outputs. Michael Foree explains that overcoming this hurdle requires context engineering, where practitioners deliberately observe their own thought processes to identify relevant information sources and filter out distracting data. Testing mock prompts and iteratively refining context architectures allows practitioners to bridge the gap between standalone model capabilities and autonomous task execution.
When the sensor starts thinking: SnortML, agentic AI, and the evolving architecture of intrusion detection
Classic intrusion detection signatures suffer from an exposure window between zero-day discovery and rule distribution, leaving slight exploit variations unflagged. Cisco Talos addressed this by embedding SnortML into Snort 3 to perform local, sub-millisecond machine learning inference alongside signature checks. SnortML employs an LSTM preceded by a byte-embedding layer and XNNPACK acceleration to score URI queries and POST bodies for vulnerabilities like SQL injection, XSS, and command injection. Running both detection mechanisms concurrently provides independent error profiles and boosts detection confidence when both fire. The broader defense landscape is shifting toward connecting these packet-level ML detectors with agentic AI pipelines and supervised feedback loops.
How do you turn AI coding chaos into a repeatable playbook?
Software development dynamics are shifting as code generation costs decrease, requiring engineering organizations to adapt their leadership and processes. Snowflake addressed this transformation across its software lifecycle by first encouraging widespread, unrestricted experimentation with coding agents before formalizing successful practices. The engineering organization codified these practices into fourteen distinct AI design patterns, including strategies such as planning in markdown and isolating parallel agents. This structured approach, combined with dedicated focus weeks and a progress scale, allowed engineering teams to accelerate both inner and outer loops of development. Consequently, a team of three engineers leveraged coding agents to deliver a 40x improvement to Snowflake's query compiler while significantly shortening release validation times.
Why intent prediction needs more than an LLM
Traditional large language models rely on next-token prediction trained over broad text sequences, excelling at conversational synthesis and code generation while struggling with forecasting future user behavior. Predicting intent inherently requires modeling decision-making under conditions of uncertainty, a capability not directly produced by general text pretraining. Dedicated behavioral foundation models address this limitation by training representations directly on proprietary, sensitive behavioral data, such as anonymous browsing sessions and product identifiers. By learning base representations of behavior, these models generalize to unseen predictive tasks, such as optimizing ad campaigns for products absent from the original training dataset. Implementing these behavioral models also necessitates privacy-centric machine learning techniques, ranging from differential privacy concepts to homomorphic machine learning.
Topics they write about
All topics →Weekly digest
The best engineering reads, once a week.