I don't really care if it says load-bearing or belt and suspenders so long as it's using them correctly, which it mostly does.
I don't know how programmers, who are so used to staring at the same handful of keywords every day for decades, have suddenly become so discerning.
Yes, Claude writes boring and predictable prose. It also writes boring and predictable code. That's good!
> which it mostly does
I don't think that's true. I find that it way, way over-intensifies: eg using "load-bearing" for something that's just "kind of necessary although we probably could find a way without it". My personal gripe is how easily it uses "incredibly" or "wildly": just today it was telling me that something is "incredibly cheap" to mean that it's not over-priced ("cheap" would have been okay and even then, barely)
I'd contend that Claude's prose is not boring. It's generally overly grandiose waffle with a cliche or two punctuating every other sentence. It's good for tasteless marketing copy, sure. It's inappropriate in most scenarios.
I hate it because put together, it all increases the cognitive load of understanding what it's saying. It routinely invents phrases, and every single one makes me pause and think "okay, what the fuck does that mean". Half the time the phrases are incoherrent.
I definitely care. They are impressionistic responses that smooth over exceptions and lack precision and are often completely wrong in the sense that, when pressed, the agent will acknowledge the lack of rigor in the response. "That phrase was wrong of me to use. There is clearly an exception to what I just said, and it goes like this..."