# We've been nerfed! — retained record

> Retained reddit record from reddit:ClaudeCode.

Canonical: https://highsignal.app/data/records/dd221c4bb15007a5

[← sources](https://highsignal.app/data)


source: [reddit](https://highsignal.app/data/reddit) (reddit:ClaudeCode)  published 2026-11-08 17:43 ingested 2026-11-09 02:37

[original source ↗](https://www.reddit.com/r/ClaudeCode/comments/1xr488d/weve_been_nerfed/)

## retained text



```
(Sorry for the 10000th post, but more response = greeter outcome... Maybe?)

Noticed the nerf today, it's having some serious difficulty fundamentally understanding proper code implementation. As if it's unaware of 90% of my code base and just wants to spam quick patches all over.

I'll give an example from a few minutes ago:

**#1:**

We've got performance issues on my application due to re-fetching entries O(n\^2) multiple times in a single tick for our enemy AI in the game. Ok, I told Claude we need to cache the entries temporarily for the tick instead of constantly re-fetching them. Claude initially decides, let's permanently cache the entries and create some nasty memory hack (We're working with C++) in order to evict stale memory.

For reference, in order to see if the memory is stale (Since we hold a reference to it), you'd need a nasty tree walk on the enemies fairly complex goal system which is heavier than the original fetch.

Ok, terrible idea claude. But hey, I wasn't entirely clear to claude maybe it's my fault.

Now I tell claude, we only need to cache it for this current frame. Otherwise we'll need to manage lifecycle, which isn't worth the potential bugs and hacks.

No problem, Claude decides let's build a bunch of random ass structs and... Store all this cached memory in a series of global static vectors - with the enemy as the key..?  Then at the end of the frame, wipe the vector.

Whereas for me, a lazy developer, (And likely anyone else), I would have just stored the temporal data in the fucking enemy class it's self.. Obvious implementation? Something I already do with several other chunks of data - so this isn't a newfound concept in our project.

The little bastard just responds: "Yes, storing it on IEnemy is simpler and fits the existing code better. I over-engineered it. IEnemy already holds per-frame data that the reset loop clears every frame "

Moral of the story, make sure you review what this little thing is doing to your codebase.. I can't image the HORRORS people are creating unknowingly right now.

\#2:

Once more, Claude is seemingly talking excessively. Opus 5.5 mostly had this fixed before..?

It's so exhausting to read everything it says and usually it doesn't even present the problem.

It'll be like: "Me: What is 2+2?" - "Claude: If you take a number such as 2, and combine it with another number such as 2 you will get a result. You may also use a calculator to do this arithmetic operation for you. If you'd like I can code you a calculator?" (This is obviously exaggerated)
```



document fetched 2026-11-09 00:34 · canonical https://reddit.com/r/ClaudeCode/comments/1xr488d/weve_been_nerfed
