←back to thread

The highest quality codebase

(gricha.dev)
576 points Gricha | 3 comments | 08 Dec 25 21:33 UTC | HN request time: 0.794s | source
Show context
kderbyma ◴[10 Dec 25 01:59 UTC] No.46213171[source]▶
Yeah. I noticed Claud suffers when it reaches context overload - its too opinionated, so it shortens its own context with decisions I would not ever make, yet I see it telling itself that the shortcuts are a good idea because the project is complex...then it gets into a loop where it second guesses its own decisions and forgets the context and then continues to spiral uncontrollably into deeper and deeper failures - often missing the obvious glitch and instead looking into imaginary land for answers - constantly diverting the solution from patching to completely rewriting...

I think it suffers from performance anxiety...

----

The only solution I have found is to - rewrite the prompt from scratch, change the context myself, and then clear any "history or memories" and then try again.

I have even gone so far as to open nested folders in separate windows to "lock in" scope better.

As soon as I see the agent say "Wait, that doesnt make sense, let me review the code again" its cooked

replies(6): >>46232798 #>>46232866 #>>46232939 #>>46232955 #>>46233047 #>>46233145 #
1. rtp4me ◴[11 Dec 25 16:08 UTC] No.46233145[source]▶
For me, too many compactions throughout the day eventually lead to a decline in Claude's thinking ability. And, during that time, I have given it so much context to help drive the coding interaction. Thus, restarting Claude requires me to remember the small bits of "nuggets" we discovered during the last session so I find myself repeating the same things every day (my server IP is: xxx, my client IP is: yyy, the code should live in directory: a/b/c). Using the resume feature with Claude simply brings back the same decline in thinking that led me to stop it in the first place. I am sure there is a better way to remember these nuggets between sessions but I have not found it yet.
replies(1): >>46233244 #
2. mingus88 ◴[11 Dec 25 16:15 UTC] No.46233244[source]▶
Shouldn't you put those things you keep repeating into CLAUDE.md?
replies(1): >>46233287 #
3. rtp4me ◴[11 Dec 25 16:18 UTC] No.46233287[source]▶
Perhaps, but I already have a CLAUDE.md file for the general coding session. Unique items I stumble upon each day probably should go into another file that can be dynamically updated. Maybe I should create a /slash command for this?

Edit: Shortly after posting this, I asked Claude the same type of question (namely how to persist pieces of data between each coaching session). I just learned about Claude's Memory System - the ability to store these pieces of data between coding sessions. I learn something new every day!