Re:Why You Shouldn't Interrupt a Programmer
by Maxious on Monday October 28, 2013 @05:31AM
(#6625963)
This is a common technique in engineering troubleshooting http://en.wikipedia.org/wiki/Ishikawa_diagram http://en.wikipedia.org/wiki/5_Whys
[ Parent
| on HN ]
Re:Why You Shouldn't Interrupt a Programmer
by calineczka on Monday October 28, 2013 @05:36AM
(#6625977)
I never thought about it as something that can have such fancy name and such broad engineering application. I think my technique is like 1% of what Wikipedia describes.
The old "So you want to be a success at selling?" training video starring John Cleese has a wonderful example of (roughly) the Five Whys applied to sales.
(It can be seen at http://www.videoarts.com/sales-and-negotiation/so-you-want-t... at 15:15 , but alas only after registration now.)
Re:Why You Shouldn't Interrupt a Programmer
by MortenK on Monday October 28, 2013 @12:16PM
(#6627804)
Ishikawa diagrams and the 5 whys are quality control tools, specifically root cause analysis tools.
What OP mentions is taking notes of his though process as he goes along, so he can jump back in after an interruption.
Re:Why You Shouldn't Interrupt a Programmer
by gmt2027 on Monday October 28, 2013 @06:55AM
(#6626228)
This is the kind of revelation that brings me back to hacker news!
Re:Why You Shouldn't Interrupt a Programmer
by rikibro on Monday October 28, 2013 @09:18AM
(#6626675)
Wasn't the latter inspired by kids?
https://www.youtube.com/watch?v=BJlV49RDlLE