Help me, or not - rubber duck debugging
Why articulating a problem can instantly help to solve it?
Imagine this situation at work:
You: “Can I ask you a question?”
Colleague: “Sure in 15 minutes!”
You: “You can cancel the meeting…
Colleage: “Ok, but why?”
You: “I found the solution when preparing to explain it to you.”
This happens to me pretty regular when working on code…
Why you shouldn’t feel bad and why it happens?
A colleague pointed me to a Wikipedia article, an excerpt:
Many programmers have had the experience of explaining a problem to someone else, possibly even to someone who knows nothing about programming, and then hitting upon the solution in the process of explaining the problem. In describing what the code is supposed to do and observing what it actually does, any incongruity between these two becomes apparent.[2] More generally, teaching a subject forces its evaluation from different perspectives and can provide a deeper understanding.[3]
Post image: Unsplash.com
Send feedback!
