Well Made Used to Mean Something

Anyone who has ever hired someone has made this inference. Work arrives finished, tidy, the numbers adding up, no loose ends, and from it you conclude something the work itself never states: that hours went into it, that the person understood what they were doing, that they are probably worth keeping. The inference was never naive. For centuries it was the only one available.

On 5 August it was declared unusable, in writing, somewhere nobody was watching.

Rust is a programming language with no owner. Volunteers scattered across the world maintain it, the code is public, and anyone can propose a change. Proposing is not deciding: the proposal, called a pull request, has to be read by someone else who takes responsibility for accepting it. The arrangement is older than software. You bring something, another person examines it and puts their name next to yours.

Five teams in the project adopted an LLM policy that day, and Jynn Nelson, who wrote it, explained why in public. One sentence carries the whole thing, and it has the flatness of an audit finding: "polished technical products no longer indicate effort."

Open source spent years measuring what a contribution cost to produce and calling that cost competence. The cost was the message. A clean pull request with tests and documentation took hours out of somebody's evening, and Rust built three habits on that arithmetic: close a proposal reluctantly, because it represents a person's work; argue about it in the open, letting the project change its own mind along the way; treat whoever sent it as somebody asking to join. Three social rules resting on a single assumption about price.

Models changed the price and left the object untouched. The proposal looks exactly as it did and now says nothing, which makes a polished pull request into the demo of understanding, and demos have always been cheap to build. You can read the result in the queue: 1,281 pull requests sitting open, waiting for a human to look at them. Writing became free while reading stayed expensive, and reading is where the decisions live, because a reviewer settles whether a direction makes sense for the next ten years. Nobody discounted that.

A project with an owner settles this in one line, and two of them did. Zig bans model-generated code and prose outright. Torvalds, who rules Linux, treats it as one more tool in the box. Rust had neither option, because it runs on consensus and its own policy states plainly that consensus here will never arrive. Where the others declared, Rust had to design.

What they designed is a rule they admit they cannot enforce in several places. The obligation moves from verifying to declaring: you must say whether a model was involved, and moderators act on an observable fact, the silence, leaving intent alone. The line that shows how well they understood the problem is aimed at their own reviewers, and it is a prohibition: style proves nothing, and accusing a contributor of using a model is forbidden. Once an object stops carrying its origin, reading it for clues is divination, and a community that starts guessing becomes a community where people accuse each other. They gave that up before it started.

Plenty of immaculate pull requests came from people who vanished a month later, and plenty of scruffy patches came from those who stayed a decade. The signal was noisy long before any of this, and the review queue was already jammed. What changed is the character of the noise: it used to be random, and it now scales with whatever compute you point at it.

The policy keeps the machine in the room and takes one permission away: creating. It stays welcome to answer, analyse, distil, check, suggest and review. Where it remains allowed the bar goes up, because model-written code must carry tests, always, however inconvenient, and must stay clear of the parts of the language that everything else depends on for not breaking, unless the author already knows that ground, and even then it is discouraged. The working line is four words: "write better, not faster." Nobody here wanted a replacement. They put the machine where it extends how far a human judgment reaches, and forbade it to sign.

Nelson reaches for Asimov's Profession, the story where knowledge is installed by tape and anyone who cannot take the tape is filed as defective, until it emerges that new knowledge only ever comes from the rejects. The policy signs off with three words: "No programmer tapes."

The same thing is now happening to everyone who hands work to somebody else for judgment. The cover letter, the exam essay, the report that lands on a manager's desk on Friday evening, the surveyor's assessment, the builder's quote that looks properly done. In every one of them the cost was the message. Two roads are left, and choosing between them is a political act before it is a technical one. The first is the metal detector at the door: detectors, provenance tracking, suspicion as the default posture, the burden carried by the institution and every member handled as a defendant. The second is asking people to state how they worked, accepting that some will lie, and treating them as adults until shown otherwise. Rust took the second and paid the full price, ending up with a rule its own author says everybody rather dislikes.

From here on, the well-made thing you hand over says nothing about you. What is left is your ability to explain why you chose that way and to hold up under questions from whoever has to sign next to your name, which happens to be the one thing no machine can hand over on your behalf, because it is not an object.

Good work never spoke for you. It only saved you the trouble of saying it.