I feel like it works A LOT better than Opus 4.8 + Sonnet. I now use it exclusively at high effort for planning and low effort for writing the code (instead of Opus 4.8/Sonnet).

However, it's absolutely exhausting to use because of the way it communicates.

All the jargon and its weird, over complicated way to phrase simple things makes it almost impossible for me to understand what the hell it's trying to even say half the time.

Cherry on top, the idiotic follow-ups and caveats that are completely useless 99% of the times but reveal major bugs 1% of the times, so you're forced to read them. Absurd.

I've tweaked CLAUDE.md to force it to only responds with TL;DRs and avoid follow-ups, suggestions and next steps at the end unless they can lead to destructive actions or loss of data, but I'm fighting against the system and diluting other instructions.

A huge piece of shit like other models, but that's what they pay me to do and I do it and go home.

▲

crab_galaxy 2 hours ago | parent [-]

I have to preface all my prompts with, “in simple, plain English…” because it doesn’t respect my rules on this stuff.

I’m glad to read I’m not the only one getting these unintelligible responses from Claude lately

	▲	altern8 2 hours ago \| parent [-]
		Nope, you're definitely not the only one. It's just really hard to understand what it's trying to say. Another rule that was really helpful for me was to disallow anything that isn't yes/no for yes/no answers. If I ask "is the DB up?", I don't want it to take 5 minutes studying the schema to tell me if any of the tables need to be optimized or not.