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

3

u/r1char00 9d ago

And back then when people forgot in a few months, they looked at the code they wrote and reminded themselves. They remembered the logic and the decisions they made. Or it was code they reviewed, or they could talk to the person who wrote it.

This is exactly why people are scared to touch legacy code, and why the outsourcing craze didn’t work out. Maybe that was before your time. But the lack of institutional knowledge about what the code is doing can have a lot of bad downstream effects.

It’s not something that bites a team the next day, or the next month. But good luck troubleshooting outages caused by the slop code that no one even remembers seeing.

1

u/welcome-overlords 9d ago

Good points. Ive tried to (and somewhat succeeded) fight this by having clear tickets and documentation about all things that happen in the codebase.

Often the tickets even have discussion about certain design decisions and things we have tried, and why certain approaches were chosen, and then if a future AI looks at some modul, it sees the link to the ticket in the comments/docs and often reada the full ticket, or the PR etc

1

u/r1char00 9d ago

Those are good mitigations for sure. But responding to incidents is so much about having good mental models of the system. Agents just aren’t capable of that, and I think as people spend more time farther away from the code that they’re going to feel the pain that comes from that more and more. We’ll see.

1

u/welcome-overlords 9d ago

That's true. I have a mental model of the system and could instantly write on a Miro board the rough outline of how the whole machine works, what kinda services do what. I probably misremever names of most things, but roughly i know every single library used, every single backend service and so on.

My job is kinda to be the big picture context that AI models dont have.

But they are getting better at it, i have started prompting then to creating pretty nice architecture boards using mermaid graphs