A part of the puzzle that rarely gets discussed is something that predated LLMs entirely-- "software engineering" and "programming" have been conflated for a long time now and there's a huge gamut of roles out there.

The practice of writing code, or programming, in recent years has really fallen into two buckets:

The vast majority of folks are given a task, they write code to complete that task, and the task completion then counts towards some objective (eg; a new feature, product or fixing a bug). Perjoratively, they've been known as "ticket takers".

A much smaller group have instead worked in the other direction-- identifying where improvements can be made to a product, piece of infrastructure, or pain point and transformed that into tasks that can then be solved via code.

How much of a role you play in that strategy and formulation has been the real differentiator. Not so much what you know. While these are correlated, they're very different.

At a high level, it's been the difference between "developer" and "engineer" but the reality is the titles have become somewhat meaningless in recent years where many "engineers" are just doing the same CRUD tasks over and over.

The reason this matters is that at some point, you can only abstract so far... the requirements for what to build have to come from somewhere. At the most extreme case, there's only the CEO and a company that's nothing but AI agents. In the least extreme case (today) each line worker could manage 1 or more LLMs/agents.

It's not entirely clear to me or frankly a large portion of those in the industry that we're suddenly on pace for one outcome vs another. But I do think that software isn't particularly unique here other than it was an initial starting point for LLMs to deliver value. All white collar work is at risk including CEOs.

And if that happens it would be outlandish to think a utopia emerges... the opposite is far more likely.