The most widely read literature of the last forty years was written by engineers under deadline, in a text field with a character limit, for an audience already furious. Error messages are the only body of writing everyone has read and nobody has been taught to read.
The canon
Abort, Retry, Fail? Guru Meditation Kernel panic Segmentation fault (core dumped) Fatal exception has occurred
Read that as a list and it is bureaucratic. Read it as a stanza and it is apocalyptic. Abort, Retry, Fail? is a genuine MS-DOS prompt, descended from CP/M, and it is a masterpiece of accidental cruelty: three options, two of them verbs you can act on, one of them a state of being. Fail is not a thing the machine is asking you to do. It is a thing it is offering to let you become.
Guru Meditation, the Amiga's name for its crash screen, goes the other way — the machine reaches for the sublime. Something has gone so wrong that the computer has withdrawn into contemplation. The Unix kernel panic is more honest, and funnier for it: the system has not withdrawn, it is screaming. Segmentation fault (core dumped) is the coldest line in the language. Something died. Here are the remains. Good luck.
An error message is a poem with a hostile audience and no time to warm up. That is a harder brief than most of us are working under.
The joke that became a standard
HTTP 418 — I'm a teapot — was defined in RFC 2324, the Hyper Text Coffee Pot Control Protocol, an April Fools' document from 1998. It was never a serious status code, and it has been quietly implemented as an Easter egg ever since, defended by developers who fought off attempts to remove it. A joke that outlived its own occasion and became infrastructure: there is a poetics in that alone.
The haiku that never happened
You have probably seen these:
The Web site you seek can not be located but countless more exist.
Chaos reigns within. Reflect, repent, and reboot. Order shall return.
They circulate as Microsoft Japan's error messages, supposedly shipped in Vista. They were not. Snopes has rated the story false since 2003; the poems are English-language internet folklore, correctly counted at 5-7-5, attached to a company that never used them. Some accounts trace the underlying idea to the NetPositive browser on BeOS, which did display cheerfully strange error text — an origin story that is itself hard to pin down.
We find the debunking more interesting than the claim. Thousands of people encountered these poems and found it entirely plausible that a large software company had answered system failure with seventeen syllables. The legend survives because the wish behind it is real: we would like the machine, at the moment it fails us, to say something worth keeping.
An assignment
Write the error message for a thing that cannot be fixed. Under twelve words. No apology, no exclamation mark, no please. The constraint is the whole exercise: the great error messages are great because someone had to name a catastrophe in the space of a button.
Send them to us. We will print the best ones. Retry.