Rubber Ducking
Updated 2026-08-13
INTRODUCTION
English translation pending.
CORE DEFINITION
Rubber ducking means explaining code or a problem line by line to an inanimate object or an uninvolved colleague, whose comprehension is irrelevant to the outcome. The core proposition is that the act of explanation forces implicit reasoning into a linear verbal form, where gaps and contradictions become visible to the explainer. The key qualification is that the listener must not interrupt the flow: interjections redirect the reasoning and break the self-explanation effect that produces the insight.
SCAFFOLDING EFFECT
Reduce cognitive load
- Listener choice: pick an object or person who will not interrupt the explanation. - Line-by-line narration: state what each part does and what you expect it to do. - Contradiction log: note the moment the story stops making sense and investigate that point.
Anchor fast decisions
Implicit reasoning tolerates leaps, because the missing steps are never made explicit. Narration forces each step to be stated in order, so a step that cannot be stated becomes conspicuous. The listener contributes nothing; the gain comes from the translation from compressed intuition into sequential language.
MINIMUM ACTION
In progress 0/1Practice this model in one real situation:
account_treeGenealogyexpand_more
menu_bookReferencesexpand_more
Source support: Explicit
- en.wikipedia.orghttps://en.wikipedia.org/wiki/Rubber_duck_debuggingverified
PRIVATE NOTES · Only visible to you
SAVED Q&A
ENTRY Q&A · Private saving available
Ask with a clear boundary
thinkingmodels answers from published entry context only.
Your question is sent to thinkingmodels. The answer uses public entry context only.
RELATED MODELS