Imagine a team where artificial intelligence (AI) agents write most of the code, and then imagine it ten or a hundred times bigger. Writing code stops being the slow part. This post walks through the stages that become slow instead, from reviewing pull requests to talking to other systems, and proposes the best fix for each one.
When a coding agent writes most of the code, reading every diff stops being realistic, and "reading diagonally" — skimming — becomes the default. It is a real bet, not a safe one: architecture doesn't break in any single diff, it erodes across all of them, and skimming checks exactly the part that was never the problem.
Every strategy for surviving the flood of machine-written pull requests optimizes the same thing: catching bugs. The research on code review says catching bugs was never the job it was best at.