Rubber Duck Debugging

A technique to debug an error: a developer explains an erroneous code line by line, step by step to a rubber duck (or human colleague or co-worker).

Thomas Rasshofer

Usually developers solve code problems by themselves this way, explaining it to the other and then solving it before the other says a word.

Discuss on Twitter
Edit on GitHub

About Dev Tips

This site was started by Thomas a few years ago and ever since, we published all kinds of tips, tricks, techniques, tutorials, and tidbits about what we know and love with the software developer community with the goal of helping others build, solve problems, and learn.

Our glossary attempts to explain terms and buzzwords often used in software development in a few simple words with the purpose of having explanations than can be easily referenced.

All articles are licensed under CC-BY-SA 4.0. Code snippets are licensed under MIT, unless otherwise noted. Thanks a ton to all authors for their awesome contributions.

You can find a list of all articles in our archive. If you’d like to contribute to this site, simply head over to its GitHub repository, fork it, make your contributions, and send a pull request.

© 2023 Dev Tips