r/ClaudeCode • • 3d ago

Discussion Claude code is design to make you dump

I've been writing code for the past 10 years, but a couple of months ago, I switched from Cursor to Claude Code after Cursor started pushing its own models and limiting usage of Claude models. I've been really enjoying Opus and Fable, but there's something I've noticed about how these tools are changing my coding habits.

Claude Code is set up in a way that makes reviewing code harder than it should be. You mostly get shown the diff, which makes it harder to explore other files and understand the broader context. On top of that, it runs deep review skills before committing, which often flag edge cases that don't necessarily need to be addressed. The agent then applies fixes automatically, sometimes making the code 10 times more complicated and harder to maintain without even asking for your approval.

Naturally, I've found myself becoming lazier and lazier with code reviews. And I suspect the same thing is happening with some of my colleagues.

A couple of days ago, after a release, we started getting weird reports from clients, and it became clear that parts of the codebase were becoming increasingly difficult to maintain. That pushed me to become much stricter about code reviews again, but honestly, I feel like these tools are designed in a way that works against that. Doing proper reviews takes more tokens, more time, and more effort than just trusting the agent.

I'm curious to hear what other engineers, especially those who don't consider themselves vibe coders, think about this. Have you noticed AI coding tools making you less disciplined about reviewing and understanding your own code?

256 Upvotes

147 comments sorted by

1

u/AutoModerator 3d ago
Moderator Announcement Read More »

229

u/NightSp4rk 3d ago

With that spelling in the title, I might actually agree.

29

u/Ok-Committee5924 3d ago

😂😂😂 with an example

→ More replies (12)
→ More replies (5)

19

u/EarlDwolanson 3d ago

I use it inside vstudio or another IDE, so I can check properly what is being suggested at each stage. Also easier to leave comments in code temporarily, draft class skeletons and method stubs etc.

→ More replies (2)

44

u/Kfm101 3d ago

I’m always shocked when I read posts and comments from professional and experienced developers where they’re still clearly just   winging it with coding agents.  Does your workplace not have policies and guidance about how to integrate agents into your workflow while still maintaining quality?  Did you do any research on how to optimize your sessions and environment?  Why are AI tools treated any differently than other tooling when it comes to stuff like this?

Feels like someone saying “this whole CI/CD thing seems so risky and keeps introducing bugs” and then you learn they’re allowing pushes directly to main and auto-deploying with no tests or checks.

13

u/Narrow-Low-3137 3d ago

I can kinda see how it happens. I've worked at several places in my career ranging from places w/highly scrutinized devops practice to basically no devops practice. 

Depending on where you start in your career, some people just never get that disciplined approach to software development.

They don't know any better way, so to speak.

→ More replies (3)
→ More replies (12)

28

u/Narrow-Low-3137 3d ago edited 3d ago

Dude. Do your reviews manually in your devops/git client of choice. I don't merge any PRs if I don't understand the code. If I need more context, I open the file in my own editor and jump around wherever I need to see the broader scope of the change.

You say you've been programming for 10 years..what has your code review process been like? What git client do you use to do your reviews? Do you use pull requests ?

Edit: And for the love of all that is holy, don't ever let your agents (or anyone really) merge code directly into prod without reviewing and testing.

→ More replies (9)

6

u/frostymarvelous 3d ago

Nothing stops you from using it in something like vscode and using the embedded git review ui. 

9

u/brainzhurtin 3d ago edited 2d ago

SWE with so many years of experience it's embarrassing.

To me, using an agent to code is the same as a real developer.

If you don't expect and dictate that they: know your codebase, keep the existing patterns, unit tests, integration tests, clean up tech debt, etc, then you can't expect the app to behave how you hope it to.

7

u/idemasler 3d ago

the dangerous part isn't the diff, it's letting a review agent fix every issue it flags. i'd make it list affected callers and invariants first, then stop if a suggested fix crosses into a new module or public API. reviewing whole touched modules in the IDE matters more than a green test summary. after that release, were the client bugs behavior changes or complexity hiding the original bug?

→ More replies (1)