Rubber duck debugging
source link: https://en.wikipedia.org/wiki/Rubber_duck_debugging
Go to the source link to view the article. You can view the picture content, updated content and better typesetting reading experience. If the link is broken, please click the button below to view the snapshot at that time.
Rubber duck debugging
Jump to navigation Jump to search
In software engineering, rubber duck debugging 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 themself to explain it, line-by-line, to the duck.[1] Many other terms exist for this technique, often involving different (usually) inanimate objects, or pets such as a dog or a cat. Desk check your code is the original term for this technique.
Many programmers have had the experience of explaining a 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.[2] More generally, teaching a subject forces its evaluation from different perspectives and can provide a deeper understanding.[3] By using an inanimate object, the programmer can try to accomplish this without having to interrupt anyone else.
In popular culture[edit]
Insights are often found by simply describing the problem aloud.
— Duck, Quack Overflow
On 1 April 2018, Stack Exchange introduced a rubber duck avatar on their websites as a new feature called Quack Overflow. The duck appeared at the bottom right corner of the browser viewport, and attempted to help the visitor by listening to their problem and responding with a solution. However, the duck merely produced a quack sound after apparently thinking and typing. It referenced rubber ducking as a powerful method for solving problems.[4] Some confused visitors seeing the duck for the first time thought that a malware program had been installed in their computer before realizing it was an April Fools' Day joke.[5]
See also[edit]
References[edit]
External links[edit]
Recommend
-
78
Told my sister about the rubber duck method ages ago, got this for Christmas yesterdayChevron Pointing Right
-
27
The “Rubber Ducky” by Hak5 is a very powerful tool that lets the user perform rapid keystroke injection attacks, which is basically a fancy way of saying the device can type fast. Capable of entering text at over 1000 WPM, Mavis...
-
73
Did you know you can measure an unknownmass with arubber band? You pretty much can. The first thing you should do with any project is to play. So, go get a rubber band and play with it. Wha...
-
70
README.md Cuberto's development lab: Cuberto is a leading digital agency with solid design and development expertise. We build mobile and web products...
-
76
README.txt _ _ _ USB _ _ _ __(.)< __(.)> __(.)= Rubber >(.)__ <(.)__ =(.)__ \___) \___) \___...
-
15
Taking too much slack out of the rubber band Of late, I keep hearing more and more about elastic this and elastic that. People use it in order to "right-size" their services, and only run the number of instances, pods, or whateve...
-
9
That lovely smell of burning plastic and rubber Back when I used to work for a school district, I may have supposedly been their Unix sysadmin, but I wound up dealing with a great many other things. One of them was a lot of deskt...
-
9
Code reviews with a rubber stamp
-
10
The art of Rubber Ducking or Rubber Duck Debugging Sponsored By It works. Really. "Put a rubber duck on your monitor and tell it how the code is supposed to work."
-
8
Episode 512: Tim Post on Rubber Duck Debugging...
About Joyk
Aggregate valuable and interesting links.
Joyk means Joy of geeK