Search results
Results from the WOW.Com Content Network
In software engineering, rubber duck debugging (or rubberducking) is a method of debugging code by articulating a problem in spoken or written natural language. 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 ...
The book uses analogies and short stories to present development methodologies and caveats, for example the broken windows theory, the story of the stone soup, or the boiling frog. [6] Some concepts were named or popularized in the book, such as DRY (or don't repeat yourself ) and rubber duck debugging , a method of debugging whose name is a ...
Main page; Contents; Current events; Random article; About Wikipedia; Contact us
An example of a Japanese riddle used in the study: The thing that can move heavy logs, ... Rubber duck debugging; Principles of grouping; Katsu (Zen) Notes
This is a list of approaches, styles, methodologies, and philosophies in software development and engineering. It also contains programming paradigms, software development methodologies, software development processes, and single practices, principles, and laws.
Rubber duck debugging: Code debugging by explaining your code to a rubber duck. Quack! RTFM: Four letters that solve most problems. Rubber-hose cryptanalysis: Cryptography by other means. Scunthorpe problem: Spam filtering based on text strings can cause problems. Just ask the residents of S****horpe. Send Me To Heaven
Rubber duck debugging; Rule of three (C++ programming) Rule of three (computer programming) S. The Story of Mel; T. TPK algorithm; U. Heisenbug; W. Write once ...
"The name is a reference to an apocryphal story in which an unnamed expert programmer would keep a rubber duck by his desk at all times, and debug his code by forcing himself to explain it, line-by-line, to the duck." — Preceding unsigned comment added by 70.79.74.100 05:21, 13 May 2012 (UTC)