I did a grep for load-bearing in our codebase and it now appears hundreds of times. I'm actively starting to hate Opus because of this shite. It's just infuriating to read now.

▲

Bluestein 14 hours ago | parent | next [-]

"You are absolutely right to push back!" ...

I am really really really trying to wrap my head around this. I am of course first discarding the obvious: "more tokens used is simply more tokens burned ..."

... read somewhere that it is partially a result of Claude now wanting to be ready for longer, more complex, mutli-step work. And this verbiage is the result.-

Whatever it is, they've got people begging for 4.6 back (wrt tone).-

▲

fluidcruft 14 hours ago | parent | prev | next [-]

I mostly hate that it spits out this gibberish and then sees its own gibberish and argues about things in gibberish with itself to then tell me that it thinks it's maybe a bad idea to do the simple task that I told it to do (which is very much not a bad idea, I just don't feel like typing out the whole goddamn plan to justify refactoring when I know the refactoring is the point)

	▲	okwhateverdude 13 hours ago \| parent [-]
		Tell it that. Seriously. "Shut the fuck up and do what I say. Don't think about it. Don't go spelunking through the code base. I've already given you all the context you need." I've needed to start doing this because otherwise, it wants to `find /` and grep its way across my system for everything. I've got one project where I force certain complete documents into context, specifically to avoid it trying to grep around and only load partial chunks. It will still want to go do that grepping of those documents for some reason.

▲

ViewTrick1002 14 hours ago | parent | prev [-]

Based on the plans I’ve had Claude write since February, “load-bearing” first started appearing in early May.

	▲	latentsea 13 hours ago \| parent [-]
		It has gotten to the point where I'm now having to add a linter into our codebase to keep Claudism's out of it because there's literally hundreds of instances of "load-bearing" that have crept into the codebase, and that show up in tickets and PR descriptions etc. From now on I'm just going to make that fail the build. Fuck this noise.