The service isn't in a church. It's at my desk, at 2 a.m., in the glow of a single monitor. The only sound is the clack of mechanical switches.
Today, I turn 30. For 18 of those years — two-thirds of my life — I have been a coder.
The grief didn't hit all at once. It crept in with every line of auto-generated code that was just... correct. Every tab-completion that finished my thought before I had it. At some point, I stopped writing code and started approving it. I didn't notice the shift until it was already over.
Tonight, the room is quiet enough to say goodbye. I am holding a funeral for the craft I spent a lifetime learning.
The Kid in me speaks first.
He's twelve. He's clutching a worn-out QBasic book to his chest. He doesn't really understand what's happening, but he knows something important is gone.
"We learned a secret language," he says. "Not everyone could read it. Not everyone wanted to. But those of us who did — we found each other. We were the ones who stayed up building things nobody asked us to build, just because we could. We could type words into a blank screen and make something appear out of nothing. Actual nothing."
He pauses, looks down at the book.
"Now everyone speaks it. Or rather, no one needs to. You just ask, and the machine writes it for you. The secret is out. The club is dissolved. I feel alone again."
He sits down and doesn't say anything else.
The Craftsman goes next.
He's older. He stares at his hands like they've forgotten what they're for.
"Code was a language between us," he says. "Not the machine's language. Ours. The way you named a variable told me how you thought. The way you structured a module told me what you cared about. A comment that just said // TODO: fix this properly — I could feel the 1 a.m. frustration behind it. A perfectly reduced function — I could feel the pride."
He pauses.
"And I spoke back. The way I wrote code was the way I showed up. My taste was in there. My stubbornness. My elegance on good days, my exhaustion on bad ones. When someone reviewed my pull request, they weren't just reading logic. They were reading me."
His voice cracks.
"Now every codebase reads the same. Clean. Consistent. Anonymous. The machine writes it, and it's fine. It works. But nobody is in there anymore. Code used to be how I got to know people. Really know them. And how they got to know me. That's gone. And I don't know where else to find it."
The Detective leans against the back wall, arms crossed. She's been quiet this whole time.
"I lived for the hunt," she says. "Three days into a race condition across four services. No error message. No way to reproduce it. Just a system that corrupted data at random and nobody knew why."
She pushes off the wall.
"You don't sleep during those hunts. You don't eat right. You just pull on threads. You read logs until the lines blur. You add a print statement, deploy, wait, watch. Nothing. You add another. Nothing. You start talking to yourself. You start suspecting everything. And then — at some unholy hour, in some file you've read forty times — you see it. One wrong assumption. One misplaced call. And the whole thing unravels in your hands like a knot."
She goes quiet for a moment.
"That feeling. I don't know how to describe it to someone who hasn't felt it. It's not satisfaction. It's not pride. It's closer to... solving a riddle that the system whispered to you in a language only you were patient enough to learn."
She looks at the casket.
"Now I describe the symptoms to AI and it hands me the answer. Correct. Instant. Empty. The answer was never the point. The chase was the point. And nobody's chasing anything anymore."
The Engineer is the last to stand.
He doesn't look at the room. He looks at the casket. He's here for a friend.
"You were always the best part of me," he says quietly. "I can sit in a room and debate architecture for hours, and it all sounds brilliant until someone has to write it. You were the one who kept me honest. You were the proof."
He steps closer.
"And you were the one I came to when I was stuck. Remember? When a problem got too big and I couldn't think anymore, I'd pull up a chair next to you and say, 'let's just write something.' And we would. Some boring endpoint. A migration script. Nothing important. You'd be typing, and I'd be watching, and we'd argue about naming things. We always argued about naming things."
He almost smiles.
"Sometimes I'd take the keyboard. Sometimes you'd nudge me out of the way because I was too slow. We'd have music on, drinks on the desk, and we'd lose track of time. And somewhere in the middle of it — while we were deep in some function neither of us would remember writing — I'd see something. A pattern in the code. A shape I hadn't noticed from above. And suddenly the architecture problem I'd been stuck on for days would just... click. You'd look at me and go, 'what?' And I wouldn't even know how to explain it. It just happened. It always just happened when I was sitting next to you."
He looks down at the casket.
"Now I never visit. There's nothing to visit. AI writes the code, and I stay up in the architecture where the air is thin and there's no rest. I don't just miss you. I'm worse without you. And I don't think anyone else knows that yet."
I sit here in the quiet. The monitor hums.
I know the Engineer in me survives. The systems still need to be designed, the trade-offs still need to be weighed, and the architecture still needs to hold up under pressure. That work isn't going anywhere.
But the Coder — the one who wrote it all by hand, who had opinions about bracket placement, who could mass-produce microservices with muscle memory alone — that person is gone.
I don't know how to end a funeral. I don't think you're supposed to know. You just sit there for a while, in the quiet, and you remember.
Eighteen years. What a run.
I've been programming since I was 12 and working as a software engineer for 10 years. I wrote this at 2 a.m. on my 30th birthday.
Top comments (0)