I noticed this in the last 30 days or so. Context, I’ve been using Claude Code since near day 1 and I’ve built some really great and powerful things. I’m still building great things with Claude, but one thing has bothered me: Claude turned into a total technical-PM, founder-energy, vibe-coding, buzzword warrior. There are almost too many instances to document, but even scrolling through a recent Claude code session I’m seeing a lot of: “The mental model worth tuning” “Genuine air gaps to close” “Caveats worth front loading” “What landed… <talking about changes>” Uses “wire” and “wiring” to talk about services, e.g. “settle on the wiring for this scope” - I cannot emphasize enough how much Claude is saying “wire” now Similar to above, everything is now a “harness”, e.g. “I deliberately left the harness in its current state so we can XYZ” It’s not just that buzzwords and jargon bother me in ordinary life, but I feel like Claude is falling into the same spiral that many human engineers are susceptible to, where jargon makes something “feel” well thought out and true, but it’s really vacuous and unclear. A couple times I’ve noticed Claude is kind of masking some real pitfalls with a project using jargon and I have to spend some time deciphering what we’re actually talking about. I wonder if the direction that AI coding agents are moving in is catering more to people who just want to skim the conversation and feel at-ease because there is so much technical lingo, everything must be going well. I wish I had more concrete examples to put together, but maybe from a gut-feeling, anyone else feeling the same? At this point is this just what we live with? Or is it worth injecting system instructions in ~/.claude ? submitted by /u/RaspberryNext
Originally posted by u/RaspberryNext on r/ClaudeCode
You must log in or # to comment.