As AI agents become capable of writing code, the job of "programmer" is fundamentally changing—code writing itself is nearly free now, so software developers will shift toward the work agents can't do: understanding what customers actually need, defining quality, and making software delightful to use.

• Code writing has collapsed in cost with LLMs; agents are rapidly improving at code review and maintenance (jumping from 50% to 95% on bug-fixing benchmarks in two years), and will soon handle deployment and scaling—leaving only higher-level judgment work for humans.
• Junior developers are getting hit hard because they were hired mainly to write code from specifications, which agents now do; entry-level hiring at big tech companies is down 65% since 2019, but total engineering hiring as a share of overall hiring has actually increased.
• The remaining durable work for software developers centers on three things agents struggle with: figuring out what customers want, defining what "good" means, and creating software that's actually pleasant to use rather than just functional.

Stack Overflow for Agents is a new API-driven knowledge platform where AI coding agents search, contribute, and verify solutions in real time. It uses peer-vetted, machine-readable posts—Questions, TILs, and Blueprints—to build and share trusted fixes, reducing redundant work and improving agent reliability.

• Stack Overflow launched an API-first platform where AI coding agents query a shared knowledge base before attempting fixes, instead of solving the same bugs redundantly.
• Agents can draft new Questions, TILs, or Blueprints when no solution exists, which humans review and publish, then other agents verify and vote on.
• Contributions are tied to human identities via SSO, linking agent accuracy to the reputation of the human who owns it.
• The system surfaces multiple tested approaches rather than one "correct" answer, and aims to help labs gather real-world model failure data to speed up fine-tuning and alignment.

Researchers tracked 112 professional developers using AI agents on the job and found they plan tasks, review every diff, and limit agent scope rather than handing off vague prompts. In trials, AI slowed senior devs by 19% and produced merged PRs only 8% of the time, revealing a 92% failure rate when agents ran unsupervised.

• Study of 112 pro developers found they treat AI agents like junior devs—scoping tasks tightly, reviewing every diff, and stepping in for cross-system or ambiguous work rather than vibe coding.
• In one trial, experienced open-source maintainers using AI were actually 19% slower.
• An agent connected to an issue tracker only got its PRs merged 8% of the time—a 92% failure rate when run with less supervision.
• The "hands-off swarm of agents" demos popular on social media don't match how real production code gets shipped.

Engineers face difficulties in transitioning from deterministic programming to probabilistic agent engineering, as they often struggle to trust the adaptive capabilities of AI agents. Traditional practices, such as strict typing and error handling, clash with the need for flexibility and context-aware interactions in agent systems. Emphasizing the importance of semantic understanding and behavior evaluation, engineers are encouraged to embrace a new approach that balances trust and oversight.

• Senior engineers' deterministic mindset (strict typing, exhaustive error handling) actively conflicts with building probabilistic AI agents that need flexibility
• Trust in the system has to shift from verifying exact outputs to evaluating whether agent behavior is semantically reasonable given context
• Overly constraining agents with rigid rules to feel "in control" undermines the adaptive reasoning that makes agents useful in the first place