It's kind of interesting how genuinely hard it is to get models to deviate from basically all of these tropes. You can straight up tell it "I hate that card design, do something different, get creative!" and it'll do something either (a) ugly as sin (clearly just essentially a random walk through parameters) or (b) some same-y derivation of that card.

In coding, I've noticed a few tropes as well: everything is a "contract" or an "artifact" (clearly trained on like three decades of Java lol), everything is constantly "backwards-compatible" or "versioned" (even if working on a brand new greenfield project), and a few others.

▲

throwatdem12311 5 minutes ago | parent | next [-]

I’d rather they not deviate so I know right away that I can stop reading something because it’s slop.

▲

jkdufair an hour ago | parent | prev [-]

If claude says "load bearing" once more, I think I'll vomit.

▲

dieselgate an hour ago | parent | next [-]

That's a funny one. I don't use LLMs at all but "load bearing" is such a common/over-used internet joke for DIY building projects and stuff like "load bearing caulk". Have never heard it in a software sense really so am slightly perplexed

	▲	thewebguyd 33 minutes ago \| parent [-]
		> Have never heard it in a software sense really so am slightly perplexed It's been used in an ops context for a long time, pre LLM even. Same with "blast radius" has been a cybersecurity term for as long as I can remember.

▲

dvt an hour ago | parent | prev [-]

Hah, ChatGPT constantly says "that's real" or "less about X, more about Y."