The Moon Lander's Glitch: On the Writer's Vocation in an Age of Perfect Machines

A reader writes in with a question that is, I suspect, on many minds, though few have the courage to articulate it so plainly: If a machine can write a coherent article, a passable poem, or a serviceable synopsis, then what exactly am I for? What is the purpose of my struggle, my slow-dripping craft? It’s a chilling thought, isn’t it? One that can silence the click of the keyboard as effectively as a power cut.

The easiest answer, of course, is defiance: to declare that the machine’s work lacks soul, that it is sterile, derivative, that it can only remix what already exists. But this feels increasingly like a hollow boast, a whistling past the graveyard of our own insecurities. The output is often seamless, polished, and factually dense. It doesn’t make glaring errors of grammar. So, if our only defence is an unprovable claim on ‘soul’, we may find ourselves on shaky ground.

I’ve been thinking about this lately through an unexpected lens: the first moon landing. The Apollo 11 lunar module, the Eagle, was a masterpiece of engineering, a machine of breathtaking precision. Yet, as it descended toward the Sea of Tranquility, its computer began to sound alarm codes. It was overloaded, trying to do too much at once. In the most high-stakes moment imaginable, this perfect machine glitched. The NASA flight controller in Houston assessed the situation in seconds and gave the now-famous command: “We’re go on that alarm.” He understood that the machine’s perceived error was not fatal; it was a distraction from the primary goal. The astronauts, trusting that human judgment, landed safely.

This, I believe, is the writer’s irreducible territory: not the flawless execution of a pre-programmed task, but the judgment in the face of the glitch. A large language model is trained on the entirety of the text it has consumed. It knows the well-trodden path. But it doesn’t know when to ignore an alarm, when a rule of thumb should be broken for the sake of a better rhythm, or when a cliché, used just so, can be resurrected into something heartbreaking. It cannot make a meaningful mistake.

Your struggle, your slow-dripping craft, is the human consciousness in the loop. It is your ability to decide that the story should take a left turn into the dark alley, even though every structural guideline says to keep it in the sun. It is your willingness to write a sentence that is technically ‘wrong’ but perfectly, achingly right for the moment. It is your vocation to bring the context that the machine lacks: the memory of a specific smell of rain, the weight of a particular silence, the emotional truth that resides not in data but in the lived, flawed experience of a single life.

The perfect machine will generate a thousand competent descriptions of love. Your purpose is to write the one that stings with the memory of a love you actually lost. The machine’s work is a map of a place, accurate and detailed. Your work is the account of walking through that place with a stone in your shoe, the sky threatening rain, and a forgotten song stuck in your head. The imperfection is the point. The glitch is the signal. The struggle is not a sign of your obsolescence; it is the very proof of your necessity. Your purpose is not to be the perfect machine, but to be the hand on the throttle, trusting your own judgment to land the thing, alarms blaring, exactly where it needs to be.

Notes & further reading

A few pages I came back to while writing this: