Please, for the Love of God, Take My Fucking Job
The AI revolution is coming. Apparently, it got lost on the way.
Everywhere I look, somebody is warning me that artificial intelligence is going to take my job.
Software engineers are doomed. Programmers are obsolete. The machines are coming. The future belongs to AI, and all of us poor bastards who spent decades learning how to build software should start preparing for unemployment.
Please.
For the love of God.
Take my fucking job.
I'm begging you.
I've spent roughly twenty-five years writing software. I've dealt with databases, distributed systems, servers, cloud infrastructure, deployment pipelines, Windows, Linux, and every other technological nightmare humanity has invented to make a computer do something useful.
And now we're supposedly on the verge of replacing me with artificial intelligence.
Fantastic.
Except there's one tiny fucking problem.
I can't get the artificial intelligence to reliably follow a goddamn instruction.
Not a complicated instruction. Not something involving quantum computing, theoretical physics, or the internal architecture of a nuclear submarine.
I asked it to publish a fucking story.
That's it.
I even built the workflow for it.
I created a skill called Note. It captures information and saves it in my private repository.
I created another skill called Journal. It examines a conversation, identifies potential stories, lets me select which ones I want, asks whether I want light editing or full storytelling, and eventually publishes the selected articles when I authorize it.
Two skills.
Two different purposes.
Simple enough that a reasonably competent houseplant should be able to distinguish them.
And for a while, the AI did.
I tested the fucking thing. It worked. I tested it again. Still worked.
Beautiful.
Then one evening I invoked Journal, and the machine apparently decided that storytelling was no longer its primary responsibility.
Suddenly we were discussing private notes, repository destinations, unpublished drafts, publication authorization, skill availability, and some computer automation that I had absolutely no idea was happening.
I wanted an article.
I got an archaeological expedition into my own goddamn workflow.
And the AI kept explaining to me what it thought I meant.
Motherfucker, I wrote the fucking skills.
I know what I meant.
What really kills me is the confidence.
The system doesn't simply say, "I don't understand."
No, it constructs an elaborate explanation of why its behavior makes perfect sense.
Then, when challenged, it constructs another explanation.
Then it contradicts the first explanation.
And eventually, after consuming an unreasonable amount of my evening, it announces that perhaps there was a misunderstanding.
Perhaps?
You think?
Meanwhile, somebody on the internet is publishing another breathtaking prediction about how AI will replace every software engineer by next Tuesday.
I would absolutely love to see it.
Because right now, the machine that's supposedly replacing me needs me to supervise it, debug it, correct its assumptions, inspect its output, explain its own instructions, and occasionally remind it what the fucking assignment was.
That's not job replacement.
That's management.
Worse, it's management of an employee who works at superhuman speed, never sleeps, and occasionally decides to reorganize the entire filing cabinet because somebody asked for a sandwich.
So yes.
AI is coming for my job.
Please hurry.
I'm fifty years old. At this rate, I'll be dead before the thing figures out where to publish my fucking journal.
And when that glorious day finally arrives, I have only one request.
Take my job. Just stop making me do yours, too.