Can a Rubber Duck Really Solve Your Coding Bugs? Try This Simple Debugging Trick

Earlier I saw an article describing a programming master who always carries a small yellow rubber duck; when debugging, he places the duck on his desk and explains the problem and each line of code to it, which sparks insight.

Many of us have experienced a similar situation: we encounter a puzzling, strange issue, spend a lot of time thinking and debugging, yet the code seems fine. When we finally bring a colleague over and describe the symptoms and our steps, we often suddenly realize the cause and fix it, while the colleague hasn't done any work.

In fact, that colleague is the rubber duck from the article; the solution doesn't come from the colleague or the duck, but from yourself.

During problem solving, your thoughts are scattered; by describing the issue, your thinking becomes coherent, and you naturally organize the details, which often leads to a solution.

I have a similar habit: because I'm reluctant to speak, I write the problem description and thought process on paper or in a notebook, and it frequently helps me resolve the issue.

Therefore, I find the rubber‑duck debugging method very useful and recommend trying it; you can look for a personal “duck” that suits you.