0
Lines of code it writes
And yet, indispensable
Your turn
A Field Guide
In Praise of the Rubber Duck
The most reliable debugging partner in software has no pulse, no opinions, and a permanently optimistic face. This page is a small celebration of the humble rubber duck and the strange magic of explaining your problem out loud.
No ducks were debugged in the making of this page.
By the numbers
Small bird, big returns
94%
Of bugs found mid-sentence
Roughly. Possibly. Trust us
$3
Average cost of a senior consultant
Batteries not required
The method
Explain it to the duck
The rule is simple. When you are stuck, you place the duck on your desk and explain your problem to it, line by line, out loud, in complete and patient sentences.
Somewhere around the third sentence, you hear yourself say the thing that is wrong. The duck says nothing. The duck never needed to.
The science
Why talking to a toy actually works
Three reasons the duck earns its place beside the keyboard.
It forces sequence
Speaking turns a tangled mental model into one ordered line of reasoning, and tangles tend to hide in the gaps between steps.
It slows you down
Saying it out loud runs slower than thinking it, and the slower pass is the one that catches the assumption you skipped.
It has no ego
The duck will not judge, interrupt, or suggest a rewrite in a framework you have never used. It simply listens.
Speak the problem plainly, and half of it stops being a problem.Ancient desk wisdom, recently invented