Do you have a Rubber Duck?

Debugging is a major aspect of being a software engineer/developer and there is a method of debugging which we do every day, but we are not aware of it…

This method is called rubber ducking.

Rubber ducking refers to a programming practice where a developer explains their code or problem-solving process to an inanimate object, often a rubber duck.

The process of explaining the code or issue helps the developer gain more insights and often leads to problem-solving.

This is what you do unknowingly. You start talking to yourself when you run into bugs.

Rubber ducking is a form of self-reflection and debugging (it’s a very good practice), where the act of explaining forces you to think more deeply about your code, identify the issue and come up with solutions.

The term originates from the idea that explaining the code to a rubber duck is as effective as explaining it to another person.

If you found value in this article, kindly share and follow me on twitter and LinkedIn.