What unverified output costs in practice, and what regulators now require.
In a randomized trial, experienced open-source developers were 19% slower with AI tools, while estimating they were 20% faster.
METR — Measuring the Impact of Early-2025 AI on Developer Productivity · 202516 developers, 246 real tasks in familiar codebases; under 44% of suggestions accepted.
Output quality is the #1 barrier to putting agents in production (32%) and to scaling them (33%), ahead of latency at 20%.
LangChain — State of Agent Engineering (n≈1,300) · 2025Vendor-run survey of its own ecosystem.
30% of developers trust AI-generated code a little or not at all; the report's follow-up analysis names the 'verification tax': time saved writing is re-spent auditing.
Google/DORA — State of AI-assisted Software Development · 2025The EU AI Act requires high-risk systems to log events automatically (Art. 12), remain overseeable by humans able to detect anomalies (Art. 14), retain logs at least six months (Art. 19), and ship 'concise, complete, correct and clear' instructions (Art. 13).
Regulation (EU) 2024/1689 — statutory text · 2024Inadequate software-testing infrastructure was estimated to cost the US $22.2–59.5 billion per year.
NIST — Planning Report 02-3 · 2002A 24-year-old software-bug study, often quoted without its year or scope. Cite it as history, not as a current documents figure.
90% of developers regularly use at least one AI tool at work; 74% use a specialized coding tool.
JetBrains AI Pulse survey (n≈10,000, fielded January 2026) · 2026The freshest developer-survey figure available. Stack Overflow's 2026 survey opened in June — 'for human developers only' — with results not yet published, so the 2025 numbers remain the newest SO data.
275 million commits a week on GitHub, against one billion commits in all of 2025.
GitHub COO Kyle Daigle, on record, April 2026 (captured by Simon Willison) · 2026The verifiable substitute for the viral 4M-to-17M agent-PR claim, which traces only to a paywalled report and stays uncited here.
Reviewer defect-detection drops sharply past 200 to 400 lines per review session.
SmartBear/Cisco peer-review study (Cohen et al.) · 2006About 2,500 reviews over 3.2 million lines of code. A per-session attention limit, not an organizational capacity law.
In one study, 15 of 18 writers assisted by ChatGPT could not quote their own essay minutes after writing it.
Your Brain on ChatGPT — MIT Media Lab (preprint) · 2025Small-sample preprint (n=18 per condition); a methodological comment raises sample-size concerns. Formerly on the landing deck; the deck now argues review capacity rather than reader memory.
Anthropic's own developer docs instruct: hallucination-reduction techniques do not eliminate hallucinations — always validate critical information.
Anthropic developer documentation, reduce-hallucinations guide · liveThe vendor prescribing the practice; the landing page cites it as its quickstart support line.
People find only 40–90% of errors when working alone: readers caught 81% of nonsense-word errors but just 66% of real-word errors, and detection of nonsense-word errors falls to 47–58% in difficult material.
Panko — Errors in Proofreading, summarising published detection-rate experiments (difficult-material figure from Riefer) · 1980–1993Laboratory experiments on general prose. The 47–58% figure is Riefer (1991) for NONWORD errors in difficult material; Riefer's word-error range is 42–62%. The 87% professional-proofreader figure on the same page rests on three editions of the author's own textbook and is deliberately not used.
Across 22,000 developers, the median time a pull request spends in review rose 441% year over year — against 91% in the prior year's dataset — 31% more pull requests merged with no review at all, and 25% of pull requests are now reviewed by an AI agent.
Faros AI — The Acceleration Whiplash · 2026Vendor telemetry from a company selling engineering analytics. The year-over-year comparison runs on the same pipeline, so it is like-for-like, but the methodology note is not public.
In one year on GitHub, pull requests created rose 20.4% and commits 25%, while comments on issues and pull requests rose 0.35% and comments on commits fell 27%.
GitHub Octoverse · 2025GitHub labels these observational signals rather than causal claims. Comments proxy for review attention rather than being it, and Copilot code review shipped in April 2025, so part of the flat line may be review that moved to a machine.