upvote
Yes, I had a related experience of reading a book and observing what I thought were claude-isms, only to realize it was written in 2019. Some of the common tells are actually good writing practices, but I guess they are best in smaller doses.
reply
Sure, that's where the AI got them: the training data. These phrases and cliches were very prevalent especially in corporate "white papers" and memos and marketing materials. There was a time when "stove pipe" was a common one too, along with "silo."

But the LLMs really seem to fixate on using the same ones in the same places all the time. I guess that's because that's the highest probability construction.

reply
This is exactly why humans invented the idea of things going in and out of style.
reply
Actually, AI was learning these 'AI-isms' even back in 2017/2018 (probably even earlier). I think a lot of people who just jumped on the imaginary AI bandwagon more recently don't realise the mannerisms AIs are adopting are not really new. At some point the bleed between 'you' or 'you' and AI will just become so transparent it will be obliterated, more likely than not.
reply
I believe you and OP are in agreement — they were saying that the 2019 book had them, therefore the terms _do_ predate AI. Your point that AI was being trained on material than is load-bearing (lol) but in agreement with OP, not contradictory.

Only mentioning because your "actually" may imply you thought you were disagreeing, when in fact it's one big happy family!

reply
I wrote a thank you message on Teams to my coworkers on a project, and half of them thought I had used AI to write it. As a professional writer in a previous life, I was astonished. Then they told me that they had never seen me write anything more than a sentence or two so naturally they assumed something relatively polished had to be AI assisted.
reply
Though I haven’t been a professional writer, I’ve been a good writer with an expansive vocabulary since high school where English was my best subject despite being a STEM maven. I hate the fact that what was previously considered an advantageous skill is now a millstone in public use. I hate having to dumb down and self—censor in order to avoid being accused of using (or being) an LLM. Even though my writing has a few repeated personal tells - certain linguistic errors that I nevertheless employ as part of my idiom (and an LLM never would) - people don’t always notice them. So, I’m forced to change my voice to deal with what’s essentially an IRL Captcha.
reply
When I write these days, I am more aggressive in using "I", so it's clear it's my own voice. Generally, an LLM is less prone to self-reference like that unless it's prompted to, I guess.
reply
Good advice though too much “I” can sound a little self-centred to my ears.

If/when AGI arrives I assume this tactic will stop working.

reply
unfortunately load bearing is one of those things that became a claudism but has been part of my daily lexicon for decades. There are a lot of things I say regularly as part of my own vocal quirkiness that now I have to self censor.
reply
I've used it since that simpsons episode

"it's a load bearing poster..."

reply
I'm pretty sure that's not the source for me but most of my vocal quirks have origin stories like this so it's entirely possible. They're almost always things that I heard which either amused me or I thought sounded cool at the time and just stuck with me.
reply
Stories like this make me want to use each AI at least briefly, so I know what to avoid writing/saying. Or maybe just do a search every couple months to find out what different AIs are known for saying too often.
reply
Or if confronted just say you were using it first, and Claude must have copied you.
reply
The one Claudism I will never ever use is "synthesize". I don't even know where that came from - no one talks or writes like that - "I can synthesize that for you".
reply
I had a similar experience, only, I was my natural way of talking.

e.g. one pattern I had/have is

<scope problem> the good news is <solution by way of analogy> is aviliable. The <constraint/requirement> is loadbearing though, ...

a near automatic script I rattle off in discussions/consults. When you solve similar problems several times, you figure out what works for communicating things you stick with it and you recycle/polish.

problem is, when for whatever reason, that pattern ends up as part of the core statistical distribution a model uses. You could royally fuck ones life up if working for a "frontier" lab, by simply finding a person with an acceptable speech rythem and cloning it, making it synonymous with ai slop. you'd destroy that persons image every time they open their mouth without them realising it. I for one started randomly getting quite hostile reactions from software devs who would be exposed to more llm putput than others.

Imagine an AI lab steals your voice, and uses it to scam call folks all day. Now, every time you call anyone, you are met with an immediate hangup. you'd have to put on a fake voice just to get the call to stay connected.

I love ai, and what it promises excites me, but as usual, humanity has a way of taking a cool tool and fucking it up royally. maybe the solution is to simply pepper slurs into everything one writes to blacklist ones content from training.

reply
Claude's affected my language in two ways. one is that, for a long time, Claude in particular responded more to feedback if I swore at it, which caused me to swear at it more. this vicious cycle generalized to the point where I now have to consciously remind myself not to swear when doing something as simple as buying a coffee or asking somebody what time it is. it was difficult to even write that sentence without throwing in an F-bomb just to emphasize the silliness of the problem.

anyway, the other way is I found it's helpful when prompting LLMs to use the same "it's not delivery, it's DiGiorno's" pattern that they're all so obsessed with. especially when the thing's misapprehended some concept, so you need to clarify. this hasn't yet generalized from the fake "conversations" I have with chatbots into my conversational style out in the real world, but the risk is fully there. (it's not an inevitability -- it's an occupational hazard.)

reply
It's good to know that Claude knows its place then. By contrast, I have to watch myself with Siri, because calling it the *&^#@$ it is seems to trigger refusal a lot of the time.
reply
“Now the only coworker who will sit with me at lunch is Claude. Alice, what do I do?”
reply