Track · 2:30 · Liner note
The Duck Types Back
Rubber duck debugging means explaining a problem line by line to a silent listener so that describing the code exposes the mistake, and the title nods to duck typing, which judges an object by what it can do rather than by its declared type.
Explain the bug out loud, line by line, to something that cannot interrupt. Rubber duck debugging works because describing the code forces you to say what it actually does, and somewhere in the telling the assumption breaks. The Duck Types Back lets the duck reply, with a nod to duck typing, which judges an object by what it can do, not by what it is called.
Try it before you pull in a colleague. Write the question out in full, including what you expected and what happened instead. Half the time the bug is fixed before you press send.