Hello fellow Programmer, have you ever experienced resolving your debugging problems while you explain it to someone else? If yes, we call this process as “Rubber Ducking”

It’s a very simple but practically useful technique for finding the cause of a problem by simply  explain to someone else. Why it works? By explaining the problem to someone else may help you to gain new insights to the problem.

The act of Rubber Ducking is explained in the book, “The Pragmatic Programmer”

The other person should look over your shoulder at screen and nod his head or her head constantly (like a rubber duck bobbing up and down in a bathtub). They Don’t need to say any word; the simple act of explaining step by step, what the code is supposed to do often causes the problem to leap off the screen and announce itself.