Rubber ducking is the unexpected superpower for software engineers

Earlier this week I had a one-on-one with a team member. He was stuck. Thoughts all over the place. So I mentioned rubber ducking. To my surprise… he had never heard of it. That got me thinking. If this simple but powerful trick is still unknown to many, it’s worth sharing.

Rubber duck

So let’s dive into what rubber ducking is, why it works, and how you can use it in your daily work. 💡

What is rubber ducking?

The term comes from The Pragmatic Programmer by Andrew Hunt and David Thomas. The idea is simple: explain your problem to a rubber duck (or any object on your desk). By talking it out step by step, you often unlock the solution without needing anyone else.

Why does rubber ducking work so well?

  • 👉 Clarifies your thoughts
    Talking it through forces you to structure your thinking.

  • 👉 New perspectives
    Explaining makes you look at the problem from a fresh angle.

  • 👉 Reveals mistakes
    Saying things out loud can expose gaps or errors you missed.

How to apply rubber ducking

  • 👉 Step 1. Identify the problem
    Be clear on what you’re actually stuck on.

  • 👉 Step 2. Explain it to your duck
    Go step by step, as if you’re explaining to a colleague. Leave nothing out.

  • 👉 Step 3. Notice insights
    Pay attention to those “aha” moments that come mid-sentence.

Practical tips for better ducking

  • ✅ Take your time. Don’t rush the explanation.

  • ✅ Be thorough. Even the obvious steps matter.

  • ✅ Use a real rubber duck. It sounds silly… but it works.

  • 🤖 Or use my GPT: The Reflective Rubber Duck. A virtual duck that listens to you 24/7.

Closing thought

Rubber ducking is simple. And that is the beauty. Whether you’re debugging code, designing a feature, or just stuck in a loop… talk it out. You’ll be surprised how often the answer is already in your own words.

Have you tried rubber ducking yourself? Or do you use another quirky problem-solving trick? Slide in the DM on my socials!