Rubber duck debugging
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. Many other terms exist for this technique, often involving different inanimate objects.
Many programmers have had the experience of explaining a programming problem to someone else, possibly even to someone who knows nothing about programming, and then hitting upon the solution in the process of explaining the problem. In describing what the code is supposed to do and observing what it actually does, any incongruity between these two becomes apparent. More generally, teaching a subject forces its evaluation from different perspectives and can provide a deeper understanding. By using an inanimate object, the programmer can try to accomplish this without having to interrupt anyone else.
- Code review
- The Aha! effect
- Pair programming
- Socratic method
- Software walkthrough
- Think aloud protocol
- The Pragmatic Programmer: From Journeyman to Master. Addison Wesley. ISBN 978-0201616224. p. 95, footnote.
- Baker, SJ, The Contribution of the Cardboard Cutout Dog to Software Reliability and Maintainability.
- Hayes, David (25 June 2014). "The Psychology Underlying the Power of Rubber Duck Debugging". Press Up. Retrieved 3 July 2015.