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.
This concept is also known as "Talk to the Bear".
Read more about Rubber Duck Debugging: Similar Terms, See Also
Famous quotes containing the words rubber and/or duck:
“The idea that information can be stored in a changing world without an overwhelming depreciation of its value is false. It is scarcely less false than the more plausible claim that after a war we may take our existing weapons, fill their barrels with cylinder oil, and coat their outsides with sprayed rubber film, and let them statically await the next emergency.”
—Norbert Wiener (1894–1964)
“Here is no eft or mortal snake
But only sluggish duck and drake.”
—T.S. (Thomas Stearns)