← Back to context

Comment by hgomersall

10 hours ago

Ha, yes! A few times I've had a back and forth with Claude about why software X isn't working as I expected it to, with Claude coming up with more and more ludicrous explanations, and in the end I say, "just go and read the code", and it remembers it can do that and goes and does it and then finds the bug, or the weird UX design or whatever. It's really helpful.

i have the opposite problem, sometime i tell it to read the doc/header to understand how to use API, but then it proceeds to dive into the SDK to read the source, which is not a bad thing but that takes both time and a lot of token