I remember this time in university when I was sitting in class, and my professor wanted to show us how to use the debugger GDB for C. He was going through it and talking about how amazing it is, but to me, it seemed very complicated and intimidating. At this point, I had already been coding for a few months and was thinking to myself, “Why would I want to use a debugger when I can use a print statement to sort of debug my code?”

Maybe it was just the way my professor was presenting it, but from that point on, I really wanted to stay away from debuggers. It was only when I started working at my company that I began to use a debugger. The first time I used a debugger was in Eclipse while learning Java. My company wanted me to help build a GUI application.

That’s when my supervisor taught me how to use a debugger in Eclipse. Once my supervisor showed me how to use the debugger in Eclipse, I started using it for everything. I would put breakpoints all over my code to figure out at what point the code went to these listeners or other event handlers.

This was the main way I started to learn Java. I also used these techniques when learning Android development. Fast forward to my current company when I started coding in C# and using WinForms, I had to use the Visual Studio debugger to understand how the code was working.

In this video, we will go through a code base together, fix some bugs, and use the debugger to debug those bugs. Hopefully, by the end of this video, you’ll see the value of debuggers and when to start using them in your software development. If you’re not using debuggers yet, I hope this will clarify why you should start using them now.

Thank you for watching, and happy coding! 💻🧡
-Henrik