Working Surfacelink · 14 Nov 2026
01
A railway sorting yard where a lever-operated switch sends most light goods wagons straight through an open gate, while a few heavy sealed wagons are diverted onto a side track where a lone figure seen from behind waits with a lantern to inspect them, the whole scene drawn with wide empty margins on every side.
Dev Interrupted

All the code review is a stage

Andrew Zigler · 12 November 2026

Company story · critique & review · roles · Human approval

Read the original
Takeaway

Engineering leaders told Andrew Zigler of Dev Interrupted that AI-written pull requests have outgrown careful review, so they now sort changes by risk before deciding who reads them.

Summary

Andrew Zigler writes Dev Interrupted, the publication of LinearB, which sells engineering metrics software. He asked engineering leaders where pull request review had become a formality as AI agents wrote more code, and what replaced it. Their answers describe sorting changes by risk, routing risky ones to a qualified reader and spreading the review load.

Key points
  • LinearB's figures from more than 8.1 million pull requests show AI-generated pull requests merging at 32.7%, against 84.4% for human-written ones, and waiting 5.3 times longer for a reviewer.
  • At Postman, an API platform, tests, documentation edits and internal business logic can merge without a person, while authentication, billing, public APIs and core data model changes still need one.
  • At Deel, a payroll company, each AI reviewer's configuration, approved instructions and findings can be traced, and a missed issue is fixed in the reviewer's instructions.
  • At Harness, a software delivery company, automatic merging is paused for a class of change after an incident until the check that missed it is fixed.
Implication

An engineering team could write down which kinds of change may merge on automated checks alone and which need a named reader. This is an inference and is not the author's claim. The piece is published by LinearB and ends by promoting its product.

Plays
Engineering

Sort pull requests by what they could break, let test and documentation changes merge on passing checks, and send authentication, billing or public API changes to a qualified reviewer.

Engineering

After a production incident, stop pull requests of the same kind from merging on automated checks alone until the team fixes the check that missed the problem.

Derived by Working Surface from the article; more in the Playbook. Source line: A rubber stamp is a governance policy too.

Source issue

14 November 2026: as AI agents produce more code and tests than people can inspect, teams are writing down which work gets checked closely, by whom or by what, at what cost, and how they will know it worked.