Rubber Duck Debugging | Prepsa Kayastha | Gurzu

Do you like debugging?

Rubber duck debugging is a programming and debugging technique in which a programmer explains their code or problem to an inanimate object, often a rubber duck. The idea is that by verbalizing the code and the thought process behind it, the programmer can gain a better understanding of the logic and identify any errors or issues.

In this episode of knowledge ketchup, Prepsa talked about why, how and when to use Rubber Duck Debugging.

www.gurzu.com

Transcript

1. Do you like debugging?
3. Do You Have A Rubber Duck? The Power of Rubber Duck Debugging
4. • A debugging technique in which you explain your code or problem to someone else or an inanimate object, like a rubber duck • First introduced in the book ‘The Pragmatic Programmer’ by Andrew Hunt and David Thomas RUBBER DUCK DEBUGGING
5. How does it work?
6. Step 1: Be stuck on a bug
7. Step 2: Obtain a rubber duck
8. Step 3: Explain Your Problem or Code to the Duck
9. Step 4: Have a Eureka! moment
10. The Psychology Behind It • Forces Articulation of the Problem • Engages Multiple Cognitive Processes • Breaks Down Complex Issues • Eliminates Assumptions and Biases
11. • When to use? • Choosing the right rubber duck • Creating a distraction free environment • Be patient and persistent Practical Tips
12. When to use?
13. • The danger of explaining without listening. • When not to use Rubber Duck Debugging. • Finding a balance with other debugging techniques. Pitfalls
14. Conclusion
15. So, do you have a rubber duck?