Ask HN: AI has changed my job for the worse

[dead]

I feel your worries, but sooner or later sde roles will adjust to the new requirements and tools. If a companies business model is at risk by an evolving technology or innovation, it wasn't very good after all. Nonetheless, the skills are still essential to good products imho

This seems to be par for the field rn. I would say learn the tools for now, do your best to ship code you like, release as many f*cks as you can about what you're building - especially if the product and majority of products belong to someone else, and start putting feelers out for something better to hopefully come along.

It sucks SO much rn, but it seems the majority option is to grin and bear it for the time being and pray to whatever gods you believe in that we get back to something sane sooner than later

There’s tons of jobs in the world. Go get a different one if you’re that miserable?

You’ll probably find something to hate about that new job, too.

Everyone in the field seems to be in deep FOMO driven by the other guys also being in a state of FOMO. This creates chaos, delusion and a stressful environment where things are irrational.

I understand your thoughts, we have to keep pushing through this and saner heads will prevail.

be the best at using llm and do talks how to use them get noticed and stay hired.

It’s understandable to feel this way — the shift happened incredibly fast, and a lot of teams weren’t given time to adapt. Maybe the real challenge is figuring out how to redefine what meaningful work looks like in this new environment.

[dead]

This too shall pass.

Why aren’t we replacing the executives who make the poor business decisions which lead to layoffs with AI agents?

find a project on github and contribute it!

Not to be flippant, but - be glad you’re not a writer, because you might not have a job at all.

They won't get rid of all, but many of you will be let go for sure.

I feel the same way. Im on the job market (though still employed) and i can tell you my core skills have degraded since using LLMs last year or so where technical (non leetcode!) interviews are now more challenging to me since i forgot how to make all these small decisions (eg should this be a private class property or public).

I decided to just disable codepilot and keep my skills sharp i know we will be called back to clean up the mess. Reminiscent of offshoring in the 2000s

name and shame, so that I can get off of their products ASAP.

vibe code is going to crash those apps and I want to be away from them when it happens.

your job security is probably at risk already, so sharpen up that resume killer -- the market is rough right now.

You’re not alone—many teams pivoted fast to agent-written code, and it can feel like craftsmanship no longer matters. A few concrete moves:

- Have a candid 1:1: say you’re misaligned with the process, but propose owning guardrails leadership cares about—reliability, security, test coverage, CI policies, prompt/eval hygiene. Suggest measuring outcomes beyond velocity: defect escape rate, change failure rate, MTTR, SLOs, incident cost. - Differentiate where agents are weak: ambiguous requirements, system design, debugging gnarly prod issues, performance tuning, threat modeling, compliance. Volunteer for those areas. - Use AI defensively: generate tests, fuzzers, benchmarks, docs, migrations; prune agent output; write prompts/evals to reduce rework and incidents. - Protect yourself: keep a brag doc with quantified impact, network for internal transfers, and quietly explore roles that still value rigor (fintech, healthcare, infra, aerospace, devtools). - Set a 60–90 day window. If nothing changes, execute an exit plan rather than burn out.

It’s okay to be disillusioned. Your edge now is owning quality, risk, and outcomes—things the org can’t ignore even when throughput is cheap.

I think LLMs can generate tons of production quality code if you put in the time. I do it every day. The output and productivity is amazing.

I'm also really bored and hate that my job is writing specs and stupid prompts.

I read what you say, but I can hardly imagine how people can be twice as productive. I use Claude daily for writing various scripts. It produces a lot of code, so yes, if I measured it by generated code, then it's productive. However, it works best for short, clearly defined tasks/scripts. If you want anything longer, you have to watch it like a hawk so it doesn't go off track. And I'm not sure if I would give this code to someone else to use without a thorough review. I would say it may be even less productive (I think there was a paper on that).

I also use LLMs for writing; it's good, but again, you need to carefully read everything and rewrite passages that are completely made up. So I'm not really sure how this can replace people, to the point that Amazon is firing 30,000 people. I have a hard time squaring it that it's because of AI.

>and you have to keep up with everybody who ship twice as much code as before

The competitive nature of this regard was always there, it just took a pause during Covid hiring.

FAANG in mid 2010s used to be fairly competitive.5-10% of the people that got the in-person interview got the offer. The stories you heard about work load and stress and PIPs weren't so much about how the expectation was, it was more along the lines of the bottom line of developers who never developed the skill set to be effective at work just couldn't keep up with the people that did.

Companies still grew, so people were still building stuff, and if you knew any of the "top" developers, you saw they weren't stressing. Partially, they enjoyed the work they did and weren't working for the FAANG paycheck only like the majority of people. But mostly its because when it came to doing the work, the biggest advantage that they had is they had the ability to independently figure shit out. This is where "knowing how to code = knowing how to google" and "copy pasting stackoverflow" memes came from. Whereas people that didn't were always slow because they a) were only doing what they have been taught without any interest of actually learning things, and b) they relied on others a lot for guidance.

Then came the covid hiring craze when interest rates were low and companies invested a shit ton of money into products. People needed to get hired. Standards slipped. Lots of people with very low skill got hired that should never have been.

Now, the competitive edge is back on, except this time, its about how to use LLMs. Contrary to popular belief, LLMs take skill to use, not everyone can vibe code services into production. Prompt engineering is very real. To get LLMs output good quality code you have to guide them quite a bit. If you don't have a set of personal prompts you use to get LLMs to do stuff, you are behind.

Thats the nature of the game where new grads can make 100k out of college. That money isn't free. Learn to play the game or don't play at all.

[flagged]

These tools have already peaked usage, and even its greatest proponents are questioning its viability, see:

https://garymarcus.substack.com/p/is-vibe-coding-dying

I'm under the impression a lot of these tools are:

1. Aggressively pushed by VCs on company boards.

2. Productive of code that is not maintainable and becomes very difficult to deal with when it is non-trivial. 3. Not what customers want.

Don't get me wrong, I use LLMs and LLM tech in my work*, they are useful and interesting products, but they are a small part of the work and a small part of the product. Sure, there are people who use them extremely effectively, but those people are offset by those who have LLMs write code they don't understand and do not review (leading to a scenario where code is effectively ghost code often without even provenance back to the LLM that wrote it).

It seems to me that layoffs in tech are partly a cultural contagion in executive circles, but more importantly it seems to me like offshoring is much more responsible.

[*]: Mainly for codemods and reorganization of code, where I'm not really changing the intent of the code but its structure.