We are gathered here to bury the geek, and the geek will not stop interrupting the service. He is in the third row, taking notes. He has read the eulogy — an AI wrote it, and he has opinions — and he has opened a ticket: the coffin lid closes with a visible flicker. I come to bury him, not to praise him, and I cannot get the lid shut, because the deceased keeps sitting up to code-review his own funeral.

And the principle was absolute: never do by hand what you can automate, and never, ever make an exception.

Who killed him? Nobody with a name. The cause of death was a kind of seppuku — a death by professional honour. The geek belonged to the one trade in history that built the instrument of its own end on purpose. And the principle was absolute: never do by hand what you can automate, and never, ever make an exception. He automated the travel agent and the typesetter, and mourned neither, because the hand on the shovel was always his. Then the ethos came round to his own desk, and he did not flinch. An exception would have been unprofessional.

They have buried him before, of course. COBOL was going to finish him; he still runs the world's payroll from inside a mainframe nobody is allowed to switch off. No-code was going to finish him; it produced apps that promptly needed a geek to explain why they didn't work. Twice he climbed out of the box to correct the death certificate.

Here I ought to put down the shovel and look at my own hands. I have a new start-up, nouplica.com, and my team delivers in a day what used to take weeks, sometimes months, at a fraction of the cost. It does not need the same mistake explained for the umpteenth time. It does not need me to write test cases, or tickets to report the bug again, or a QA department squinting at every browser, resolution and device anyone ever imagined. So I am one of the pallbearers at the burial I am narrating, and the suit I arrived in is also black.

Every inquest wants a suspect, and the cheap seats have found theirs, with a one-word charge: AI produces slop. It is the sound of a man who wakes to find a bulldozer in his tomato patch, a crew he never hired putting in a swimming pool, and a stranger waving cheerfully from the deep end — and who chooses to complain that the hole was not dug by hand. "Slop" is not an argument. It is the last cry of arrogance of the desperate, shouted at full volume in the hope of stemming the thing already coming up the drive.

Cartoon of a man in a bathrobe with a shovel scowling at the swimming pool a crew has dug in his tomato patch, while a stranger waves cheerfully from the deep end.

The better evidence is the confessions. I keep running into videos of geeks recounting their experiences with AI, and the arc is always the same: curiosity, a long pause, then the quiet admission that they cannot compete, not even close. Some have thrown in the towel on camera, in good light; the lighting alone would get them hired, if anyone were hiring. The layoffs arrive daily, and the hiring freezes have turned the careers pages into a museum: plenty to look at, strictly no touching.

Whether that is a fortress or palliative care I honestly cannot tell you, and anyone who claims they can is selling something.

And yet the body declines to be entirely dead. Replace the geek, and the cheerful replacement ships code with holes in it, so the CTO keeps him on, the way you keep the one man who knows which wire not to cut. Whether that is a fortress or palliative care I honestly cannot tell you, and anyone who claims they can is selling something.

What I can tell you is who is smiling. For as long as there have been ideas, the person who had one stood at the geek's door with a notebook and a hopeful face, waiting to learn whether today the thing could be done. It generally could not: it was not in the sprint, or it was the wrong ticket, delivered with a sigh so heavy the idea went home and lay down. The geek's disposition, usually foul, was the weather under which every business lived, and the sulk was a line item. The power has changed hands. It now sits with whoever has a good idea and the stomach to build it.

So the service stays open, the lid will not shut, and the deceased goes on taking notes. I have no verdict on whether he stays dead. As to who killed him, I will say only this: he did. He automated everyone else and then, on principle, would not spare himself — leaving unit tests in his own coffin in case someone needed to reopen it. The rest of us are still laughing. We are only laughing a chapter or two ahead of our own.