Now, hear me out: what if the rubber duck burned tons of energy, poisoned the water and air, caused a global shortage of computer parts, was built with material without the permission of creators, made it easy to make nonconsensual sexual images of people, and lied to you?
post
Not a programmer but at my last job I couldnt count how many times I would walk into our engineers office and start explaining a problem only to stop mid sentence and say "wait, I'm an idiot" then walk back out. Sometimes talking about it is all you need to make the pieces fit.
works even for non programming stuff. its letting our brain process the information in order ans organising it
Yeah. I'm no programmer but I've had it often that I couldn't find a solution for a problem myself, said 'fuck it, I'll have to ask the internet', and by writing out what my problem was I figured out the solution so I never even posted the half-written posts lol
I write a lot of notes, because I can't trust myself to remember details of any project after a day or more of hopping through multiple other tasks and online information onslaught. This particularly concerns any problems on which I get stuck — and whaddayaknow, writing out what specifically doesn't work and how it should work, helps with realizing why it might not work.
This happens so often with my wife that she’s started saying “quack” when I figure it out
this is one reason I type questions out before asking them
came to say this and in addition its more effective with an actual person even if they don't say anything. Even a small amount of feedback helps that much more although ironically though it kinda palteus if it stops you from jumping on your new ideas and getting them down.
Works with writing fiction, too. I read the section aloud and explain the reasoning behind the choices, and that helps me figure out what isn't quite working. Also, reading aloud makes awkward dialog stand out more so than reading silently.
This is why I put rubber ducks at all desks of my it colleagues. It helps.
It might have escalated a bit after that though. There are hundreds of rubber duckies all around the office now...

Every single popcorn flick from the 80s and 90s has a main character make a big plot-resolving realization while doing early act 3 exposition
If this is such a universal human experience that we wrote it into movies made for general audiences, I think that programmers are not the only ones debugging to their ducks
I call one of my coworkers once a week with "Can I rubber duck you?" which means I'm just going to talk about my problem and explain my thought process in hopes she spots an obvious solution.
We do it to each other and 30% of the time the other dev says "why not just X" and we agree that it's pretty obvious.
I do this to my main analyst as a last resort; have since day 1.
"Sorry, I gotta rant this one out." Knowing full-well they have nfi what I'm going on about.
Then eventually, that feeling of a clarity bomb going off followed by a period of dopamine fallout.
My wife is my rubber duck. She doesn’t mind when I explain the most jargon-heavy stuff to her.
A corollary to this is that it's often very difficult to explain what's wrong because if you could explain it clearly, you would probably be fixing it already.
it is the process of explaining how your code works (or should work) to someone that you realizes the errors or solution.
I used to teach design. Before a presentation, I always asked my student to explain their project to someone with no knowledge on the subject, like their grandmother or so. Mainly to discover the logic flaws in their presentation.
I have a few Lego kits my kids have gotten me, and a small toy penguin, which I talk through things with.
Thankfully it looks like I'm just on camera. Though I work from home so it doesnt really matter.
I also treat several coworkers like my rubber ducky. I warn them first though, so I feel like its not as bad.
Do you squeeze them until they squeak?
Not quite the same, but sometimes when I’m doing a task I like to talk through what I’m doing out loud as if I was showing someone else how to do it.
Hell, even just having a completely different conversation can sometimes lead to huge breakthroughs! I've seen it happen!
But isn't that well known, even from school days? If you've ever explained something to someone you've recognized that by doing that you're forced into overthinking the context, diving deeper into the subject.
Sure, teaching is one of the fastest ways to learn.
Also see SoDoTo. See one, Do one, Teach one.
https://www.eclathospitality.com/blog/career-management/use-the-sodoto-method-to-learn-anything
Also going for a walk, driving, or the other morning I woke up spontaneously about 2 hours early and come up with a solution.
Prolonged and energetic walks jolt my brain so well that I have a standing task of maybe finding a way of recording audio clips right from the lock screen of my phone. Unfortunately, I know for certain that this will result in a pile of said clips collecting on the phone, as sorting them into notes isn't a priority once I'm back home.
The Feynman method
fun fact, I used to do this and had a small mental breakdown because my piece of shit boss refused to listen to my solutions, ultimately causing me more work and stress because the solutions he forced me to implement failed even more spectacularly.
I burned the duck as an effigy of my boss when he was finally fired.
I will never have another duck.
I feel like you burned the messenger, somehow.
I do this, but with my half-naked anime figures.
This has a name? I thought this was just how it works. It’s why we think out loud.
eta: thinking + speaking + hearing engages more of your brain. That’s obvious, right? More engagement == more connections?
The Feynman method is another name for it. Thanks to PennyRoyal@sh.itjust.works for this info.
I don't know who initialyse selected the rubber duck as a symbol for that. But it can't be a coincidence that the method works even better for me while showering.
(Although with that, the energy costs might rival that of AI use)
If rubber ducks are a sign of bugs, then I do not want a Jeep.
Haha! But imagine how many programming problems some Jeep owners could debug all at the same time!
The first time I saw one of those rubber duck heavy Jeeps, I wondered if they were a C++ programmer or something.
Edit: And for anyone unaware - the origin is super adorable. https://en.wikipedia.org/wiki/Jeep_ducking
Isn't that just brainstorming?
No. Brainstorming is when you’re with a group and everyone is throwing out ideas unfiltered.
Rubber duck debugging is when you are trying to solve an issue by describing your problem to another person (or a rubber duck) and through the act of describing the problem you gain a better understanding of the issue and often this causes you to get a ‘eureka moment’ where the solution is suddenly clear to you.
I mean in my line of work that is the collaboration process. Our problems are not in "debugging". However it's real solutions to problems. We discuss ideas and execute the one we feel is best. Quite often these discussions create that moment you speak of. Perhaps it's nuanced to programming.
No, it isn't nuance. You are describing a completely different part in the process.
Rubber ducking is after you decided on a solution to a problem that you know should work but it isn't working the way you expect. "Why isn't the change I am making doing the thing? It works on the other site and oh shoot I forgot to add in the workaround for our goofy environment."
I’d say brainstorming is what you do before writing code and rubber ducking is what you do to debug code that you’ve already written.
They also work kinda differently. Brainstorming an idea is different from explaining it out loud, detail by detail.

all 63 comments