The true reason why code review is universal is that it provides a liability shield for negligence. Negligence is interesting. It has nothing to do with whether or not you ship something broken. As long as you follow a process that attempts to not ship something broken, then you are not negligent.

Engineers played along with this farce because code review served valuable team collaboration, coordination and management functions, about which the author of the article is correct.

Understanding a system by reading code is harder than understanding a system by writing code.

If AI can generate code at 100X, 1000X, or 10000X human capacity (no ceiling here), and you are gated on code review as your mechanism for system understanding, then a team's productive output will barely increase.

If companies want to compete in the world of AI generated code, human code review has to go. The only question is, what replaces it?

Continuing to apply human code review to AI generated code is negligent, if you are shipping at AI generation speed, with that as your only gate, and no other systems and processes to validate correctness and limit risk.

On the engineering side we can adapt easily.

Code review was never about finding bugs. When we do code review the first thing we check is: "do the tests pass?" Then we look at the change and the test coverage added for it and ask: "does the test coverage adequately demonstrate the functionality of the code?" The we ask: "What is the scope and potential impact of this change?" "What is the deployment and rollback plan and how will we monitor and detect defects after deployment?"

Code review was never about the code. It made the lawyers happy and provided a vehicle for doing the things that actually make systems work.

> If companies want to compete in the world of AI generated code, human code review has to go. The only question is, what replaces it?

You’re going a bit hand wavy for an answer by redefining the term into something that fits what you’re promoting.

I guess out in the wild vibe coders will tell you code review is replaced by "prompt review"

"does the test coverage adequately demonstrate the functionality of the code?"

and is this a solved problem? If not, then the bottleneck is right here, if it is solved, then yeah we shouldn't need anymore software engineers other than the elites