debugging duck
/dɪˈbʌɡɪŋ dʌk/
CommonAn inanimate object (classically a rubber duck) used as a sounding board when talking through a bug out loud.
Can refer to the literal rubber duck, the practice itself, or any object or person used as a passive listener. Sometimes used affectionately when a teammate just sits and listens without speaking.
Real-world examples4 examples
| # | Example | What it means | Source |
|---|---|---|---|
| 01 | spent 2 hours on this bug then explained it to my rubber duck and fixed it in 5 minutes | The act of explaining out loud immediately revealed the bug. | x, 2023 |
| 02 | can you just be my debugging duck for a sec? don't say anything, just listen | Asking a colleague to silently listen while you talk through the problem yourself. | reddit, 2024 |
| 03 | my rubber duck has seen more of my bugs than any senior dev ever will | The duck is the first thing consulted when something breaks. | tiktok, 2024 |
| 04 | okay i'll just rubber duck this one, brb | Going to talk through the bug alone before asking for help. | x, 2023 |
Use it when
- You are stuck on a bug and explaining it to an object or a colleague who says nothing.
- You solve your own problem mid-explanation before the other person responds.
- Describing the rubber duck debugging technique to someone unfamiliar.
- Joking about talking to yourself or an object while coding.
Do not use it when
- You mean pair programming where both people actively contribute.Use “pair programming” instead.
- You mean a code review.
Variations and related forms
Origin and context
Popularized by the book The Pragmatic Programmer (1999), which described explaining code to a rubber duck as a debugging method. The term spread into general developer culture over the following two decades.
- First seen
- 1999
- Confidence
- high
Cite this page
Use this stable URL to reference the entry.
https://slang.fyi/debugging-duckUpdated: 2026-08-29License: CC BY 4.0