3 ms·
Honestly i'm less scared of claude doing something like that, and more scared of it just bypassing difficult behavior. Ie if you chose a particularly challengin
by unshavedyak 1y ago
Honestly i'm less scared of claude doing something like that, and more scared of it just bypassing difficult behavior. Ie if you chose a particularly challenging feature and it decided to give up, it'll just do things like `isAdmin(user) { /* too difficult to implement currently */ true }`. At least if it put a panic or something it would be an acceptable todo, but woof - i've had it try and bypass quite a few complex scenarios with silently failing code.
- WXLCKNO 1y agoThis is by far the most crazy how thing I look out for with Claude Code in particular. > Tries to fix some tests for a while > Fails and just .skip the test
- Paradigma11 1y agoOh, but it will fix the test if you are not careful.
- alwillis 1y agoSounds like a prompting/context problem, not a problem with the model. First, use Claude's plan mode, which generates a step-by-step plan that you have to approve. One tip I've seen mentioned in videos by developers: plan mode is where you want to increase to "ultrathink" or use Opus. Once the plan is developed, you can use Sonnet to execute the plan. If you do proper planning, you won't need to worry about Claude skipping things.
- unshavedyak 1y agoI wish there was a /model setting to use opus/ultrathink for planning, but sonnet for non planning or something. It's a bit annoying having to swap back and forth tbh. I also find planning to be a bit vague, where as i feel like sonnet benefits from more explicit instructions. Perhaps i should push it to reduce the scope of the plan until it's detailed enough to be sane, will give it a try