[pmr_]

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.

[jeffclark]

When I'm working in a coffee shop or library or whatever, I do the same thing, but in an empty email.

Just writing out what I'm trying to do in a hypothetical email to someone who has no knowledge of the problem usually unties the knots in my brain.

[rmgraham]

In an office environment any co-worker can be a rubber duck for you. Of course, if all you can find are people who are knowledgeable about what you're working on, you may not need a rubber duck.

[steverb]

Please don't do this. If you can figure out the solution by explaining the problem to someone else, then you've just wasted the time of your co-workers.

At least take the time to sit down and write up a detailed explanation of the problem first. Do your due diligence before consuming the time of another developer.