←back to thread

What makes Claude Code so damn good

(minusx.ai)
469 points samuelstros | 1 comments | 23 Aug 25 19:07 UTC | HN request time: 0s | source
Show context
yumraj ◴[23 Aug 25 20:37 UTC] No.44998945[source]▶
I made insane progress with CC over last several weeks, but lately have noticed progress stalling.

I’m in the middle of some refactoring/bug fixing/optimization but it’s constantly running into issues, making half baked changes, not able to fix regressions etc. Still trying to figure out how to make do a better job. Might have to break it into smaller chunks or something. Been pretty frustrating couple of weeks.

If anyone has pointers, I’m all ears!!

replies(6): >>44998959 #>>44999168 #>>45000839 #>>45001463 #>>45001506 #>>45015437 #
1. jampa ◴[24 Aug 25 02:38 UTC] No.45000839[source]▶
I felt that, too. It turns out I was getting 'too comfortable' while using CC. The best way is to treat CC like a junior engineer and overexplain things before letting it do anything. With time, you start to trust CC, but you shouldn't do that because it is still the same LLM when you started.

Another thing is that before, you were in a greenfield project, so Claude didn't need any context to do new things. Now, your codebase is larger, so you need to point out to Claude where it should find more information. You need to spoon-feed the relevant files with "@" where you want it to look up things and make changes.

If you feel Claude is lazy, force it to use more thinking budget "think" < "think hard" < "think harder" < "ultrathink.". Sometimes I like to throw "ultrathink" and do something else while it codes. [1]

[1]: https://www.anthropic.com/engineering/claude-code-best-pract...