Ding ding ding!
AI can absolutely reduce headcount. It already could 2 years ago, when we were just getting started. At the time I worked at a company that did just that, succesfully automating away thousands of jobs which couldn't pre-LLMs. The reason it ""worked"" was because it was outsourced headcount, so there was very limited political incentive to keep them if they were replaceable.
The bigger and older the company, the more ossified the structures are that have a want to keep headcount equal, and ideally grow it. This is by far the biggest cause of all these "failed" AI projects. It's super obvious when you start noticing that for jobs that were being outsourced, or done by temp/contracted workers, those are much more rapidly being replaced. As well as the fact that tech startups are hiring much less than before. Not talking about YC-and-co startups here, those are global exceptions indeed affected a lot by ZIRP and what not. I'm talking about the 99.9% of startups that don't get big VC funds.
A lot of the narrative on HN that it isn't happening and AI is all a scam is IMO out of reasonable fear.
If you're still not convinced, think about it this way. Before LLMs were a thing, if I asked you what the success rate of software projects at non-tech companies was, what would you have said? 90% failure rate? To my knowledge, the numbers are indeed close. And what's the biggest reason? Almost never "this problem cannot be technically solved". You'd probably name other, more common reasons.
Why would this be any different for AI? Why would those same reasons suddenly disappear? They don't. All the politics, all the enterprise salesmen, the lack of understanding of actual needs, the personal KPIs to hit - they're all still there. And the politics are even worse than with trad. enterprise software now that the premise of headcount reduction looms larger than ever.
Trucks in the oil sands can already operate autonomously in controlled mining sites, but wide adoption is happening slowly, waiting for driver turnover and equipment replacement cycles.
... because I gave up on C++ in 2011, after reading Scott Meyers excellent Effective C++. It made me realize I had no desire to use a language that made it so difficult to use it correctly.