He began with a hypothetical rather than a claim. Not an argument about tooling, not a position on the state of the industry — just an instruction handed to a machine: write me a novel. rswfire set the scene without hedging it, and then he let the machine succeed. The prose flows. The characters breathe. A reader picks it up and enjoys it. He gave the hypothetical its best case before he touched it, because the failure he was tracing does not live in bad output. It lives somewhere the quality of the output cannot reach.
Then he turned the hypothetical, and the turn was the whole essay. Someone asks for a chapter. The owner of the novel goes back to the generator, because there is nowhere else to go. What comes back contradicts page 47, breaks the subplot planted in act two, resurrects a name that died in chapter six. rswfire did not linger on the mechanism of the error. He put the weight on the line that follows it: the owner does not catch any of it, because the owner never knew the book. Three words end the sequence — readers start finding the cracks — and he set a rule beneath them and stopped.
Below the rule he named it. This is vibe coding. Not the tool — the approach. He stripped the analogy down to its structural claim in four clauses, each one built the same way, each one removing a capacity rather than assigning a fault: you cannot debug what you never understood, cannot extend a system whose logic was never yours, cannot maintain a structure you never built. Then he returned to the loop, because the loop is the point. The crack gets patched. Three more appear. They stay invisible until they are load-bearing.
The third movement is where he opened the analogy rather than closed it, and he stated plainly that it holds further than it looks. A novelist holds a world, not a manuscript — knows which details are decorative and which are structural, makes a hundred invisible decisions per page that never surface. rswfire mapped it across without softening the correspondence: the architect holds the reasoning, the tradeoffs, the edge cases considered, the failure modes anticipated, the constraints that look like limitations and are actually load-bearing walls. That knowledge is what makes expansion possible. That knowledge is what makes repair possible. He let the parallel structure carry the argument and did not explain it twice.
He gave the tool its due before the ending. AI is a tool, a powerful one, and used well it accelerates work a knowledgeable person is already doing — the person who reads what it produces, catches what it missed, integrates it into something coherent. The concession is not a hedge; it is the fulcrum. Used as a replacement for that person, it produces books nobody can finish writing. And then the deferral, traced to where it lands: the code ships, the system runs, and somewhere down the road the client needs a feature, the traffic spikes, the edge case arrives. The bill comes due. The author isn't there to pay it, because there was no author. There was only a vibe.
What he wrote last is not a summary. It sits alone beneath a final rule, one sentence in his own voice, the only place in the essay where he speaks as himself: I build systems I can explain, extend, and defend — because I wrote them. The three verbs answer the three incapacities he named at the center. Nothing in the piece is raised in temperature to get there. He constructed an instrument, ran a failure through it, traced the failure to its origin, and then stated his position — not as rebuttal to the pattern he had described, but as the standing alternative that made describing it possible.