It never was for those doing consulting work, as customers always expected more than plain coding.

Everyone is now a developer (Just don't tell them about software maintenance)

AWS meant that (a lot of) "developers" were needing "Ops" skills

AI hasn't "forced" domain knowledge to be required at all, it's been there as a requirement for a long time (I had several medical projects turn myself and many other good developers away because we didn't have domain knowledge, which was fair because we needed to have some idea of the subtext in the field)

This was true before.

The famous essay "Don't Call Yourself A Programmer" dates from 2011! I thought it was required reading here on HN.

https://www.kalzumeus.com/2011/10/28/dont-call-yourself-a-pr...

Software Development might be dead, but Software Engineering is alive and well.

Anyone seriously interfacing with AI code generation can tell you that understanding how software is composed and architected is, and will continue to be, a requirement to building anything worthwhile. These systems are impressive but we are a far ways away from "Magical Genie Wishes" as a means of creating software.

Just talking about AI isnt enough to ship your bang average products anymore

My experience is this has always been the case. Although I imagine if there were any just a dev jobs they are at risk!

Being "Just a Developer" was never a thing for anyone above Junior level, AI code generation hasn't changed anything about that.

In fact, AI code generation hasn't changed much at all for anyone with a significant amount of experience (outside of business and management expectations) - its just another tool of varying usefulness.

I agree with some parts, at least.

After my recent layoff, I realized I had become too narrow. I knew one language and one subject matter well, and couldn't quickly switch to something else. I was lucky and found an exact fit within a week - but there's no guarantee that will happen again.

Definitely doesn't hurt to know a few languages, a few subjects well. Even if you're not an expert, you can fake it for a bit while you get the details down.

No need to go by some generic rules. Just respond to what's going on around you. Not all companies move the same way in adopting AI. Some do it for PR sake. Highly regulated domains move at snail's space. So wait until you see the change and respond in way that aligns with the change. No hard rules.

I've done "being not only a developer" for some time. It's okay, even fulfilling but sometimes exhausting. Would have liked to take a break at some cushy, technical only position. Damn, should have done this while still possible...

Just move on to something else already, e.g. designing physical products, getting them manufactured, and selling them. Use AI all along the way instead of fighting it. The longer one stays a developer, the worse the salaries will get. It won't be too long before it becomes a minimum wage job.