Rubber duck debugging
Rubber duck debugging, rubber ducking, and the rubber duckie test are informal terms used in software engineering to refer to 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 his code by forcing himself to explain it, line-by-line, to the duck.
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. By using an inanimate object, such as a rubber duck, the programmer can try to accomplish this without having to involve another person.
- Teddy bear programming
- Confessional debugging
- Rubber plant debugging
- Cardboard programmer or programmer's dummy or cardboard colleague
- Cone of answers
- Thinking out loud
- Frog debugging
- "Rubber Ducking", Portland Pattern Repository, C2.
- "The Rubber Duckie Test", Technically Speaking, Google, Mar 2009.
- 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.
- The Practice of Programming
- Bolboaca, Adrian. "Teddy bear pair-programming". Retrieved 2014-05-28.
- McConnell, Steve. "Code Complete, First Edition". Retrieved 2012-08-20.
- "Cardboard Programmer", Portland Pattern Repository, C2.
- "Cone of Answers", Portland Pattern Repository, C2.
- "Thinking out Loud", Portland Pattern Repository, C2.