In software engineering, rubber duck debugging or rubber ducking is a method of debugging code. The name is a reference to a story in the book The Pragmatic Programmer in which a programmer would carry around a rubber duck and debug their code by forcing themselves to explain it, line-by-line, to the duck.[1] Many other terms exist for this technique, often involving different inanimate objects.
Mom: “Who are you talking to, down there?”
Kid: “Noone, Mom!”
Mom: “Well I can hear you talking to someone. Should I call a doctor?”
Kid: “It’s noone, mom, just my rubber duck.”
Mom: “Oh, now I am going to call the doctor! You haven’t spoken to that duck since you were a little baby.”
Kid: “It’s okay, Mom. I’m debugging.”
Mom: “Then I need to call an exterminator!”
Kid: “I’m debugging my program!”
Mom: “You mean you’re talking to the TV?”
.
.
.
TBC
