598 karma · joined January 24, 2026
Harsh take: nobody's stopping you from doing that. You can dust off an old computer right now and write software for it. All of that joy still exists. It's just that nobody's going to pay you for it and it's no longer mainstream relevant - the world's moved on from those times, in many cases for good reasons.
So I think what the person really wants is to have their cake and eat it too. They want to be mainstream relevant and employable... whilst having fun.
That's a luxury. More specifically it's a first world luxury. Most people don't get to have that. True, many programmers did get to have it for a time - but that doesn't mean we're entitled to it forever - not unless it's somehow directly tied to producing valuable results.
But you know it's strange to me that programmers lose sight of this. I became a programmer because I saw Wolfenstein 3D on a 386, and was inspired by there being a "world in the box". I wanted to make worlds too. That's an important distinction: I didn't become a programmer because I wanted to write code, I became a programmer because I wanted to create worlds. The programming is a means to an end, it's not the end unto itself - at least I never looked at it that way. And that's in spite of the fact that I genuinely enjoy programming in and of itself. But I still value the outcome more.
And in fact I actually went through a related transition some years ago on a personal level, when I shifted from always trying to write game engines from the ground up to being willing to use engines like Unity or Unreal. It felt like a betrayal - I no longer had a deep understanding of every layer, I could no longer bespoke craft everything to my personal whims. But you know what? It was absolutely the right choice because it put me on track to actually finishing the games I was working on, which was the entire point of the exercise in the first place.
So I don't bemoan or regret it for a second.
Anyway hope that didn't sound too blunt - it's just my way of speaking - I can sympathize with the author but I just think it's on the self-indulgent side.
I've been playing Kingdom Come 2 of late, and I find it's natural to just kind of take the world they've created for granted - just like we do the real world. But when you actually stop and look you have to consider that every one of the finely crafted details was built by someone's sweat and tears, be it artists, programmers, or designers at edit time.
No wonder it's an industry of crunch, the work involved can be uniquely daunting.
Various possibilities I suppose - I could just be overly skeptical, or failures might be kept on the down low, or perhaps most likely: many companies haven't actually reached the point where the hidden tech debt of using these things comes full circle.
Having been through it, what's your current impression of the success stories when you come across them?
To me the claim of the article was silly on the surface of it, silly enough that I was surprised that folks consider it worthy of discussion.
Is there just a large number of upvoters here without even a basic understanding of the topic at hand? Or is there some other explanation beyond that?
So I'm guessing they just rise because they spark a debate?
I don't see agentic programming coming to take my lunch any time soon.
What I do see it threatening is repetitive quasi carbon copy development work of the kind you've mentioned - like building web applications.
Nothing wrong with using these tools to deal with that, but I do think that a lot of the folks from those domains lack experience with heavier work, and falsely extrapolate the impact it's having within their domain to be applicable across the board.
Anyway, this stuff makes me think of what it would be like if you had Tolkein around today using AI to assist him in his writing.
'Claude, generate me a paragraph describing Frodo and Sam having an argument over the trustworthiness of Gollum. Frodo should be defending Gollum and Sam should be on his side.'
'Revise that so that Sam is Harsher and Frodo more stubborn.'
Sooner or later I look at that and think he'd be better off just writing the damned book instead of wasting so much time writing prompts.
But there's still a lot of programming out there which requires originality.
Speaking personally, I never was nor ever will be too interested in the former variety.
Using the scarf example - nobody's paying you to knit it. Knitting it probably won't put food on your table. Maybe for tribal humans that kind of thing did, hence the psychological reward wiring, but not now.
Here's a reality: we do all become obsolete. It's called aging. I don't know how exactly to fit that into that puzzle, but my brain told me it's a relevant reference point, somehow.
A hiring company just wants you to make the thing with an optimal balance between quality and efficiency.
As I see it, one has a few options. A common one is just hoping everything will be okay. Often that turns out to be the case.
Another one is to proactively 'adapt or die'. Master the new way of making the thing even if it tastes bitter. Harder to do with age, but in some sense the obvious choice if you want to be competitive.
Speaking of, I think we often forget that - the world is one big competition for resources and survival. Happiness is a luxury, but we've converted it into a requirement.
I'm not saying I like any of this - I want to be secure for life following the same old patterns I've already learned as well.
But I consider that thought a comforting fantasy to be eyed with suspicion.
That said, thankfully, AI is still pretty good at enshittifying things, so I have a suspicion that one may not need to always adapt that enormously. I work with a lot of legacy software, and have seen that a lot of companies are full of old school tech debt for which hands on programming is still a must have.
Claude code or what have you is a little limited when you're writing code for obscure software packages which nobody knows the name of anymore, but on which some companies still depend for their core business logic.
Will it all dry up eventually? Sure. But slower than we expect methinks.
I work on game engines which do some pretty heavy lifting, and I'd be loath to let these agents write the code for me.
They'd simply screw too much of it up and create a mess that I'm going to have to go through by hand later anyway, not just to ensure correctness but also performance.
I want to know what the code is doing, I want control over the fine details, and I want to have as much of the codebase within my mental understanding as possible.
Not saying they're not useful - obviously they are - just that something smells fishy about the success stories.
As for critical analysis - I don't see why it can't be done for games as for any other artform - at the end of the day all such analysis, including of more passive artforms, really boils down to 'did you enjoy it, and are others likely to enjoy it as well?'.