Fifty years of review. One quiet inversion.
How the bottleneck moved from typing to meaning — and why the scarcest resource in your building is now the one nobody budgets.
diff & patch
Larry Wall hasn’t even written patch yet; changes travel as printouts and mailing-list diffs. Attention was assumed — reading was the whole job, because there was so little to read.
git
Version control gets fast enough to disagree in. Branches multiply. Somewhere, the first “LGTM” is typed by someone who mostly meant it.
the pull request
The greatest reading ritual ever shipped: here is my change, will you take it? A generation learns craft inside green and red diffs. Still merging. Forever loved. This site is its tribute act, not its funeral.
LGTM enters muscle memory
Reviews scale; reading doesn’t. The checkmark starts drifting away from the comprehension it was invented to certify. Nobody notices, because the humans still type slower than they think.
“Attention Is All You Need”
Eight authors teach sand to pay attention. It is a mechanism — queries, keys, values — and it works so well that within a decade the machines write most of the world’s new text. The title was a spec. We thought it was a paper.
autocomplete grows opinions
The assistants arrive. First they finish your line, then your function, then your afternoon. The diff volume curve leaves the chart. The reading volume curve does not.
the queue inverts
Agents take goals, plan phases, open pull requests, and wait. For the first time since the punch card, machines queue on humans — not for compute, for comprehension.
the attention request
Reading becomes the ceremony. The document becomes the program. And the ten quiet minutes a human spends understanding what’s about to happen become the most leveraged minutes in the company.
Proportions invented. Direction unarguable.
Every era of work has a scarce thing, and every scarce thing gets a ritual. When compute was scarce, we booked time on the mainframe. When typing was scarce, we hired typists, then engineers, then more engineers. The rituals — the sign-up sheet, the code review, the sprint — were never about the artifact. They were about spending the scarce thing on purpose.
The scarce thing has moved. A competent agent now turns a well-written paragraph into a working system overnight, which means the paragraph is load-bearing. Whether anyone actually understood it — before it ran, while it ran, after it ran — is now the difference between a company that compounds and a company that accumulates surprises.
Here is the uncomfortable symmetry: we spent two decades engineering machine attention until it became abundant, and the same two decades letting human attention be strip-mined until it became rare. The machines read everything, always, without fatigue. We read almost nothing, and mostly confirm it. Both trends are still accelerating, and they cross exactly where your approvals live.
This is the laugh-or-cry part. You may pick either. We alternate.
The attention request is a small idea about that crossing. It does not slow the machines down; they keep shipping at machine speed. It does not romanticize reading; it schedules it. It simply takes the ten minutes of human understanding that were always the real bottleneck and gives them a name, a place, and a gate — so that what runs at machine speed is something a human, on the record, actually meant.
Whatever the machines become, the reading is ours. It was always the best part.
The machines got our attention. Now they’re requesting it back.
Politely. Formally. One document at a time.