Technical Context
I appreciate these texts not for the hype, but because they finally name the problem directly: code reviews have become a bottleneck. When I design AI architecture for engineering teams, I almost always hit a wall not with code generation, but with who should review it and when.
Eric Zakariasson's idea is simple and highly relevant: a code owner no longer has to be human by default. An agent can process a PR, assess the risk, auto-approve minor safe changes, and only call a human when something can actually break.
This isn't magic or a lack of control. It's a standard risk-based approach: renamed a variable, fixed text, or extracted a constant without changing behavior? The agent lets it pass. Messed with billing logic, access rights, subscription duration, or critical flags? Escalation goes to a human.
The second publication, Reviews are Dead, pushes the idea further. I read it as confirmation that AI implementation in development is already shifting the very checkpoint itself: an agent doesn't just comment on the diff, but validates, rewrites, runs tests, verifies invariants, and only then shows the result to a human.
This is where I paused. Because this is no longer a "reviewer's assistant," but a new layer of code ownership where human review becomes the exception rather than the default route for every change.
Impact on Business and Automation
The practical effect is very grounded. Teams stop waiting for the "right senior to be online," and the merge flow depends less on time zones, moods, and the workload of a specific reviewer.
Products with a massive stream of minor changes win big: internal platforms, SaaS, and support-heavy teams. Conversely, processes where every PR is routinely forced through the same heavy manual review—even if the risk is near zero—will lose out.
But there's a trap: if you just slap an agent on top of chaos, you get chaos on autopilot. You need clear risk rules, solid access policies, testing barriers, and proper AI integration in CI/CD. At Nahornyi AI Lab, we build exactly these solutions for clients: not "just another bot," but a working AI automation schema without unnecessary blockers.
If your development is already stalling at the review stage, I wouldn't cure it by hiring a couple more exhausted approvers. It's better to look at your entire workflow and build a layer of agentic control so that speed grows without trading off for chaos. If you'd like, at Nahornyi AI Lab, we can design such a system together tailored to your team and risks.