Such a correction was always going to happen. Coders always were the blue-collar workers of the 21st century, and capital ruthlessly optimises for profit. Where you once needed thousands of workers to run an assembly line, you now have dozens; where you once needed hundreds of programmers to run a big SaaS, you will now have a handful. It was always inevitable.
That doesn't mean we're all dead or anything - factory workers still exist, developer jobs will still exist. They'll just be far fewer than they used to be.
> They'll just be far fewer than they used to be.
I do tend to agree. Though at the current pace of change I don't know if we can take it for granted.
As a recent example, I was on a chat with the two most experienced technical people in our company and the original developer of a feature trying to work out why we were getting a null pointer exception in a very specific case. Of course we had a fix, just a guard against the null pointer, but I'm always uncomfortable with not knowing the underlying cause.
I kept digging while someone promoted the fix. Eventually ruling out two of our original theories as to why it happened. Until eventually someone just asked Cursor which spit out a theory which matched the symptoms perfectly and which we quickly reproduced locally.
I still think we'll need some kind of human who lives in that wide space between the 95% of the population who couldn't get Excel to sum a list of numbers and the machines but the industry will be unrecognisable.