Vibe Coding, Apparently
I keep seeing developers complain about AI.
Not criticize it.
Criticism is useful.
I mean complain that the job has become too easy.
"I can't believe I get paid this much to vibe code."
Motherfucker.
What exactly is the complaint?
The tools got better?
I have been doing IT for more than twenty years.
Call it twenty-five-ish if you want the full archaeological layer.
During that time everything changed.
Repeatedly.
Languages changed.
Frameworks changed.
Deployment changed.
Servers became virtual machines.
Virtual machines became containers.
Data centers became cloud accounts.
Front ends reinvented themselves every eleven minutes.
Build systems changed.
Source control changed.
The job changed.
That was the job.
I always liked that part.
Then AI showed up and suddenly a surprising number of people in technology discovered a deep emotional attachment to technological stability.
Is AI Going to Take My Job?
Maybe.
Anything is possible.
But I have said this before: I do not think the most likely outcome is that somebody with no engineering experience gets an AI subscription and suddenly replaces twenty-five years of system design, debugging, architecture, operations, and bad decisions survived.
What AI absolutely can do is help an inexperienced person produce an astonishing quantity of bad software very quickly.
Congratulations.
We have invented a faster shovel.
That does not mean the shovel knows where the foundation goes.
The distinction people keep flattening is between:
- generating code;
- and engineering a system.
Those are not the same activity.
I do not manually type every line anymore.
I do not manually write every test.
Sometimes the model gives me three options and I say:
"Use the recommended one."
Yes.
Absolutely.
Scandalous.
Somebody alert the guild.
But I still decide what the system is.
I decide where the boundaries are.
I decide what tradeoffs I care about.
I decide what must be deterministic, what must be observable, what must survive version changes, what needs tests, what can fail, and what failure means.
And when the machine produces something stupid, I still need enough experience to recognize that it is stupid.
1,700 Tests
My game engine has around 1,700 tests now.
I did not lovingly type all 1,700 tests by candlelight while preserving the ancient dignity of the craft.
AI wrote a lot of them.
Fine.
But why do they exist?
Because I kept engineering the fucking thing.
The engine has gone through scenario after scenario.
Systems got separated.
Contracts got tightened.
Edge cases got found.
Behavior got made deterministic.
Things that used to live vaguely in my head became explicit design.
That is the part I did not expect.
AI did not make me design less.
It made me design more.
A lot more.
The boring cost of exploring an architecture dropped low enough that I started exploring architectures constantly.
That may be the biggest change in how I work.
Apparently I Became Lazy
Six months ago I put my portfolio online.
I found at least fifty public projects to put on it.
Fifty.
Since then I have probably built another twenty things I could add.
I have actually lost track.
This is apparently what AI-induced developer laziness looks like:
- more projects;
- more experiments;
- more architecture;
- more tests;
- more platforms;
- more finished ideas;
- more ridiculous side quests.
I am exhausted just looking at my own repositories.
The portfolio itself is behind because instead of updating the portfolio, I built more shit.
And then, naturally, the portfolio became its own reusable component and publishing pipeline.
Because of course it did.
The Tool Is Not the Operator
People love analogies, so here is one.
Cars made transportation easier.
Airplanes made transportation absurdly easier.
Neither one removed the distinction between access and competence.
Giving somebody a car does not make them a good driver.
Giving somebody an airplane certainly does not make them a pilot.
And giving somebody Claude, Codex, ChatGPT, Copilot, Cursor, or whatever arrives next Tuesday does not automatically make them an engineer.
It gives them leverage.
What happens next depends heavily on who is holding the lever.
I Am Having More Fun
That is the part I cannot reconcile with the endless mourning.
I am having more fun.
I can take an idea that would have sat in my notebook for a year and turn it into working software in two weeks.
I can investigate obscure APIs.
I can prototype alternatives.
I can throw away bad approaches without mourning three days of typing.
I can spend more time on the parts I actually enjoy.
Design.
Architecture.
Systems.
Making ridiculous things exist.
Maybe somebody wants the old workflow back.
Fine.
People are allowed to enjoy different things.
But I have been watching technology change for most of my adult life.
This one changed a lot.
Good.
That's why I got into this fucking business.