If Review Is The Bottleneck, Maybe The Bottle's Too Full

Chris Fildes · · 2 min read

  • Modern Engineering Practices
  • AI-Assisted Engineering
  • Quality Engineering
  • Continuous Delivery

GitHub says it saw more than 1.2 billion commits in a single week this October. That is over 400% more than the same week last year, and more than all of 2025. The post, published after GitHub Universe, asks the obvious follow-up: do you feel 400% more productive?

The answer, for most teams, is no. GitHub points to Faros AI's Acceleration Whiplash report (March 2026, telemetry from 22,000 developers). Median time in review rose 441% as teams moved to heavy AI use, and 31% more PRs merged with no review at all. Nobody chose to stop reviewing. The volume just outran the reviewers.

Atlassian's State of Developer Experience 2026 report shows the same gap from the developer's side. 87% of developers say AI helps them ship faster, but 65% spend time correcting AI work that missed the original intent. Meanwhile 60% say AI use itself is treated as a productivity signal where they work.

GitHub's answer is to put agents on the surrounding work too, splitting changes into stacked PRs, running AI review first and having agents fix failing checks. That will help. But it is a vendor selling more agents as the fix for agents, and it says little about the human part, such as who owns a merge and how a reviewer learns why a change was made.

Here's my problem with that framing. Everyone, GitHub included, treats review as the bottleneck and asks how to widen it. I'm not sure review is the problem. I think we're trying to put too much in the bottle.

When code was expensive to write, cost did a lot of quiet filtering for us. Half-baked ideas died in planning because nobody wanted to spend a sprint on them. Agents removed that filter, and we haven't replaced it with anything. So we build what we can build, not what we should, and the review queue is where the bill shows up.

A 441% jump in review time might be telling us less about reviewers and more about what we ask agents to make. Before adding another AI reviewer, it's worth asking how many of those PRs needed to exist at all.

Deciding what not to build is still a human job, and it may be the one that needs the most attention right now.