I think the initial job loss from AI will come from having individual workers be more productive and eliminate the need to have larger teams to get the same work done.
I think the initial job loss from AI will come from having individual workers be more productive and eliminate the need to have larger teams to get the same work done.
Eventually, maybe. Right now I see a lot more people wasting time with AI in search of these promised efficiencies. A lot of companies reducing headcount are simply hiding the fact that they are deprioritizing projects or reducing their overall scope because the economy is shit (I know, I know - but it feels worse than reported IMO) and that's the right business cycle thing to do. If you're dramatic and take the DOGE/MAGA approach to management, just fire everyone and the important issues will become obvious where investment is actually needed. It's a headcount 'zero based budget' played out IRL. The truth is, there is a lot of fat to be cut from most large companies and I feel like it's the current business trend to be ruthless with the blade, especially since you have AI as a rose colored scapegoat.
The way I like to describe it is that you can't go from 1 developer to 0 thanks to AI, but you might be able to go from 10 to 9. Although not sure what the exact numbers are.
For cost centers, maybe. If your development team or org is a revenue generator with a backlog, I don't see why the team would be trimmed.
I'll go further than you. Even if the team is a cost center, it may not make sense to reduce the headcount if there's still more work to do. After all, an internal team that just assists other teams in the company without directly creating value suddenly become more productive could in turn make the other teams more productive. Automatically reducing headcount after a productivity increase is like that effect where people drive more dangerously when wearing seatbelts.