| ▲ | the_af 3 hours ago | ||||||||||||||||||||||||||||||||||
> My favorite example is AI "getting tired" and "lazy" during long coding session Never seen this even once, nor anyone I know ever reported this. Do you have an example? | |||||||||||||||||||||||||||||||||||
| ▲ | nomel 3 hours ago | parent | next [-] | ||||||||||||||||||||||||||||||||||
First I saw it was Claude Opus 3.7. Had a very long back and fourth about some code, I pointed out an error, and Claude responded "That's what I get for programming at 2am", with the output being filled with "... code here ..." type shortcuts, basically no ability to one-shot a whole implementation anymore. The conversation length WAS reasonably into the 2am range, if it were real. Thought about it, did the statistical trick where I tell it to "have some rest, take a day off!" then immediately follow up with "Ready to continue?", with the next response having no shortcuts, with full implementation, and much better quality. These are trained on human text. This is the human norm, so I always find it interesting when human like behaviors, very broadly present in the statistics, come out like this. I also see it a little with Opus 4.7, with Claude Code, with the hint being much more terse planning text, that borderlines unhelpful. I put some "rest" in the context to push the latent space closer to what's in the statistics of the training data: a well rested human. | |||||||||||||||||||||||||||||||||||
| |||||||||||||||||||||||||||||||||||
| ▲ | rblatz 3 hours ago | parent | prev [-] | ||||||||||||||||||||||||||||||||||
I see laziness all the time, Claude will be helping me plan work and then it will ask me how a piece of code is implemented. I then have the choice of manually verifying how it works, or to tell it to look for itself. Ideally it would just look without being told. | |||||||||||||||||||||||||||||||||||
| |||||||||||||||||||||||||||||||||||