Honestly I am burned out on public discussion of AI. There are so many hot, low info takes on both sides. All the dumb stuff revolves around this imbecilic notion that AI will take your job.

In that sense Altman and Dario et. al. were extremely successful in their cringeworthy campaign to establish themselves as priests of a new machine god religion. Even the people who don't want it believed them.

The good news is at least this year companies are starting to get a little more thoughtful about why they're paying for AI and what specific business function it serves.

Realities:

1. AI is a tool. You don't replace a job with a tool, just like you don't replace an apple with a sock. It was always an error of classification to think this way.

2. AI is a useful tool. For every CEO who thinks it justifies mass layoffs, there are dozens of people who don't want to admit that it does have a lot of utility. Anyone who isn't figuring out where this tool can make them more productive will have a hard time down the line imho.

3. We can infer from the priors that jobs will continue to be a thing, just like they still were after the inventions of printing presses, cars, power looms, etc. but there will be some pretty massive churn, some roles maybe disappearing entirely, new ones getting created, same goes for skill sets.

4. Businesses will use this churn to the best of their ability to either reduce costs or increase output. That second part is the key the AI haters don't seem to recognize. Thanks to competition, not every business wants to just fire everyone. Yeah, America's financialized and monopolized and less competitive than it used to be, but still, plenty of businesses will repurpose their budgets to produce more and expand.

So in terms of real specific and concrete things I've seen so far.

If you're in customer support that's a pretty rough spot, a well designed RAG system can turn 20 minutes of research into 20 seconds. Customer support budgets flow downstream from actual usage/customer base so if they can do more with less people will get laid off, they don't expand scope, they automate and cut the budget.

If you're a developer, your position's a lot more secure than that, coding agents are pretty incredible but they are simply not at a point where they can think through architectural decisions, and they occasionally go off the rails and trash everything. These things need to be operated and steered. Yes that's 100% the future of the profession and I'm sorry if someone doesn't like that, being a blacksmith who forges metal things by hand is also very niche these days, kind of sad if you loved blacksmithing but it happens. Devs also have to be aware that a PM/product owner can likely do some of their job now and I think any dev whose preference was to avoid thinking about customer or business requirements is going to find his utility is shrinking. A mass shrinking of the profession is unlikely but things will change and the only rational paths forward honestly are to retire or to figure out now how you fit in, it's a career opportunity if you get ahead of the curve even.

Lastly there is a whole other domain now which for lack of a good term I'll refer to as "prompt engineering," it requires some level of systems design thinking, but basically no programming expertise. The best candidate for this work is a person who possesses business process knowledge as well as systems oriented thinking. Maybe these jobs will end up finding a home in the IT department or something. As an economy we're barely recognizing them yet but I see that in engineering we can increasingly implement places for a prompt input, and then hand some workflow/business domain decisions off to someone who understands them better and they just tweak their prompts over time to get a great system. Pretty sure new jobs will be created and formalized around this over time.