Which is kind of the inverse of how people work; a really smart person can condense difficult ideas into simple[r] terms. Whereas people who struggle speak a lot but say very little.
High/X.High do seem to deliver better quality results, but it sometimes feels like needle-in-haystack extracting that from the word vomit.
EDIT: also there's a reason the dial is called "effort", not "smarts".
Of course I don't know if there's really a way for this to be molded in current LLM's (sounds more like diffusion)
They work on a problem until their brain is full of problem-related concepts. Then something comes. After validation it might be a solution.
See, this insight it had early on looked like a red hering for a while, but then turned out to be load-bearing. And that's not just a difference in semantics, it changed the whole conclusion (spoiler: it didn't). And Claude is very eager to tell you about this exciting journey
Like, were the other parts not honest? I don't understand how Anthropic let it get like this, it's been such a clear regression
Every time, without fail, it would get me 90% of the way there and then leave a small note, exception, or deferral. When instructed to address that, Opus would somehow take nearly the same amount of time as the first 90%. And then it would finish with yet another deferral. Repeat ad infinitum.
You can sometimes get around it using the `goal` directive provided you are not subject to the constraints of mortality.
And the worst part is that this little problem will keep sneaking into the context of future sessions, unless you spend the time to fix it. Even if it isn’t important, I’ll sometimes have Claude fix it so it will shut the F up about it going forward.
it's downright exhausting to read claude, the language style was a regression imo.
You get a week of research and debugging and testing compressed into a few pages. Even if it's explained well, it's just so much information. And since it's AI, I'm constantly second guessing "is that really true?" and it's exhausting.
Can't agree with you more. I review 2-3 PRs a day from my team of eight data engineers. Most of my team members use Claude to write SQL, dbt and Python code. Some of them use Claude a lot, some less so. I can easily tell when I review the code that is mostly Claude generated vs. the one that is not. In dbt models where we have a lot of biz logic in intermediate layers, that's where I really have a difficult time following Claude-generated comments. So much jargon copied over from other adjacent dbt models (yet inconsistently), and the prose is super choppy (for the lack of better word).
After reading a looooong sentence/comment line, I still can't figure out what it really means. Had to always re-read the line 2-3 times (sometimes, more) to sort of understand. Reading code, however, is so much easier and usually, I just skip to reading the code and then come back to the comments. :D
I find it helps immensely but it'd be nice if I didn't have to do that.
P.S. Although my wife insists that I should stay polite in case AI overlords remember how I treat them ...
Separately, my boss confided in us that he's super abusive with his agent, wondering if we are too (no, lol). While I try not to read too much into this (which he doesn't make easy), I also can't help but not really notice a whole lot of amazing agentic delivery differences from his side. On the contrary, while the passion may improve his agent's performance, I'm not sure if it doesn't decrease his, upending the entire theatre.
And yes you could add context (memories, rules, CLAUDE.md entries, etc.): they won't help (for long). Same for hooks that remind Claude to be concise: it gets "attenuated" and starts ignoring any such instructions quickly. There's also writing guidelines ... but they're basically just more context with slightly higher weights (ie. Claude will still ignore them).
I've even gone so far as to make a hook that identifies long responses and requests shorter versions (which is challenging in itself, as you need to run another lower-powered model to evaluate how long is "too long", as what's "long" when the expected answer is one line is different from what's expected for a ten line answer). However, that just shows you the long version, then some hook text, then (10-15 seconds later) it shows the short version. So I created a proxy that hid the long version/hook text for me ... but I had to abandon it because all that used up so much usage I was running out.
I'm fuzzy on the details, but Caveman somehow "hacks" Claude in a way that gets past all that ... but it takes things too far in that direction, with "cave man" speech that sucks.
I took time to figure this out after Fable spat out "...then stays purely as cascade-debugging provenance rather than load-bearing arbitration."
I will say that Kimi feels nice but slow, GLM feels faster but has limited tokens (even off-peak) and OpenAI is nice and fast but has limited context (258k shows up in Codex, really).
Neither of them are perfect, but I prefer their type of prose across the board to what Opus 5 and Fable 5 kept outputting. I'll probably check out Anthropic again in a year, but for now I need a break from its brand of slop. Oh also all of the other ones allow usage in OpenCode with their subscription plans.
This sentence reads like Claude wrote it. Perhaps it did, or perhaps Claude has learned to write like the folks who work at Anthropic?
(Had I edited this, I would have said that a colon is not the right separator here. The second clause does not _explain_ the first, per se, bur instead expands upon it. Consider instead: "In some cases, however, its prose is denser than Claude Fable 5's, with longer sentences and fewer paragraph breaks.")
Also, could be just Claude rubbing off on them than it being Claude authored. I'd imagine they read it quite a bit.
Gotta fit in the watermarking.
that feels like they just blocked words like load-bearing but can't actually fix the real problem. The insane word slop density and run on sentences was the real reason it became annoying to work with claude, colored with way too many analogies and pointless linguistic comparisons.
"If you respond with more than 3 paragraphs, give me a TLDR"
"Do not assume I know all technical jargon, please explain things plainly"
But LLMs will fail at this question: they will tell you about Lamborghini's latest car and mix some history in it. Just try.
Which is the wrong answer anyway, because there's at least two major companies called Lamborghini, one making cars, one making agricultural equipment and at least one famous person (Elettra) with that family name.
This very simple test/question makes me realize how much do I hate LLMs in a sense: while I agree that the answer it gives is the most plausible for 90% of the users, it's ultimately both wrong and long. And that 90% compounds.
But there's no "correct" answer in my eyes than "who are you referring to?". Possibly without listing all the possible Lamborghinis.
If you're picking nits, why not focus on the word "do" and (wrongly) expect an answer like "Lamborghini (either of the two main companies of that name) does not 'do' anything - the companies employ humans who 'do' things. Lamborghini is a legal entity established to allow humans to 'do' things, such as make cars, or agricultural equipment."
Shared context is a thing. Reducing every conversation to first principles is not always required. Get a grip.