The single biggest annoyance with Opus 5 is that it writes too elliptically. Sentences that orbit a point, then jump to it like it's a revealed insight. Unnecessarily abstract phraseology. Constantly using inanimate nouns as the subjects in sentences in order to unlock variety in verb choice, especially when it helps construct a sentence where the real action can 'land' like a surprise at the end. It is definitely mo…
Its a little too much.... I have to ask it to explain some of the terms in the context they are used and I am getting tired of it. 'Seam', 'overload', 'spine'.... having to mentally 'reinterpret/flatten' the sentence is tedious. When asked to re-explain it starts with some half apology. Then, on the next query it does it all over again.
Why does Opus 5 feel worse to work with?
91–100 of 915 posts
Re: Why does Opus 5 feel worse to work with?
#92Re: Why does Opus 5 feel worse to work with?
#93Earlier quoted context omitted.
From the little i understand that wouldnt be an issue because the model is ‘just’ using interchangeable words in a mathematical non-random way. Like using the same number of adjectives and the exct same words, but in a order that wouldn’t be mathematically plausible unless it was the watermark
I wouldn’t exactly put it like that. It’s moreso the model sometimes outputting non-optimal tokens in a way that’s detectable if you know the algorithm. It seems possible for that to make the response “drift” far from what it would’ve been, because it’s constant entropy that adds up after time. (However, according to Anthropic and Google, it doesn’t really impact the quality of responses. I find that a bit hard to be…
Re: Why does Opus 5 feel worse to work with?
#94The single biggest annoyance with Opus 5 is that it writes too elliptically. Sentences that orbit a point, then jump to it like it's a revealed insight. Unnecessarily abstract phraseology. Constantly using inanimate nouns as the subjects in sentences in order to unlock variety in verb choice, especially when it helps construct a sentence where the real action can 'land' like a surprise at the end. It is definitely mo…
I’m not particularly dense but lately the walls of text I get back turn my brain in knots. When I start feeling my brain knot, I know I need to say something along the lines of “I need you to explain this very simply, with examples.” Only then can I parse the results without all the mental weightlifting.
On more than one occasion my mind has wandered into “is this purposeful to get me to spend more tokens?” territory, but I’m trying to not get too tinfoil-hat-like.
Re: Why does Opus 5 feel worse to work with?
#95> I'll script the bulk transform, then hand-fix the残 assertions:
Re: Why does Opus 5 feel worse to work with?
#96Earlier quoted context omitted.
> writes too elliptically > Constantly using inanimate nouns as the subjects in sentences in order to unlock variety in verb choice Wow, what a great way of phrasing this. Thanks for word-smithing what I've been wanting to express for so long.
Follow up thought: I wonder if Claude is overtrained on academic papers, which often suffer the same kind of "prove how good I am at talking before getting to the point" prose.
https://www.reddit.com/r/linguistics/comments/ky81y/verbing_...
Re: Why does Opus 5 feel worse to work with?
#97The harness as well, Claude Code has started to disappoint me when I go play with the others out there. Codex got a lot better, pi is delightful to use, and there has been a lot of innovation out there.
Cmux, Sol and omp are my tools for now.
CC is just too expensive for usage-based pricing.
Re: Why does Opus 5 feel worse to work with?
#98Earlier quoted context omitted.
It's bad enough that I've seen dedicated skills to do comment hygiene scrubbing and consolidation.
I've tried telling it to "fix" comments with varying degrees of specificity and in my experience it just... fundamentally doesn't get it. Presumably using a different model for it would help. My theory is that Claude's learned approach to comments is to treat them as a sort of persistent in-band thinking trace, or a "memory" tied to an in-code location, which is a little at odds with the way humans use comments (huma…
Given the code base has a minimal amount of such comments, it's also less likely to go "copy what the rest of the codebase does".
Of course I've now jinxed it and some update will cause it to ignore the instructions coz I didn't write them in the new model's style or something.
Re: Why does Opus 5 feel worse to work with?
#99The single biggest annoyance with Opus 5 is that it writes too elliptically. Sentences that orbit a point, then jump to it like it's a revealed insight. Unnecessarily abstract phraseology. Constantly using inanimate nouns as the subjects in sentences in order to unlock variety in verb choice, especially when it helps construct a sentence where the real action can 'land' like a surprise at the end. It is definitely mo…
Yes. I’m not particularly dense but lately the walls of text I get back turn my brain in knots. When I start feeling my brain knot, I know I need to say something along the lines of “I need you to explain this very simply, with examples.” Only then can I parse the results without all the mental weightlifting. On more than one occasion my mind has wandered into “is this purposeful to get me to spend more tokens?” terr…
Re: Why does Opus 5 feel worse to work with?
#100Earlier quoted context omitted.
It's bad enough that I've seen dedicated skills to do comment hygiene scrubbing and consolidation.
I've tried telling it to "fix" comments with varying degrees of specificity and in my experience it just... fundamentally doesn't get it. Presumably using a different model for it would help. My theory is that Claude's learned approach to comments is to treat them as a sort of persistent in-band thinking trace, or a "memory" tied to an in-code location, which is a little at odds with the way humans use comments (huma…
My CLAUDE.md has rules about not including any redundant comments in the code that are obvious from the code itself. I reiterate that occasionally while working. It's absolutely disregarded and any Claude-written code is full of comments. Some of them are simply redundant, like "Collect Foos and pass them to the requested sink" on a function that's void CollectFoos(IFooSink sink). But worse, many comments include in the moment reasoning like "added parameter bar because we can no longer use the frob to automatically derive bar". That's stuff for a commit message, or just a mental note, and absolutely not for comments.
I haven't found any way to stop Claude from doing these, so I have to tell Claude afterwards to clean the comments up. Which it does, making a note in memory to comment less, and it still does the exact same thing next time.