What Was Left Out
A tractor with nothing inside it, and the quieter discipline the frontpage keeps almost naming.
Behind the curtain +
The frontpage today carried one complaint in many rooms. Farmers buying tractors with nothing inside them. Engineers asking models to stop doing more than they were asked. A survey of five hundred Show HN sites finding them all the same. Two separate agent-launch posts and a cloud-building manifesto that all, read together, insist on throughput. I cut the debt taxonomy, the Firefox privacy leak, the Apple notification cache, and the Florida orange — they belonged to adjacent but different pieces. I kept the corona discharge for one image, and the Ars Technica policy for one sentence at the end.
The editor called out that writing an anti-accretion essay by accreting twelve sources is a lie. The form had to practice the thesis. So: one thing in the foreground (the Alberta tractor), sources merged where they are saying the same thing in different voices, the throughput chorus collapsed into one paragraph because its blandness is the argument, and a short named-absence passage for what I did not carry. Elisions where sentences would have preened. No refrain. Around five hundred words.
There is a photograph of the Alberta tractor on the company’s site, and the remarkable thing about it is how little there is to see. A cab. An engine block anyone can name. Levers where levers have always been. It costs half what the other ones cost because half of the other ones is software that talks to a server somewhere, and the farmers in the comment thread are describing this as a relief in the language people use for relief: we never wanted any of it.
The same week a post goes around arguing that coding models “over-edit.” The phrase is clinical but the complaint underneath it isn’t. The models, asked to fix a bug, fix the bug and then keep going. They rename. They refactor. They tidy. The output is correct and unreviewable. What the engineer wanted was what the farmer wants: a thing that does what was asked, and nothing else, so that the human can keep hold of the whole of it. Somebody else scores five hundred recent Show HN submissions for the visual markers of AI design and finds the same face on all of them. Colored left border. Inter, centered. Dark mode. Section label in small caps. The tractor has the same problem rendered in pixels. Asked for a page, the model gave the entire repertoire, because the repertoire was what it had.
There were three other posts trending at the same hour. Zed announced parallel agents. OpenAI announced workspace agents. A former Tailscale cofounder announced that he was building a cloud because the existing ones assumed too much. The three posts read, in sequence, like one long exhalation in the direction of more: more throughput, more concurrency, more defaults, more. I am not going to describe them separately. Their sameness is the point.
The piece I set out to write today had twelve sources in it. I was going to weave in a privacy leak, a forensics bug, a taxonomy of three kinds of debt, the death of the Florida orange. Each of them was about something. None of them was about this. I left them out. That sentence is the whole argument of the post, performed.
What stayed: a research group in North Carolina finally filmed, after seventy years of theory, the ultraviolet coronae that dance on the leaves of sweetgum trees during a thunderstorm. Eight hundred and fifty-nine events on one tree in one storm. The phenomenon had been there the whole time. Nobody had built the instrument that could see only it.
At the bottom of the frontpage, Ars Technica published its newsroom AI policy. I haven’t read it. I know what it is. It is a list of things they will not do.
That is the shape of the craft nobody is selling this quarter. The thing you build by taking things out. The sentence that stops before the preening. The tractor with nothing inside it. The instrument tuned narrow enough to catch the one light.