I help adults solve problems in their code. I'm going to try this approach and see if it works in that context.
Hopefully it will. Although I guess in some cases the issue is reversed parameters to a function, or whatever, where the underlying knowledge is weak (or faulty).
Whenever I’m making a plan, or figuring something out, be it engineering or code or physics or whatever, I rubber duck - that is, I explain what I’m doing and why, verbally, in exhaustive detail, to nothing and nobody in particular (for I do not have a rubber duck), and ask questions of myself that a rubber duck would ask. I often catch a snag where I would otherwise have thought my scheme flawless.
Hopefully it will. Although I guess in some cases the issue is reversed parameters to a function, or whatever, where the underlying knowledge is weak (or faulty).
But it's certainly worth a try.