Yes, this is the obvious problem.

We've been through cycles like this before. Back in the day, Dreamweaver was going to put every web developer out of a job. More recently, Squarespace was going to do something similar. However, as soon as you step out of the well-trodden path, you're encountering tougher to debug issue, or you want some customization that the tools aren't aware of or designed to handle, and now you're hiring or paying a specialist again.

> We've been through cycles like this before. Back in the day, Dreamweaver was going to put every web developer out of a job [...]

I get what you're saying. This is why I was also skeptical, initially. But consider this: this time, it's qualitatively different, and more importantly, companies seem to believe so, which has real impact on our jobs.

Dreamweaver never threatened my job. Not once. Neither did Squarespace. I'm sure they did threatened some jobs, but ultimately they simply didn't replace the mind and hands guiding them, and in fact, they never aimed at this. "No code" tools were similarly misguided for a lot of real use case. However, this time, AI seems to be making real progress towards this, and is becoming a real threat to jobs.

The argument of "but when calculators/writing/$SOME_OTHER_TECH was introduced..." don't fly with me. $OLD_TECH is not necessarily analogous to new tech, or AI in particular.

What if this time it's different?