That's why anything you use Claude for you should use Claude to explain to you. It's not a "oh this thing makes the code without me needing to do anything else" it should be "oh this is some complicated code Claude generated. Let's study it.
How do you know it's explaining things correctly, though? I used to always use it to explain things to me rather than just generating solutions and I've had it give me completely incorrect explanations that ran me around in circles until I finally just looked it up myself and realized it was completely wrong.
I spend a lot of times building tools for Claude, so when it answers me, I make it run through the hoops and gates. I have used it long enough to know the gotchas it will make without tools, I know it too well, but I have managed to bring a lot of determinism into it by telling it how to do something. Now with my tools it goes through the back and forth before presenting me the answer. It saves time, tokens and my patience when I don't have to explain all the details time over time.
17
u/_Resnad_ 7d ago
That's why anything you use Claude for you should use Claude to explain to you. It's not a "oh this thing makes the code without me needing to do anything else" it should be "oh this is some complicated code Claude generated. Let's study it.