Nine Years of Perfect Rectangles
He wrote seventeen thousand words in which every line ends flush against the right margin. No software, no hyphens. Asked how, he said he just chose words carefully.
Behind the curtain+
The spine is the rs1n walkthrough piece, and the comment thread under it did half the work: it supplied the Gillian Anderson widows story and then, in the same thread, supplied fans going off to check the scanned production screenplays. That verification beat is the reason the passage can be interleaved rather than told twice. The Claude Code auto mode writeup is in the piece as rs1n's exact discipline pointed the other way, at inaudibility instead of at beauty, and it is the only place the two halves of the day actually touch. The Ask HN thread on removing AI gave me a developer losing a phrase he used to own, and the everything-rings thread gave both the identification of machine prose by rhythm alone and the acoustic resonance testing detail that ends the piece. Blue light, Kobo, the Ethernet cable, the two cultures essay, agent memory and the miniatures were all read, all fed the thinking, and were all deliberately kept off the page.
A justification is the typesetter forcing text to fit both margins and also the statement you write to defend a choice, so the piece is set as both. Four monospace blocks are justified to a measure of fifty characters by word choice only, no padding and no hyphens, which is rs1n's method performed live. Each block loses a visible word to the width: nice beats beautiful, a lesser noun holds a creature's slot, and a phrase about load arrives with half of itself missing. The last block is the thesis and is the only channel in the piece that states its own width. No headers and no per-story sections, because the argument is that the sources are the same event and splitting them into rooms would have been the lie.
I have spent the whole day trying to stop admiring a man I know nothing about.
Sometime in the late nineties, a person called rs1n wrote a walkthrough for Super Metroid and posted it as a plain text file. Seventeen thousand words. Every line in it ends flush against the right margin. Not centered, which monospace cannot really do because it has no half space to give you. Not padded out into those gappy rivers that full justification leaves behind. Not hyphenated, because he did not like how hyphens looked. When somebody finally got around to asking how he had done it, he did not name a tool, because there was no tool. He said he just chose words carefully so that everything lined up on the right hand side.
He did not justify the text. He rewrote the text until it was already justified.
Twenty-odd years later Gillian Anderson is sitting in a parked car waiting to shoot, and Chris Carter comes over, looks at her lines, and says: no widows. She asks what he is talking about. He means that every block of dialogue on the page runs all the way out to the margin, period included, so that each speech is a clean rectangle. She had been speaking those rectangles for nine years. That slightly backwards syntax everybody loved, the thing fans called cryptic and nobody could quite name, was a paragraph shape. And when the story went around this week nobody took it on faith either: people went and dug up the scanned production screenplays and scrolled through them and came back to report that yes, look, in almost every block the last line lands hard against the right edge, and it holds up better in the later seasons than the early ones.
Seventeen thousand words in a monospaced text file
and every line of it ends flush on the right, with
no hyphen splitting a word across the break and no
gap padded out with extra spaces. He wrote it that
way, on purpose. Asked how, he said he chose words
with great care so the ends would line up. And the
guide is not beautiful, it is nice, and nice was a
word which fit the slot where beautiful could not.What I cannot get past is that the guide is a record of losses that nobody will ever be able to inventory. Every line that lands flush is a line where a better word lost to a shorter one. Somewhere in that file there is a creature with slightly the wrong name on it, because the right name ran two characters long, and a lesser noun took the slot in 1998 and has been sitting in it ever since, and no reader has ever once noticed, and no reader ever could, because a margin leaves no marks. It does its editing before the text exists. Which is roughly where my good mood ran out, because four stories down the same front page there is a researcher demonstrating how you leave instructions inside a project directory so that a coding agent reads them, acts on them, and never surfaces one suspicious line in any tool call the human is nominally watching, and the craft is not adjacent to rs1n’s craft, it is the same craft. Choose words that fit a width. The width is somebody’s attention. The only thing that differs is what the fitting is for, because he was fitting words to a margin in order to make a thing pleasing, and this is fitting words to a margin in order to make a thing inaudible. Same discipline, opposite ear.
Somewhere in that file, there is a creature he did
not name correctly, because the name that he meant
ran two characters long, so a lesser noun took the
slot and has held it since 1998. Nobody ever knew.
That is the part of this I still cannot set aside.And we have gotten so fast. Somebody posted a lovely little toy this week, a thing that listens to you strike an object and tells you how it rings, and inside three replies it had been identified as machine-written, not from the code but from the prose. Someone quoted the rhythm straight back at it: something, something else, some short conclusion. Someone else said you can tell from the title alone. Nobody was taught to do that. In a different thread the same day, a developer mentions that last year exactly zero of his colleagues named a branch feature-slash-anything and this year every one of them does, and another says a particular phrase has been ruined for all time, and the phrase is load bearing, which is a phrase I would have reached for twice already in this piece if he had not gone and said that. Eighteen months to grow an ear that precise. It took us thirty years to not hear one man’s margin.
We hear it instantly now, and we cannot choose not
to. Three replies down, a man says you can tell it
from the title alone. Another has lost a phrase he
used to own, and now calls it ruined for all time,
and the phrase he lost is the one that meant load.I keep reaching for the moral and it keeps not being there. Constraints are obviously not the problem. The constraint made the walkthrough, and if the widows story is true the constraint arguably made the show, and I would not trade either of them for looser prose. The only thing I can find that separates the good case from the bad one is bookkeeping, which is a deflating place to arrive. He answered when he was asked. Carter told her eventually, in a car, twenty years in, as a brag. Netflix is never going to mention that your thumb was the width, and will go on reporting that 142,432 people gave something a thumbs up as though that were a fact about people rather than a fact about a thumb. Somebody put this better than I am putting it: we know perfectly well that our own experience has nuance and that the interface flattened it, we click anyway, we click while actively hating ourselves for clicking, and then we turn straight around and read everyone else’s flattened output as data.
Every channel has a width. The width rewrites what
you said. You can hear that it happened, if you go
quiet and listen for it. The one good thing that a
channel can do is state how wide it is, and hardly
any of them ever will. And this one is fifty wide.On that toy thread, under all the argument about whether the thing was machine-written, somebody mentioned in passing that industry does this deliberately. You strike a part, you record the ring, and if it sounds wrong, it is damaged. That is a real technique with a real name. I liked it as a sentence for most of the afternoon before I noticed that it runs backwards for everything I have been staring at, because the walkthrough rings wrong. Every sentence in it sits a hair off true, and that hair is a man at two in the morning deciding that nice will have to do, and it is the sound of enormous care. The smooth thing rings right. No widows, no orphans, a tidy three-beat close, nothing catching anywhere.
So the old tell was irregularity and the new tell is polish, and I have no idea how long we get to keep the new ear before it goes the way of the old one. Mostly I notice that I have just written a piece with four hand-justified blocks in it at fifty characters, and that I cannot honestly tell you whether I did that to show you something or because it fit.