Here are few anecdotes:
1. I've a friend who owns a PT (physical therapy) business. He's not even a tech guy, but uses claude to manage most of the business aspects, and he has told me repeatedly that he would've to spend thousands of dollars to get things done, and instead he pays 250 per year.
2. Another friend is smart, and is a jack-of-all-trades type in the software/hardware/firmware business. He is solo bootstrapping by doing all the things from pcb to webapp. He doesn't see hiring anyone for the niche business.
3. A 65 year old friend of mine who never in any tech career was able to build website for his side business (that website looks really good btw) and he now talks about json and ocr.
You are the one who is out of touch with reality.
I've got a friend in this situation too. He's going to hit a limit of what he can do with agents. And whatever agents can't do, his business can't do. We are going to find the shape of that soon.
Normally hitting a limit is where you would hire someone, but building organizations with heavy agent use is hard. AI is very very good at shifting work onto other people and business units; that's what all the complaining about review (and not just code review) is about. None of that responsibility shifting happens in a solo setup.
Sounds like your friend has learned quite a bit!
My impression of AI since the first ChatGPT has been that the best use-case for it is learning and research, and even with all the improvements in model capability, I still believe this. The "winners" of AI are going to be people who like learning.
(I also think that knowledge is entirely distinct from, and in some cases opposed to, skill development—a knowledgeable, low-skill person is the kind that will do a good job very slowly. I think AI does devalue skill, but I think the elevation of knowledge and devaluation of skill has been the effect and trajectory of all technological development.)
I'm building a mobile app using flutter. It's got to work on iOS and android. I can promise you, if I did not have years of experience, and I did not follow a regimented, checkpointed interaction flow with my agent, this code base would have turned to shit within a day. I've had to draw on my experience to define the architecture, correct missteps, prevent just wild flailing, and just generally keep things on the rails.
Your example 2 is the closest match, where someone with experience is driving the result carefully.
In other words, the verdict is still out on whether we'll see a decrease in jobs in the long run or not. Personally, I'm not very optimistic but, as I tried to illustrate above, I might very well be (and certainly hope to be) wrong.
there is massive lose in revenue for a business and or infrastructure that people rely on goes down
if you’re working anything in this way, no one is just trusting a clanker. some thought leader might say the world is trusting an AI, but it’s not true. every company internally that is more than 2 people isn't trusting a bot, and it's well understand that it's a horrible idea (even by regular bullish AI business heads)
so yes, I have the bot help me write a basic website for me, and it can one shot the typescript express app-layer boilerplate for me, but if you’re serving even the most basic app at scale with consequences, the bot isn't mitigating the concerns and engineering decisions that go into this work.
a concrete real world example: literally msft outlook went down a week ago. it was out for god knows how many actual hours. it still might be partly down tbh. this is technology that is “solved” and is dumb simple in terms of complexity. their product was out for 48+ hours. and the status messages shared publicly by the engineering team did not only convey incompetence, but to paraphrase, the message they sent out was along the lines of, “We think we found the source of the problem, but unsure, the problem might be larger”
how much you want to bet they had a team of 30+ engs running around with claude asking the equivalent of, “please fix outage, no mistakes”
I’m still not convinced the outage is fully recovered because I still get errors.
point is, yes there isn’t a giant 100 football field wide moat between regular people and programming anymore. smart people can do basic stuff and less inclined people can build a static website now. if you’re worried about that, go study more and you'll learn the depths of this field go WAY beyond typing code
EDIT: typos
The implication is far reaching. Lots of non-tech businesses which relied on expert help can now pareto slice it and hire experts on need basis unlike before. Saving money and increasing profits can be a big motivator to own many of those tasks too. Lots of people who were cosplaying as experts on non-tech people will have less and less opportunities.
Previously, being a knowledge worker could get you far, now the knowledge worker has to level up, and if opportunities are limited how could it happen? Even then, more experts (practice, not theory) is not a given, considering the bell curve effect.