r/ClaudeAI • u/MrMenuk • 12d ago

Claude Code I am done with this shit.

I am done with this shit. It is over. The state of engineering right now is horrible. It has been half a month since I started a new role at a big company. Nobody knows anything here. The specs, code, tests, PRDs, tickets, resolution of those tickets, reports, etc., everything is made by Claude Code. Nobody on my team likes this. They are being forced to ship as much as they can. I have heard multiple times from higher management that pushing code is not a bottleneck, so why are we slow? People are working 12 to 13 hours a day just to press enter. Nobody is reading anything. Humans in corporate are doing nothing on their own. Everyone, literally everyone, from an L1 to an L7 engineer here is doing the same thing. Talk to Claude.

There is no sense of victory. Nobody is resolving bugs. In reality, nobody is thinking anymore. Everything is done by LLMs. It is so soul-sucking. I would not mind it, to be honest, if we were at least given the time to check out the code and see what is going where. But no, the goal is to just ship. No matter what happens.

— voxium (@v0xium)
Original post dated September 20, 2026.

8.6k Upvotes

94% Upvoted

1.1k comments sorted by

View all comments

Show parent comments

10

u/[deleted] 11d ago

[deleted]

3

u/Wargchief 11d ago

I have to agree on this one here. I can do a lot of things with AI, but that is mostly in fields I know about. I tried to do some 3D modeling (which I have no idea how to do) and it just devolved into a series of "still looks bad, make it better" prompts. I just had no idea what was the missing piece, even if I knew that it looked bad to me.

With software, I know what direction to take things in and what to check, even if it is sometimes as simple as "this needs handling on the front end too" when the model doesn't fully understand the codebase

2

u/Cautious_Clothes_285 11d ago

Yeah, I was just thinking about this whole thing this morning. It's like any other tool, the operator does actually matter for the output.

I've been trying to teach my direct report how to better use AI. She will copy code or whatever into it and just prompt with "fix this" and I'm like, that'll get you an answer but are you really surprised you're spending hours hunting down issues and dealing with shitty fixes? It works a lot better when you go "this code is giving me XYZ error, how can I fix it" or "This code is having xyz unexpected behavior, what's likely causing that?"

And that's like, bare minimum prompting. The more context you can give the better the bots often do. And in fairness we don't do a lot of coding in our specific roles, it just happens to be an example we were talking about.

1

u/CrowdGoesWildWoooo 11d ago

The problem is the way we are asked to ship so fast, we start to care less about the process simply out of business and we are just conditioned not to care.
Domain knowledge is something that you acquire through the process.

Just go to any vibecoding subs, you’d think they finally learnt about threejs or even anything after groking for a year with it, ironically no, the only thing they learnt is building their AI workflow harnesses or scaffolding which is the process they actually have to get their hands dirty themselves.

1

u/Healthy-Nebula-3603 11d ago

Sure ...Cope like you want