From 8c2886631bfb782468501b191ec196196bdd8895 Mon Sep 17 00:00:00 2001 From: Bob Mottram Date: Fri, 18 Mar 2016 16:07:40 +0000 Subject: [PATCH] Rubber duck debugging --- entries/rubber_duck_debugging.txt | 3 +++ 1 file changed, 3 insertions(+) create mode 100644 entries/rubber_duck_debugging.txt diff --git a/entries/rubber_duck_debugging.txt b/entries/rubber_duck_debugging.txt new file mode 100644 index 0000000..53810d5 --- /dev/null +++ b/entries/rubber_duck_debugging.txt @@ -0,0 +1,3 @@ +rubber duck debugging + +Hackers can sometimes get hung up on particular coding problems or bug fixes. When this happens it can sometimes be useful to deploy the rubber duck debugging method, which is to explain your problem (or how you think the system should work) to someone else. If you don't have a willing accomplice then an inanimate object - such as a rubber duck - will do. The act of explaining or trying to teach someone forces you to think about the problem from different angles and so may lead to a breakthrough. This is related to developmental psychological and the notion of thought as subsumed language and language as a behavior regulation system. Defects and hangups in your language machine may become more obvious if you invoke it explicitly. \ No newline at end of file