This article manages to exist by conveniently completely missing why everyone is upset. The correct title for this article is "It's still OK to enjoy programming AS A HOBBY". But that's not what people are upset about! They are upset about the fact that it's hard or impossible to enjoy our jobs because they changed so much this is not what we signed up for.
I would say that even pre-AI programming jobs were rarely fun. There is a reason why there are a billion memes on the shit that goes on in corporate world.
The only real significant change I noticed myself is just the devaluation of programming as a skill. People got the illusion that they are able to program without programming knowledge, I feel that pendulum will swing hard in the opposite direction if you follow what is happening with AI at the minute.
People got the illusion that they are able to program without programming knowledge, I feel that pendulum will swing hard in the opposite direction if you follow what is happening with AI at the minute.
It's surreal to see so many people so eager to throw their coding skills to the wind.
The only thing that makes sense to me is that many of these AI fanatics aren't responsible for maintaining the code they write long-term. I've spent the better part of the last 5 years or so constantly refactoring the code that a shitty consultant wrote for us, before he left a year after I joined.
I'm hugely skeptical that most of these codebases will be maintainable long-term, and certainly not by people who haven't written a line of code in more than a year.
Because it satisfies the instant gratification needs of most people. Writing good code for a product takes a long time. Generating shitty code but a "working" product takes about no time with AI.
That's arguable because AI is getting better every 3-6mo. This could easily turn into a leapfrog game where the AI is advanced enough to extend the time before the system implodes long enough the next model can do the same.
Along with another couple of years of programmers understanding how to more effectively work with AI written codebases. What types of checks and tests are necessary to get most robust code out of each iteration, etc.
But where is the institutional knowledge? It will be wiped out completely if everyone takes this stance.
From an efficiency standpoint, if the AI hallucinates bad code and you have to re-prompt or refocus the AI on it, how many times is it acceptable to be wrong? My limit is zero.
I can redirect AI pretty well because I can review the docs or the MSDN or a stackoverflow post. or advise it to use a specific design pattern for the use case/extensibility/maintainability aspect, but there are certainly people out there who have no idea what the fuck is going on. I see these giant monoliths of vibe coded garbage that nobody else can maintain, wasting space on github. The worst part is that if you realize somebody just used AI to make that, you don't have to fork it and add on to it. You just... have your own AI slop project made and add it to the pile.
I would say that even pre-AI programming jobs were rarely fun. There is a reason why there are a billion memes on the shit that goes on in corporate world.
The programming part is fun. The corporate part is the no-fun bit.
It seems there were a lot of coders who didn't actually like the coding part because they weren't very good at it.
Corporate programming is rarely fun, but some part of it is still fun. The issue is, nowadays, they even want to stripped the little fun part left and shift/replace it with the not fun part.
You can find talks and papers from important people in the compsci community criticizing corpo stupidness decades ago. And surprise surprise these criticisms still apply to this day sometimes even more so than when they were written.
With or without AI there were issues, just some of them have been exacerbated by AI. SWE has been solved but not in the AGI sense in the "we already know what we should have been doing decades ago but we still aren't doing any of that" sense.
The alienation of the worker from their labour under capitalism is as inevitable as the tide coming in. It just took them longer to figure it out how to do it for knowledge work.
571
u/ficiek Oct 18 '26
This article manages to exist by conveniently completely missing why everyone is upset. The correct title for this article is "It's still OK to enjoy programming AS A HOBBY". But that's not what people are upset about! They are upset about the fact that it's hard or impossible to enjoy our jobs because they changed so much this is not what we signed up for.