Live data from Hacker News

What is happening to jobs? Separating AI hype from reality

siepr.stanford.edu

71–80 of 412 posts

Re: What is happening to jobs? Separating AI hype from reality

#71
post #29
post #25

Earlier quoted context omitted.

> we're going to decline to renew some software subscriptions Yeah, sure you are. Report back when it happens.

We got the thumbs up from management last week.

Cool! Which ones?

(Replacing overpriced garbageware with something I scraped together in 3 days is my jam. But the specifics matter a lot.)

Re: What is happening to jobs? Separating AI hype from reality

#72

Recently poked around the job market to see what I qualify for in this day and age. Working as a solo builder in my org I would say that I have done enough in the last 18 months to consider myself “with it”. What I found was pretty brutal. Companies asking for 4 years of agentic AI experience… pardon? Then it hit me. Oh they are all making shit up now and have no bar that anyone can hit because they are believing in…

> Companies asking for 4 years of agentic AI experience… pardon? Not that I am trying to excuse it, but this is not a new thing, nor specific to AI. Job listings that ask for X years of experience where X years is sometimes literally longer than the technology has even existed has been a staple complaint of developers over my entire career, and I'm old af.

My favorite in this regard is this story: https://x.com/tiangolo/status/1281946592459853830?lang=en

Sebastián Ramírez seeing a job requiring 4 years of experience with FastAPI, the library he created 1.5 years before that posting.

Re: What is happening to jobs? Separating AI hype from reality

#73
Employees have no incentive to meaningfully implement AI to increase productivity, and if they do so, they have no reason to share it.

If AI means job cuts and not using AI means job cuts but no one really tracks AI impact that means performative adoption of AI is safest, and real gains are to be sandbagged as innate magic hand waving.

At my work I'm one of the few who says "I made this with Claude" and the near impossibility of using AI with internal email etc for security reasons means AI use is one-shot wonder oriented (for me, in my experience).

If AI usage was incentived with actual bonuses and praise it might go over better. So far I haven't seen that. Its just implicit threats.

Re: What is happening to jobs? Separating AI hype from reality

#74
post #29

Earlier quoted context omitted.

We got the thumbs up from management last week.

Cool! Which ones? (Replacing overpriced garbageware with something I scraped together in 3 days is my jam. But the specifics matter a lot.)

The software which manages our instrument spec sheets, and the software which manages our field tech rounds.

Re: What is happening to jobs? Separating AI hype from reality

#75

Earlier quoted context omitted.

bro, tech hr were asking 6 to 8 years rails experience before dhh (rails creator) was even born. This has been almost a meme on hacker news for some time. You can google it via hn dot algolia dot com by using the right keywords. Of course, i exaggerated it a bit, just like a lot of startups and vcs pimp their stuff, just that they do it much more, and they do it for money, while my mine was for fun. ha ha ha.

Wow, fuck. Literally some minutes later, i scrolled down below my above comment. And saw this one. https://news.ycombinator.com/item?id=49053201 Which doesn't validate mine, but agrees with what I said. Except that it was posted about one hour before mine. go figure.

double wow. yet another one on the same lines, as a reply to the link i posted above.

Re: What is happening to jobs? Separating AI hype from reality

#76

Recently poked around the job market to see what I qualify for in this day and age. Working as a solo builder in my org I would say that I have done enough in the last 18 months to consider myself “with it”. What I found was pretty brutal. Companies asking for 4 years of agentic AI experience… pardon? Then it hit me. Oh they are all making shit up now and have no bar that anyone can hit because they are believing in…

Use it in your favor. You just have to get past the recruiter/talent acquisition where everyone else is getting auto-rejected. You should be doing that anyway.

If decision-makers put up a front of recruiters and talent acquisition "specialists", don't they send a very explicit message that going past those is unwelcome and won't be considered?

Re: What is happening to jobs? Separating AI hype from reality

#77
post #13
post #7

Organizational inertia is a real thing. There are still fortune 500 companies with internal bans on AI. A lot of the answer to "how much impact has AI had" comes down to "how much have we even attempted?" In my workplace, we're going to decline to renew some software subscriptions because a non-programmer vibe-coded their replacement in a week. The impacts are here, they're just not evenly distributed yet.

> In my workplace, we're going to decline to renew some software subscriptions because a non-programmer vibe-coded their replacement in a week. The impacts are here, they're just not evenly distributed yet. Interesting to see the impact in the long term when battle tested software gets replaced with vibecoded variants by non-programmers. Does it increase data breaches or quality actually goes up?

To me, this is inline w the book BULLSHIT JOBS, and that class of job that was really like a few hours a week but 40 hrs pay. That type of job should be automated and the person removed. The exception is going to the person who complained to management that it’s a 2 hr a week job…. Give me more work.

Re: What is happening to jobs? Separating AI hype from reality

#78
post #55

Earlier quoted context omitted.

I wonder how much of it is real and how much of it is people just being worn down by the hype to the point they can't fight it anymore Very smart people aren't immune to being worn down over time

I really don't think that's how it works. Smart, experienced developers who thought coding agents were junk for most of 2025 and think they're useful now in 2026 are not saying that because they got "worn down over time".

I didn’t start using Claude Code until late 2025. Prior to that I would use ChatGPT to give me snippets of code but I was still doing most of the actual code writing. Coworkers told me in late 2025 about how they hadn’t written a line of code in “months” and just use Claude Code/agentic “whatever” so I tried out Claude Code and was pleasantly surprised. It is passable to have entire apps written by LLMs (I’ve made several that I otherwise never would have had the time to create by hand), but I wouldn’t say maintainable or easily extendable. It’s hard to be specific, but there’s something about LLM code that doesn’t look “natural”, and I’m not talking about the excessive use of comments in code. The code itself is unnatural. Functional, but unnatural. I wouldn’t want to suddenly lose LLMs and have to read through and understand and continue enhancing a codebase created by an LLM.

Re: What is happening to jobs? Separating AI hype from reality

#79

Earlier quoted context omitted.

Yep, the goalposts just keep shifting. In reality: they still don't work well, unless you're content with producing low quality work.

This is the opposite of my experience since about February of this year.

The quality of the output is so variable. It depends on the model, “effort level”, prompting, probably even the programming language/app functionality, and libraries involved. For example, I find LLMs are best at making simple web apps. These web apps, while simple, would still take a senior engineer perhaps a week or two to create, but LLMs can spit them out inside of an hour. Conversely, LLMs struggle with things like Docker or local model stuff. Parallelization of code is a mixed bag. In these areas I think it often would have been faster for me to write the thing by hand.

Re: What is happening to jobs? Separating AI hype from reality

#80

Earlier quoted context omitted.

Use it in your favor. You just have to get past the recruiter/talent acquisition where everyone else is getting auto-rejected. You should be doing that anyway.

If decision-makers put up a front of recruiters and talent acquisition "specialists", don't they send a very explicit message that going past those is unwelcome and won't be considered?

[deleted]
Post reply on HN