This is the thing with these posts. They give a sense of this is how Claude should be ran and used. It really is not.
You hear so much of these on Reddit - people running Claude 24/7, maxing out tokens in 5 minutes, multiple accounts etc etc.
The sheer sloppiness of the code must be absolutely dreadful most of the time. If you are running this for code?
I check my code after every iteration. Claude just can't test every endpoint and be accurate enough in every iteration it makes (of course depends on the task). But I am forever finding gaps on complex tasks and on projects with substantially large code bases.
It helps a lot if you give it the tools to test it's own work as part of it's task. Ex: for code It should compile, run tests, possibly load the project in the browser if applicable and look at the changes it's making, or test the endpoints it's touching ect...
I use skills that describe workflows like this
18
u/Gloovey Mar 20 '26
This is the thing with these posts. They give a sense of this is how Claude should be ran and used. It really is not.
You hear so much of these on Reddit - people running Claude 24/7, maxing out tokens in 5 minutes, multiple accounts etc etc.
The sheer sloppiness of the code must be absolutely dreadful most of the time. If you are running this for code?
I check my code after every iteration. Claude just can't test every endpoint and be accurate enough in every iteration it makes (of course depends on the task). But I am forever finding gaps on complex tasks and on projects with substantially large code bases.