The Pull Request is Dead - by Arman Wolkensteiner-Jalili
Bounded Autonomy
SubscribeSign in
The Pull Request is Dead<br>AI writes at token speed. We read at human speed. Holding onto the ritual isn't rigor—it's denial.
Arman Wolkensteiner-Jalili<br>Jul 23, 2026
Share
A single AI coding session now produces more code than a senior engineer can meaningfully review in a week.<br>Not a busy week. Any week.<br>The model writes at token speed, we read at human speed, and that gap has been widening every quarter with no sign of closing.<br>I’ve sat in enough reviews to know what that gap actually produces in practice. You scan the diff, check whatever looks like a hot path, skim a test or two, approve if nothing jumps out as obviously broken.<br>That’s not review. It’s a sanity check performed under time pressure, and most engineers I know will admit as much.<br>The Illusion of Quality
What makes this easy to ignore is that AI-generated code is often genuinely good. Good enough that the ritual keeps looking legitimate long after it’s stopped meaning anything.<br>When you physically cannot read the volume of code in front of you, calling it a review is being polite about the fact that the model already decided what’s going into production.
What High-Stakes Manufacturing Got Right
Manufacturing is instructive here, though not in the way people usually reach for it.<br>In high-stakes manufacturing—aerospace parts, medical devices—you still inspect the individual unit, because the cost of one failure is too high to accept anything less. But nobody’s standing there eyeballing the part and deciding if it looks right.<br>The inspection is a calibrated instrument checked against a spec, run the same way every single time. The rigor doesn’t come from a person’s judgment under time pressure. It comes from a deterministic check that doesn’t get tired, doesn’t get rushed, and doesn’t have to be trusted on instinct.<br>Moving Constraints to the Front
This isn’t about trading quality for speed. Software is too critical for that trade, and anyone arguing we should just accept less rigor to keep up with volume is arguing for the wrong thing.<br>The point is that we can keep the same bar—arguably a higher one—by moving the constraints to before the code is written, and replacing “a person reads every line and forms a judgment” with a mechanism that checks deterministically and doesn’t degrade under load.<br>Line-by-line reading was never as reliable as the ritual implied. It just used to be survivable, back when the volume was low enough that cognitive load and ordinary human error rate didn’t matter as much. They matter now.<br>Instead of asking “does this diff look okay?” after the code already exists, you ask “what is this change allowed to do?” before it’s written.
You define the boundary—which files it can touch, what patterns it has to follow, what it’s explicitly not allowed to introduce. The model generates inside that boundary. A pre-commit gate checks conformance automatically, before a human ever needs to look at a line.<br>From Diff-Reader to Constraint-Architect
Reading the code is the job. But we’re not in that world anymore. Nobody reads every line, we pretend otherwise, and the model has effectively been making the moment-to-moment calls unilaterally for a while now.<br>Constraint-defined review is the only version of this that scales:<br>Policy gates that run pre-commit
Automated boundary checks
Structural validation that executes as fast as the code gets written
The engineer’s role shifts from reading diffs to authoring constraints, and from approving PRs to auditing the exceptions the gate flags.<br>You give up granular control over the moment-to-moment syntax. What you get back is the thing that actually matters over time—whether the system still holds together structurally, six months and ten thousand commits from now.<br>The Smoke Detector
The pull request assumed someone was on the other end reading the code. That assumption is gone, but the ritual is still bolted to the ceiling like a smoke detector with a dead battery—it looks like it’s doing its job.<br>Holding onto it after the substance is gone isn’t rigor. It’s just avoiding the real work of building the thing that replaces it.
Subscribe
Share
Discussion about this post<br>CommentsRestacks
TopLatest
No posts
Ready for more?
Subscribe
© 2026 Arman Wolkensteiner-Jalili · Privacy ∙ Terms ∙ Collection notice<br>Start your SubstackGet the app<br>Substack is the home for great culture
This site requires JavaScript to run correctly. Please turn on JavaScript or unblock scripts