[viraptor]

> but it doesn't refuse to write the code without first being told why it wouldn't be a better idea to do X first

Then don't ask it to write code? If you ask any recent high quality model to discuss options, tradeoffs, design constraints, refine specs it will do it for you until you're sick and tired of it finding real edge cases and alternatives. Ask for just code and you'll get just code.

[fragmede]

To be fair, they're primed to write code, even when you don't ask for it. I explicitly tell Claude "do not write code" when I don't want any, otherwise it'll spit some out just to say hello (world).

[mlrtime]

The more I read people saying that Claude is failing, the more I realize this is 90% a user problem. This is just an example, but I see it often.

Claude has a mode specifically for what you're talking about, it is actually very good (Opus 4.5) at planning and going through design without coding, it's called planning mode.

Listen, if you aren't constantly shift-tab or esc-esc during complex problems, and then struggling when it isn't working for you, rtfm, you'll get further and better results.

[frankc]

You need to be in plan mode. Not only can it not change code, its interaction with you is quite different. It will surface issues and ask you for choices.

[freehorse]

"Here is some python code that printf's the travel recommendations you asked for, btw"

[sdwr]

They are way better at code-related tasks than design or strategy ones. Anything involving users or business strategy or a "why" is vague and misguided, they have no insight.