I am just having a hard time with all this AI stuff. The other day I got some feedback on one of the products I own. It was a small tweak to an anchor tag to add a title and change the color for just that element. I made the change in the web inspector, showed it to the user, they said yeah that’s good. I walked over to one of my engineers and asked “can you make this change and get it in dev, I just pinged it to you”. No shit they turned around and pasted what I gave them into copilot with claude and asked the agent to do it. Well it actually didn’t do it exactly the way the customer wanted, so it actually took 2 tries with claude. Incredible.
What is happening to jobs? Separating AI hype from reality
221–230 of 412 posts
Re: What is happening to jobs? Separating AI hype from reality
#222Lol figure 3 shows copilot as being the highest task time savings when in my experience it is the most garbage.
that's why companies are pushing those tools. the usage volume makes them look good on frivolous reports like these.
Re: What is happening to jobs? Separating AI hype from reality
#223there seems to be a problem by 'a.i' labs conflating tasks & jobs.
'a.i' or to be more precise are really good at some tasks. but a job is a set of tasks. jobs are not created - only discovered. that's what the a.i labs miss. hence we see that 'a.i' is not having an impact on jobs.
I wrote a bit about it here - https://news.ycombinator.com/item?id=49048723
Re: What is happening to jobs? Separating AI hype from reality
#224Big caveat to the productivity claim is that it’s concentrated in lesser experienced engineers and vanishes or goes negative with highly experienced engineers. This intuitively makes sense and generally agrees with my experience. LLMs move your baseline towards the mean. If you are below average it improves and if you are above it hinders. But also in my experience, my memory retention of the work done with an LLM is…
> My tinfoil hat says that this is what tech CEOs want. They want workers that are low skilled and can be paid less. I think it's useful to divide companies doing software development, as well as specific jobs within a company, into two groups: 1) Companies where software is the product - where what you are working on is directly what is making the company money, and differentiating what they sell from what other com…
this is useful and thx for that, but there are more layers and variations. In some companies, marketing CxO has the budgets and therefore the power, while minions execute the vision. In other companies, there are capital assets, physical assets and historical non-public relationships.. In those companies, the security of control, and the power of those that do the control, guide the boardroom. Software is involved in basically all of these, but common goods software from a vendor plays a large role. Just these examples from imagination lead to many permutations of "how software devs are treated in the company"
Re: What is happening to jobs? Separating AI hype from reality
#225I find that productivity follows a Pareto distribution (80:20 rule) and that AI is a sharper tool in that it enables the already productive to be proportionally more productive and this effect increases as the intelligence of AI increases. So 80:20 becomes a 90:10, 95:5, 99:1 etc. I also think that corporate bureaucratic change is laggy so change there will still be rather slow. I think where change will be rapid is…
> so there will be a displacement of medium to large companies by much smaller ones.
There are so many regulations EE companies follow and offer that no startup owner or worker could ever deal with. The moment your company shifts to that sort of work, you're automatically not anymore a startup (by definition).
Only if you get super smart robots that can manage a lot of bureaucracy etc. Starting from multicloud/region deployments, local regulations, accounting, taxes, laws, etc. Which is what companies like SAP (but not only them) do basically.
But if that happens we are all in a situation that we don't need companies anymore (the way we know them).
Re: What is happening to jobs? Separating AI hype from reality
#226Earlier quoted context omitted.
Anecdotally, I (along with the rest of my team) got laid off from a big tech company at the end of January. The stated reason was "AI", although I think as we all know the real reason was "we overhired in 2022". I managed to get a job by April without putting in a lot of work, though (mostly just listened to recruiters until something hit my fancy). My work experience is good, but I don't know if it's so good that I…
It's so early game, is the real problem. My experience so far, has been that it's barely a junior dev. I've met so many in my career that think reading stackoverflow, or watching a youtube video mysteriously makes them an expert. AI reminds me of this sort. Well anyone can use (prior to AI) a simple linter and learning to code isn't that big a deal. It's learning the pitfalls, the traps, that's the issue. And so far…
> My experience so far, has been that it's barely a junior dev.
At least on greenfield projects, Fable is more like having an endless succession of fly-by senior devs who lock themselves in an office for a week, and who come back with very reasonable code that I then need to maintain somehow.
For longer-term maintenance, I am actually slowly warming to Sonnet 4.5-era models (so October 2025, right before the Opus revolution). They need to be given clear instructions and watched carefully. But since they force a human to stay in the loop, you don't have the institutional knowledge loss I see in some Opus projects, or the code that was one-shot with no human interaction at all that's a constant temptation in Fable projects.
And yeah, the bit rot is painfully real once the humans step back too far. I've been dealing with a compelling prototype that someone built, and that stakeholders love (for good reasons). But it had to be put on a tech debt repayment plan for a couple of months.
Re: What is happening to jobs? Separating AI hype from reality
#227A challenge with this kind of study is that coding agents (Claude Code, OpenAI Codex) only started working really well in late November, which for most people meant early January due to the December break. General agents (OpenClaw, Anthropic Copilot, ChatGPT "Work") started working even later than that. This category of software may have a much more meaningful impact on work than the mostly-chat systems we were using…
Anecdotally, I (along with the rest of my team) got laid off from a big tech company at the end of January. The stated reason was "AI", although I think as we all know the real reason was "we overhired in 2022". I managed to get a job by April without putting in a lot of work, though (mostly just listened to recruiters until something hit my fancy). My work experience is good, but I don't know if it's so good that I…
>Long story short, I think narrative of job loss is way overblown.
Long story short, I ate dinner so I think the narrative of people over the world being hungry is way overblown.
Re: What is happening to jobs? Separating AI hype from reality
#228Earlier quoted context omitted.
Which of my blog entries contradict what I said here?
[flagged]
I don't get it. What point do you think those make?
They read to me like an accurate report on the progress of these models and tools.
In May 2025 Claude Code could help me debug a WordPress installation.
In July 2025 I reported on someone managing to get it to build them a macOS app. I got that working for myself in February 2026 https://simonwillison.net/2026/Feb/25/present/
Also in July 2025 I was successfully using one of the earliest async cloud environments - Codex Cloud - to scrape websites.
By October 2025 the most recent Claude could one-shot a simple Datasette plugin.
What changed in November 2025 was that the level of hand-holding needed to get good results dropped to the point that it was no longer credible to deny their utility.
> Can't wait for your Summer 2027 comment where you'll claim that coding agents really only became usable in November 2026.
Oh! I think I see what happened here. I said this:
> coding agents (Claude Code, OpenAI Codex) only started working really well in late November
"Working really well" and "only became usable" are not the same thing.
Re: What is happening to jobs? Separating AI hype from reality
#229AI already can do basic stuff pretty well. Think about people doing robotic work, ugly internal tools in big corporations and other. Decent engineer managing and reviewing AI output can a lot without big cognitive load and bunch of people which were needed in the past.
Re: What is happening to jobs? Separating AI hype from reality
#230Why does the unemployment chart show a slow rise in unemployment for a year or more before covid started? This does not agree with the data from the BLS, which showed unemployment spiked very suddenly in March 2020. https://www.bls.gov/charts/employment-situation/civilian-une...
Also, what is “AI exposure” in 2015? LLMs hadn’t been invented yet. I did just read some of the cited paper. Essentially the quintiles boil down to use of computers, not really use of AI as we know it today. I know LLMs aren’t all AI, but the thing that’s missing is the distinction between “AI” that can play chess and LLMs that can actually do your job, which have only existed for maybe a year.