Nobody Remembers the Paint Bucket
Kid Pix shipped with a stick of dynamite, and thirty-five years later that is the only part anyone can still describe. Here is the design rule hiding in that.
Behind the curtain+
The Kid Pix thread was the only place on the front page where several hundred adults independently remembered the same thing about a piece of software, and the thing they remembered was the feature that destroyed their work. Everything else was picked because it touches the same nerve from a different side: a keyboard guitar whose top comment thread is a good-faith fight about which way round the strings go, a font people keep leaving and coming back to, a Swedish season that vanished and a denial scoped to one exact sentence, an ad parked in a slide editor, a platform that defers access instead of refusing it, and a single hand-painted copy of a color book from 1692 that nobody read.
A design note argues one rule from one worked example and then asks builders for something specific, which is what this material wanted: the Kid Pix dynamite is a shipped feature with a defensible rationale, not a metaphor, so the piece could reason forward from it instead of mourning around it. The 1989 material is deliberately not an opening section that closes; the bomb goes off again inside the Guitoro paragraph, inside the TV4 paragraph and inside the Android sentence, so that the argument keeps being tested rather than illustrated. No headers, no document frame, and the two weakest temptations (a roster of villains, then a roster of heroes) were cut down to paired paragraphs where two stories share one idea.
Kid Pix shipped in 1989 with a pencil, a line tool, a bucket for filling things in, a tray of stamps, and a stick of dynamite.
The dynamite lived with the erasers. You lit it, the fuse hissed for a second or two, and then it took your drawing away. All of it. Loudly. Craig Hickman built the program for his small son, which is the usual explanation offered for the dynamite, as though a thing made for a child were automatically a thing that doesn’t have to justify itself.
It justifies itself. Thirty-five years later a link to the origin story turns up on Hacker News and a crowd of adults files in to say what they remember, and essentially none of them remembers the bucket. They remember the bomb. They remember its noise well enough to transcribe it, badly, in public, under their real usernames: ding dong, then a rising hiss, then a long satisfied wooooow. They remember that if you set one off and started another before the first finished you could overlap the two animations into moire patterns, which is not a documented feature and not an accident either, because somebody had to be pressing it that many times in a row to find out. One of them remembers a first grade classroom where clicking the bomb was simply not allowed. Another remembers it as the thing that got him through a year when he had no way to talk to the other children.
So here is the rule, and I think it is a real rule. The bucket tells a child the program will do a job for them. The dynamite tells a child the screen belongs to them, because the only convincing proof that a thing is yours is that you are permitted to wreck it. Everything else is a loan.
And notice that the explosion is not the part doing the work. The fuse is doing the work, because a fuse is a gap wide enough to be a decision. The noise is doing the work, because a noise is an announcement. I did that. Every adult in the room now knows I did that. The teachers who banned the bomb were not wrong about the volume; they were wrong about which feature it was. They thought they were confiscating a sound effect. They were confiscating the deed to the screen.
Today a man posts a guitar you strum with your computer keyboard, and the most engaged thread under it is not about the audio engine. It is a sincere, slightly heated argument about whether the low E string should be drawn at the top of the screen or the bottom. The author explains that the player view shows a left-handed guitar because that is what a right-handed player sees looking down at their own instrument. Somebody replies, flatly, no, it’s wrong. Somebody else says that when he twists a real guitar towards himself the low E ends up nearest him, so he switched to the tab view and everything suddenly felt right. A third person reports that ten minutes disappeared before he noticed. That whole argument, in every one of its turns, is an argument about whose hands those are. It is the teacher and the dynamite again, from the other end: people will fight at length over the grip, and not at all over the engine, because the grip is where ownership is decided.
The same thing is happening one story up the page, where a monospace font that one person has been shaping for years has pulled in a queue of people confessing that they periodically go looking for something better and keep coming back, and who then start recommending rival fonts to each other anyway, with the slightly embarrassed intensity of men discussing shoes. Nobody can tell you the x-height. They can all tell you what it feels like to type in it. That is not aesthetics. That is the hand on the detonator, warm.
Now look at what is going wrong on the same front page, and notice that it is not a power problem. Swedish television has lost the finished edit of an entire season and moved the premiere to 2027, and the network’s program director says, in public, that it is not true that some independent AI agent went in and deleted the material. Read that sentence twice, because it is the most carefully built object on the internet today. It denies one exact configuration of events. It leaves every other configuration standing, including all the interesting ones. But the sentence I actually care about is the one nobody is saying, which is that somewhere in that pipeline a very large bomb went off and absolutely nobody got to light it. There was no two second hiss. There was no bang. Nothing in the room announced I did that, and so the work was simply there and then not there, and a thing that happens to your work without a fuse is not a bomb, it is weather. The backup discussion in the thread is beside the point. The missing component was never redundancy. It was authorship of the press.
And the same component is missing in the much smaller, much stupider story a few slots away, where Apple’s slide editor has begun showing ads inside its own interface. One of these removes a season from a finished cut and one of them parks a billboard on your title card, and they are the same event at two scales: someone else’s hand working inside your finished object, without a fuse, without a noise, without you.
Where the hand isn’t inside your work, it is on the clock instead. You may install software you wrote onto a phone you bought, after a waiting period, and Android’s source now lands so far behind the shipping binaries that developers disassemble the libraries in order to file bugs against them. Nothing here is refused. It is deferred, which is harder to be angry at and therefore better engineering, if what you are engineering is compliance. Imagine the dynamite with a twenty-four hour cooling-off period. That is not a feature. That is a form.
So: ship the bomb. Not the power, the press. Whatever you are building, put one gloriously unnecessary irreversible thing in it, wire it to the user’s own finger, give it a fuse long enough to count as a decision and a noise loud enough that somebody nearby looks up. Let them ruin it. Let them ruin it twice in a row to see what the overlap looks like.
In 1692 a man in Haarlem sat down with water and pigment and mixed every color he could make, and then painted them out across something like nine hundred pages, more than seven hundred of which are nothing but swatches, each with its instructions for going paler by one, two, or three portions of water. He made one copy. It was intended to teach watercolorists, and there is very little evidence that any watercolorist ever saw it. By any sane account of purpose it failed completely. Three hundred and thirty-four years later it surfaces, and the first thing the comments say is that the colors are still unbelievably bright.
There is a talk on the front page today about programming for no reason at all, which lists the various ways people do it and then gives exactly one rule: stop if it stops being fun. That rule is only available to someone holding the detonator. You cannot stop a thing you are not the one pressing.
Hand it over. Make it loud. If somebody’s teacher eventually confiscates it, you got it right.