A senior developer on r/cursor spent 20 minutes reviewing a Claude Code utility that was cleaner than a junior’s similar PR — which took 5 minutes to approve. The AI code had better structure and error handling. It still took four times longer to ship.
The reviewer’s process for each PR:
- Junior’s PR: Read in 5 minutes, approved. Messy naming, one function too long, no error handling.
- Claude Code’s PR: 20+ minutes. Ran through CodeRabbit, then BugBot, then Claude again. Read the diff twice. Manually tested edge cases he never tested on the junior’s PR.
The code quality gap ran in the wrong direction. The AI output was objectively cleaner. The review time gap came from something else — the reviewer watched the junior’s code get made. The junior asked about the vendor CSV format at lunch. He fought type errors during standup. By the time the PR landed, the reviewer already knew the story behind every decision.
Claude Code’s utility showed up fully formed with no history. No abandoned approaches, no dead ends, no visible reasoning. The reviewer couldn’t tell whether the clean structure meant the agent understood the problem or pattern-matched its way to something that looked right.
NOTE
A LinkedIn post from Robbie Allen reports senior engineers now spend 3-4x longer reviewing AI-generated code, calling the output “almost right, but not quite.” A separate developer account estimates 60% of their time is now spent on PR review.
The bottleneck isn’t code quality — it’s context loss. AI agents ship diffs without the social trail that makes human PRs reviewable. Until review tools surface what the agent tried and discarded, senior devs will keep paying a context tax on every AI-generated PR.