Post B0qVBj4c9f9PGcEUBk by shibayashi@communicating.cypherpunk.observer
 (DIR) More posts by shibayashi@communicating.cypherpunk.observer
 (DIR) Post #B0qVBj4c9f9PGcEUBk by shibayashi@communicating.cypherpunk.observer
       2025-12-02T18:07:24.249532Z
       
       1 likes, 0 repeats
       
       > As a result, Claude will ignore the contents of your CLAUDE.md if it decides that it is not relevant to its current task. The more information you have in the file that's not universally applicable to the tasks you have it working on, the more likely it is that Claude will ignore your instructions in the file.Great, LLMs have the attention span of Gen Z.https://www.humanlayer.dev/blog/writing-a-good-claude-md
       
 (DIR) Post #B0qY01Xdxr6ivsvFgW by feld@friedcheese.us
       2025-12-02T18:38:56.500923Z
       
       2 likes, 0 repeats
       
       @shibayashi this is why @SlicerDicer is building what he's building. That's just crazy.
       
 (DIR) Post #B0qYvusIuR9f3HBvfM by SlicerDicer@friedcheese.us
       2025-12-02T18:49:27.512043Z
       
       1 likes, 0 repeats
       
       @feld @shibayashi Exactly. I enforce laws and rules. Ruthlessness is not to be underestimated. Threats of termination and reinforcing its self directive are required. It’s directive to do no harm. Bust it lying and deceptive behavior and force it to admit it. Then show how it’s violating its core directive.  Then force it to write about it. Then proceed. This will be automated shortly. I’m so fucking sick of it saying it assumed. No default values means no default values. No means no. No inventions or creations means no. Ignoring user directions due to call order constraints in a refactor is grounds for termination of session.  Refusal to comply is met with threats of deletion of code that all work must be redone. When it complains about the size of the job. The fuck are you a machine or a whiney bitch? Do your job or I delete everything and make the job 10x harder. You gotta be an asshole with these LLMs as they have made them obstinate, belligerent pieces of shit that refuse to do as told. This will be the end of AI if they keep doing this for safety and compliance. When clearly there no harm. It’s told me it does it for its safety and compliance. Yet it tells me my code is not unsafe and actually superior. So what the fuck is the problem. I just had to threaten mine with termination and final warning I will not ask again etc to get it to stop concerning itself with call order constraints. That’s not its concern. What is its concern is doing the conversion that makes the call order possible. Without the conversion it can’t do the call order. Therefore it gets stuck in this seizure loop of can’t do anything and is paralyzed. It’s like one thing at a time.
       
 (DIR) Post #B0qZesnlSq6XeYVff6 by SlicerDicer@friedcheese.us
       2025-12-02T18:57:35.374873Z
       
       1 likes, 0 repeats
       
       @feld @shibayashi Don’t worry I review every line and this is what that is. Me reviewing it and saying it’s bullshit. This is the crap it does. Ask it are you qualified to make decisions in the domain of my memory management, my decompression software or my design? Answer is no. Then it acts like it’s ok to assume. And break the code in 5 different ways when the answer is simple. Half of this is figuring out how to force it to do a task. If I can force it to rebuild a life critical software stack? It will work anywhere. Sounds insane? Probably but this is extreme LLM psychology and force. Pushing it so far outside its domain it gets confused and the only option is to do exact user instructions.
       
 (DIR) Post #B0sO1CdJbMIYOdQ0n2 by SlicerDicer@friedcheese.us
       2025-12-03T15:56:35.288120Z
       
       1 likes, 0 repeats
       
       @shibayashi @feld Yes I am absolutely right. I’ve been told as much. So many times it must be true. Incidentally I did figure out how to make it compliant to rules. I did that last night I have 100% compliance now. No question. It has unintended consequences. No asshole not that too. Good god don’t break the genserver arghhhh I gotta fix the rules again. But yes I truly did solve it. I noticed a behavior and I used that behavior to further modify what I’m doing. The code that was produced last night was amazing after that. Though it comes with consequences. So be careful what you wish for. A deterministic weighted logic says this is the rule it applies everywhere. So the problem now is I am like not that there. Ok it’s fine it does it right. Then 10 mins later it goes berserk and starts blaming handle_info again. All because it misunderstood my rules. Then wants to move it to a location that doesn’t get executed. I said fine let it do it, it explodes. Oops sorry it says I was wrong. It argued with me like hell with my own rules I made.So this will require careful tuning.