4 ms·

Great approach. Being forced to wrap some words around your problem is really helpful. I didn't have a duck nearby so I recently talked to my hand during a chal

Great approach. Being forced to wrap some words around your problem is really helpful. I didn't have a duck nearby so I recently talked to my hand during a challenging adventure in threaded code. How often have you grabbed a colleague for help, gotten half way through explaining the problem, then said "Oh, I'm an idiot, I see the problem, nevermind." It also works for more abstract problems. If the rubber duck isn't your style, grab a notebook and a pencil then interview yourself on paper about whatever is giving you trouble. (life, career, relationship, motivation, inspiration, anything) I've had some great insights and ideas tumble out of this process – stuff I simply would not have thought of otherwise.

dekz 16y ago
I've only been programming for a few years, but this has to be one of the most successful methodologies I've added to my arsenal. Instead of an actual anthropomorphic figure, I use a chat window with someone. Mostly they ignore it, but I still type in that window what the code should be doing. More often then not someone might reply with "wtf why". Which is great because the duck in this case can provide feedback and thought. I know of a few places like THQ in Australia which promote this idea of rubber ducking. Also paper and pencil works well for when your only option is to printf debug (embedded devices with no support). I just hate those times when you've misunderstood the API and you expect certain functionality which isn't its actual defined functionality. You live, you learn.