Skip to content

Rubber duck debugging

← All terms · Software culture & jargon

Also called Talking it out, duck debugging

Explaining a problem out loud, step by step, often to an inanimate object, to notice mistakes that were easy to miss while thinking silently.

What it is

Rubber duck debugging works because speaking forces you to slow down and make each assumption explicit. The moment you explain the logic clearly, the bug or bad assumption often becomes obvious.

When you would use it

You use rubber duck debugging when you are stuck and need a different way to inspect your own reasoning.

Common operations

  • Debugging confusing logic
  • Checking assumptions aloud
  • Spotting missing steps in a process

Related terms

Where this is taught

No learning path uses this term yet. Browse the Learning Atlas for guided sequences through related ideas.