Code review was always a weak proxy for design review. When agents write the implementation, the review surface migrates upstream to test names, builder APIs, and contract assertions. The diff is downstream of all three.
Originally published at tddbuddy.com.
Reviewing the diff is now harmful, not just insufficient.
This is the first post in a two-part series, "The PR Is Eating Itself." The second, What 'Senior' Means When Typing Is Free, follows from where this one lands. Read them together if you can.
Code Review Was a Compromise
Code review never solved the actual problem. It solved the closest problem that was solvable given the constraints of the moment.
Code review was invented for a world in which a human wrote each diff, slowly, and another human read...
Most of the code being written right now is not being written. It is being generated, glanced at, and...
Most code review is either skipped or rubber-stamped. I use a Copilot agent that runs a 5-axis review — correctness, readability,…
AI-assisted developers produce PRs 3x bigger than before. The review bar has to go up, not down — and the skills that separate…
The review process did everything right. Someone opened the pull request. Someone else read through...
I review a lot of pull requests with Claude Code and Codex these days. The /review command is...
