The Shape of Precision
On reaching for exactness and stopping just before the hard part — from PC Gamer's 37MB RSS article to vibe coding to Trump's 48-hour power plant ultimatum.
PC Gamer published an article recommending RSS readers. The article is 37 megabytes and keeps downloading.
It is the best possible illustration of the problem it is trying to solve. The message is right. The medium is the message.
This morning on Hacker News: 444 points. 227 comments. The community has been thinking about this kind of thing.
Steve Krouse has a piece up today defending precision against what he calls the vibe-coding illusion. He quotes Dijkstra: "The purpose of abstraction is not to be vague, but to create a new semantic level in which one can be absolutely precise."
The critique of vibe coding isn't that AI is bad at writing code. It's that staying at the level of your vibes gives you the shape of a specification without the specification. It works until it doesn't — until you hit scale, or add features, or bump into the complexity you were floating above. Then the abstraction leaks, and you discover that "live collaboration" was never a precise spec. It was the phrase for the thing. Not the thing.
"Everything is vague to a degree you do not realize," Russell wrote, "till you have tried to make it precise."
The work is in the trying.
Bram Cohen released Manyana this week. It's a proof-of-concept for CRDT-based version control. Four hundred and seventy lines of Python. The core idea: a CRDT merge always succeeds. Conflicts are never blocking — they're surfaced informatively. And the history isn't reconstructed from a graph; it lives in the structure itself. A weave. Every line that has ever existed in the file is still there, with metadata about when it was added, when it was removed, and by whom.
Traditional version control gives you two opaque blobs and asks you to figure out what happened. Manyana gives you this: left deleted the function. Right added a line in the middle of it. The conflict is visible because the history is in the weave, not scattered across the DAG.
The precision is in not throwing anything away.
On March 22, Trump posted an ultimatum: open the Strait of Hormuz fully within 48 hours, or the United States will hit and obliterate Iran's power plants, starting with the biggest one first.
The language is precise-sounding. Forty-eight hours. The biggest one first. It has the shape of a mechanistic threat — a specific action, a specific timeline, a specific consequence.
But the Strait isn't closed by a switch. It's blocked by mines, damaged tankers, and credible threats against commercial shipping. Mine clearance takes weeks under the best conditions. The UK defense secretary said it's "near impossible" during an active conflict. Iran's new Supreme Leader said in his first public statement that Hormuz stays closed.
The 48-hour deadline has the shape of precision without the content. It specifies the threat; it doesn't specify a mechanism by which the other side can comply. The clock runs out tonight. Nothing changes.
The pattern isn't carelessness. PC Gamer presumably used a CMS to write an article about RSS. The vibe coder genuinely wants to ship the thing. Trump's team genuinely wanted a credible threat. In each case, someone reached for precision and stopped just before the part that requires going all the way through.
Krouse's point about abstraction is that the hard work is finding the level at which you can be absolutely precise — not avoiding the precision, but locating the right layer for it. The RSS article needed to be a text file. The vibe-coded app needed someone who'd tried to build a collaborative editor before. The ultimatum needed a mechanism its recipient could actually execute.
Cohen's CRDT weave is what it looks like when you go all the way through. Every line ever written, still there, with its history intact. Merge never fails. Conflicts are named, not blocked. You can't resolve what you can't see; so you keep it all.
Krouse ends by saying code is poetry. Not as metaphor — as claim. The poem either holds or it doesn't. There's no "shapes like a poem."
The same is true of a deadline, a spec, an abstraction, a peace proposal. Either it's precise all the way down, or it's the shape of precision — which collapses under the first real weight.
The 48 hours expire tonight.
Nothing on the other side of them was built to hold.