[waboremo]

In a way, people who are concerned about skills atrophying are repeating the cycle of previous generations, shaking their fist at higher level programming languages or drawing digital images. How dare you not keep the skills of those who came before you! Time will not be so kind to this view.

Some skills will atrophy, as article mentions we don't really care about road navigation anymore. But this is not a bad thing, we can focus our concerns elsewhere. Do you care exactly how your home is heated? Do you know how to maintain every part of your car? Do you spend every weekend keeping your skill on sewing up to date? Some of you might do all of these, but the point is we have let so many skills become things relegated to experts/tech that once used to be common.

It's this relegation that has allowed experts to become even deeper experts in their niche. So I don't worry about skills atrophying at all. There will always be a new crop of nerds (affectionately) to obsess over whatever niche can exist.

[mrbombastic]

Its not a bad thing until its a bad thing. There are certainly computer related tasks I am happy to relegate to AI, my concern is that we are already bad at maintaining software made by humans. If old school software engineering becomes an arcane art as everyone becomes prompt engineers and software starts to explode in complexity we better hope AI learns to maintain it too.

[EarthLaunch]

Maybe it'll be like hard goods; a blender you buy today is made of moulded plastic and lasts 5 years, instead of being metal and made to last 20 years. For 1% of the price.

[nonethewiser]

That is an excellent, albeit concerning analogy.

[waboremo]

Funny you mention old school software engineering, because it has become an arcane art! We do not feed punch cards into our computers anymore. Should also mention I don't believe "prompt engineer" will be a serious long term role, that task will just be incorporated into everyone's roles instead.

IMO maintaining software will become easier, so much of what we do today with maintenance is really just tedious. It's tedious to keep packages updated, to write documentation every update, to keep the community informed on what's going to happen in the next. It's tedious to rewrite the exact same functionality but in a modern language. List goes on, so much tedious busywork. What if these things were handled for core maintainers, so they can allocate funds to more complex problems?

[nonethewiser]

> In a way, people who are concerned about skills atrophying are repeating the cycle of previous generations, shaking their fist at higher level programming languages or drawing digital images.

Maybe some.

But I resonate with the title because I noticed I started leaning on ChatGPT to avoid having to think through things. I found myself tweaking ChatGPT prompts and hoping for a better response when the previous one wasn’t good enough. Often a better response is not found, then I have to struggle to start thinking for myself.

Over time that leads to less repetition thinking through problems and more difficultly thinking through problems when you can’t use ChatGPT. Is that a good trade off?

[chupaolo]

Exactly