Comment by dingaling
15 hours ago
> resistance to change generally
Nah, software engineers were always butterflies fluttering from one language or framework to the Next Hot Thing. Change was part of the job, if you didn't keep up you fell behind and atrophied.
Resistance to AI is, I think, more because it is seen as an existential threat, or because it's something whose ultimate long-term outcome is still undefined. It's going to be either a benefit or a hazard, and we don't yet know whether we'll need Bladerunners to rein it in.
Resistance to AI is because it doesn't work. It has nothing to do with job security. It's a tech with nothing but hype, no substance at all.
I think I can offer an alternate explanation and it jives with your first point.
When I use AI to completely write code for me (not using it as a powerful auto complete), it's not fun. I don't learn anything. It takes everything I love about software development and makes it just like any other job.
I'm also never happy with the result and, when I go back to make it work the way I want it to, I have to learn a new code base that isn't built the way I would have. If that happens to a project I'm working on as a hobby, I find it incredibly unmotivating.
It turns my intellectual pursuit into an assembly line and I hate that.