4 Prevalent Themes in Discussion About Claude's Language
-
Frustration with Incomprehensible Jargon and Overuse of Specific Phrases
Users consistently complain that Claude's output is filled with confusing, repetitive terminology ("load-bearing seam," "fibred," "capstone") that obscures meaning and feels artificially inflated."The fibred side folded its capstone into the existing name, so the kinds are asymmetric." What on earth does it mean to fold a capstone into a name‽ — black_knight
"You need a PhD to understand its explanation of a code snippet." — fny
"It just overuses jargon that has NO meaning. Sometimes, it actually hand waves too much as well while trying to dumb down stuff for you." — Labo333 -
Speculation About Root Causes (RLHF, Training Artifacts, Agentic Behavior)
Many theorize that Claude's style stems from reinforcement learning (RLHF) rewarding novelty, internal agent communication, or training on AI-generated text, rather than inherent intelligence."I suspect it's the same thing going on in the hidden thinking tokens." — fwip (referring to agent summarization)
"My unprovable pet theory is that, especially for writing about technical topics, the RL process has an open-ended way to weight things for quality..." — zbentley
"It's like it has a built in e bullshit generator." — swader999 (linking to bullshitgenerator.com) -
Debate Over Whether This Represents a Problem or Just Different Communication
Some argue Claude's style is actively harmful and non-human, while others see it as neutral or even beneficial for technical precision, noting humans may adapt to it."This represents a great argument against the somewhat frequent claim that 'AI writing patterns reflect human writing patterns'. Rather, AI writing is distinctly not human..." — bakugo
"I suspect, as we continue forward, humans will slowly start to adopt the language of LLMs..." — nater5000 (noting his own adoption of "... such as, , etc., ...")
"Is it actually better though? Can you even measure it? Unguided, Claude will just produce mediocrity..." — incrudible -
Practical Observations, Workarounds, and Broader Impacts
Users share coping strategies (output styles, switching models), note real-world adoption of Claude-isms in workplaces, and discuss implications for documentation and communication."They just addressed this with 'Output styles'" — josefresco (linking to Claude's documentation)
"In the enterprise, we are already adopting them. 'Seam'... is now not only our defacto way to describe the boundary..." — threecheese
"I've found myself rewriting my own words to avoid Claudisms (because they can be cringe and I don't want people to think I'm copy/pasting Claude output at them)." — cpeterso
"I just subscribed to ChatGPT yesterday, as I've become impatient with Claude for a text-dense project I'm working on." — rubslopes