Six months ago I wrote about how to kill the code review, and I was wrong. I still think line-by-line The post Kill the code review theater, keep the review appeared first on The New Stack.
Six months ago I wrote about how to kill the code review, and I was wrong. I still think line-by-line The post Kill the code review theater, keep the review appeared first on The New Stack.
In context
- Topic: Desarrollo con IA — Copilotos y agentes en el ciclo de desarrollo de software.
- Source: The New Stack
- Published: 30/09/2026
Continue reading at the original source →
Excerpt published automatically by the site radar. The full text belongs to its publisher and is linked above.
Why it matters
AI applied to development moved the bottleneck. Writing code stopped being the slow part; now the slow part is reviewing, understanding and maintaining what was written. Any team adopting these tools without adjusting review gets faster in week one and slower by month three.
I distinguish between accelerating an experienced developer and accelerating someone just starting. In the first case the tool multiplies judgement; in the second it multiplies the lack of it. Adoption policy has to acknowledge that difference or the codebase fills with plausible, wrong code.
What usually goes wrong
What usually goes wrong is that review does not grow at the same rate as production. The team generates twice as much and still has the same two people reviewing, who get tired, start approving faster, and three months later quality has dropped without any indicator showing it yet.
What to watch
- The effect on people newly joining the team, which is where judgement erodes fastest.
- Whether total time to production drops or only writing time, which is not the same thing.
- What happens to code review: if the assistant produces more, somebody has to read more.
How I read this entry
What I would ask to measure is not lines or accepted suggestions, but defects reaching production and review time per change. If those two go down, the tool works. If they go up while speed goes up, debt is being accumulated and it gets paid in incidents.
This entry is an excerpt from the original source, selected by the site radar. The commentary above is the site's own and does not belong to the cited publisher.
Comments
No comments yet. Yours can be the first.
Living through this in your own team?
Open the chat and tell me how you're handling it. I'm interested in comparing notes.
