forked from barryclark/jekyll-now
-
Notifications
You must be signed in to change notification settings - Fork 33
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
12 changed files
with
33 additions
and
40 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file not shown.
This file was deleted.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,24 @@ | ||
--- | ||
layout: default | ||
--- | ||
|
||
## The Rubber Duck Debugging Method | ||
|
||
1. Beg, borrow, steal, buy, fabricate or otherwise obtain a rubber duck (bathtub variety) | ||
2. Place rubber duck on desk and inform it you are just going to go over some code with it, if that's all right. | ||
3. Explain to the duck what your code is supposed to do, and then go into detail and explain your code line by line | ||
4. At some point you will tell the duck what you are doing next and then realise that that is not in fact what you are actually doing. The duck will sit there serenely, happy in the knowledge that it has helped you on your way. | ||
|
||
**Note**: In a pinch a coworker might be able to substitute for the duck, however, it is often prefered to confide mistakes to the duck instead of your coworker. | ||
|
||
*Original Credit*: ~Andy from lists.ethernal.org | ||
|
||
## FAQs | ||
- **If duck's are so smart, why don't we just let the ducks do all the work?** | ||
It would be wonderful if this were true, but the fact is that most duck's prefer to take a mentoring role. There are a few ducks however that do choose to code, but these are the duck's that nobody hears about because they are selected for secret government projects which are highly classified in nature. | ||
|
||
- **Where can I learn more about rubber duck debugging?** | ||
More information can be found [here](http://en.wikipedia.org/wiki/Rubber_duck_debugging) and [here](http://lists.ethernal.org/oldarchives/cantlug-0211/msg00174.html). | ||
|
||
- **Where can I hire my own duck?** | ||
Great question! [Amazon.com](https://www.amazon.com) hosts a wide selection of affordable ducks that have graduated with a technical degree from some of the world's leading universities. |