Show HN: The load-bearing vocabulary of Claude

Everyone talks about Claude, but I'd like to bitch about Sol. "Unusually" is its absolute favorite word in the chat interface (less so in Codex), and I fucking hate it. Every single thing is unusually something. "Unusually good", "unusually efficient", "unusually inexpensive", "unusually attractive", "unusually difficult", "unusually nasty", "unusually cacheable", "unusually interesting", "unusually decisive", "unusually narrow", I'm surprised I haven't seen "unusually unusual". If I search chat history for "unusually" it brings up every single fucking chat I have from before I added it to an illegal words instruction. I can't believe I haven't seen anyone else complaining about this, it's as pervasive if not moreso than anything I've seen from Claude.

It's a waste of tokens to do it post-hoc instead of fixing it upstream, but when I see a wall of text I just prompt "TLDR;"

"Fuck" isn't there. Did they only analyze "AI" PRs?

I'd like to share with HN an almost exact message I got from Fable today, with exactly ONE word changed for privacy reasons.

I love what I can build now, but I sure as hell don't love the headaches this trend has been giving me.

> So the full honest arc on the case we set out to fix: the expiry rules and day note tripled the loose version of the story, the relay fix carried the device’s own guardrail through the pipeline, the fair replay then revealed the last mechanism — ticket-anchoring — which none of the shipped layers reach. Remaining options, in order of my confidence: making the resolved-ticket summaries in the AI’s context carry their day so the expiry rules have something to bite on (small, mechanical, targeted at the observed anchor); and the plan-B second-model check, which structurally catches this class no matter how the model reasons. About $25 of headroom remains. Which way?

Yikes.

(The worst part is that I understand it)

[flagged]