Rubber Duck Problem Solving

After reading Ridiculous Fish's version of this (http://ridiculousfish.com/blog/posts/The-app-that-was-fixed-...), I use a mental version of Dr. House.

It's worked out a couple of times... "How can the process have failed when the logs indicate success?" "Everybody lies." "Oh, so maybe the log is written at some point before the process actually finishes?" "Treat with steroids."

I've been the duck.

Years ago when I was doing tech support a fellow on Long Island would call up and start explaining his problem--at a rate of speech that made me get out of breath listening. Usually, about 3 minutes into the call he'd arrive at the answer that had been occurring to me, thank me, and hang up.

I sometimes do this while writing an essay. I simply imagine I'm talking to someone about the topic and when something good comes out of my mouth I write it down.

I remember reading the term for the first time in The Pragmatic Programmer by Hunt and Thomas. They give the experiences of one of the authors as the origin of the term, but I would really be interested where the term was used the first time. Personally, I'm sticking with the technique ever since. Although I've never managed to use it in an office environment with other people. I don't know if this is caused by the environment or if it simply feels too awkward to me.

I know a number of project managers who read Jeff Atwood's blog intently. I really hope they don't go out and buy stuffed animals and put them in meeting rooms so people can ask the animal questions. Unfortunately, I think some will.

The theory is definitely sound, but simply saying "phrase your question in an email to me, making sure to be detailed" should suffice. Talking to stuffed animals is probably unnecessary!