https://github.com/EspoTek/.claude/blob/master/CLAUDE.md
replyStick the "Never suppress errors" section into your Claude.md, this will never happen again (works for me with Python/Flask, ymmv for other languages).
A lot of that sounds like offensive programming: https://en.wikipedia.org/wiki/Offensive_programming
replyDidn't know there was a word for that, thanks! Looks like my programming style matches my communication style in general. :P
reply[dead]
replyFallbacks and backward compatibility are killing me :) So many code paths that just don't fail predictably.
replyI’ve experienced this with GPT but not with Opus/Fable.
replyI experience it with everything including opus/fable.
replyThough my feeling, no proof, is that the opus/fable today is not what it was months ago. there was a time for about a month where opus was incredible. Just incredible but as fable started to move out i swear to god it feels like sonnet now. Fable feels like opus used to but costs more.
recent gpts are horrendous for this, whereas recent claudes have a tic where they incessantly add useless comments referring to previous changes and will use multiple single-line comments instead of a standard multi-line docblock.
replyThe incessant need to constantly leave "the code doesn't work like <bad implementation>, it works like <good implementation>" frustrates me to no end. No amount of directions against it in project MEMORY, CLAUDE.md, or even embedded in the prompt seem to be able to stop it from doing this. I don't understand how it could have gotten into the training because I've legitimately never seen an actual person write code comments like this.
replyIt writes code as if the audience is you, the user of Claude, and not other developers reading the code in the future. I found that it helped to instruct it to keep in mind who the audience is and only write comments that describe the current state of the code and never describe anything that can just be inferred from the git history. I found that that helped, and I almost never see these nonsense comments anymore.
replyMaybe it's self trained. It eats its own output and likes it...
replySounds like my code. They may have been trained on my code!
replyI have not noticed this with Opus 4.6+. The result is usually not too far from what I would have written myself.
replyOpus 4.6 was the best model in the family, following two ones were seriously brain damaged to do well on benchmarks.
replyyeah those have been horrible
replyI wouldn't say terrible-terrible but only better at from-prompt-to-solution rather than interactive discussing and problem solving.
replyI tend to define it "better at solving, worse at assisting phenomenon". Which doesn't properly show on benchmarks that only focus on the solving part.
I tell it to avoid belts and suspenders, don't leave dysfunctional code in, and fail loud. Seems to change that behavior.
reply