LLMs mean less devs are needed, not no devs. even after serveral more decades, they'll need steering. I've seen agents stuck chasing one issue, when to me the issue was obvious, but I can see how the model would rule out the obvious easily and move on, but my instinct/experience tells me that's where I need to focus time on. This translates into costly token-waste. Secondly, it isn't simply "quality", the LLM might generate something that's good quality from its perspective, but it simply won't consider things unless it's explicitly told to in excruciating detail, and even then! understanding things from a simian point of view can't be perfected without that simian experience as part of its training. It can come very close but not quite.

Think of it this way, who needs engineering managers, project managers, scrum masters,etc.. if they're employable then surely actual devs that can tell what good architecture is vs bad, good code vs potentially bug code is are also employable.

But the number of devs needed, that demand will obviously decline dramatically. At the same time though, there are other careers that require programming and software dev as part of your skill set. Simply integrating LLM-enabled solutions into real world workflows is a new area that's very young and immature.

Let's not act like we're suddenly in some sort of post-scarcity utopia where all problems are solved by LLMs, where tech can solve problems, there is demand for those who can use technology to do so. However, I see a lot of people attacking the technology and resisting change a lot, and to those I suggest they look up every single technological revolution and see about the fate of such people.