Practical .NET

Insider: Secrets of Debugging

Faced with reviewing large swaths of other people's code, Peter Vogel is left to ask: what does it really take to be good at debugging?

Even with following a Test Driven Development regime, my code doesn't work the first time (pretend you're surprised). So debugging is a critical skill for me. Also, as a hired gun, I'm frequently having to deal with someone else's code, which often isn't working the way everyone expected it to.

One thing I have noticed: I'm better at debugging than a lot of the people I work with. My first step is to look at the evidence to make sure that I know what the problem is. A lot of people seem to feel that the first step is to SOLVE THE PROBLEM. They look at some of the symptoms, assume that they know what the underlying problem is and then start implementing a solution -- which usually means that we end up with two problems where we originally only had one. But I've already written about what I consider the essence of the debugging technique (getting a good description of the problem) and the mental tools for achieving that goal. Feel free to read it and disagree.

Lately, however, I've been reviewing a large whack of code with an eye to improving its quality and performance. That means that I've been reviewing my debugging and analysis toolkit. And that's led me to writing up some of the resources that you have available in the .NET/Visual Studio environment and may not be aware of. Those topics are so short that they don't really belong in this forum, so you'll see them turning up as weekly tips in my .NET Tips and Tricks blog over the next few weeks.

But I wonder: Can people learn to "debug better?" Or are some people just good at debugging and every else is just good at generating bugs? You tell me.

About the Author

Peter Vogel is a system architect and principal in PH&V Information Services. PH&V provides full-stack consulting from UX design through object modeling to database design. Peter tweets about his VSM columns with the hashtag #vogelarticles. His blog posts on user experience design can be found at http://blog.learningtree.com/tag/ui/.

comments powered by Disqus

Featured

  • Compare New GitHub Copilot Free Plan for Visual Studio/VS Code to Paid Plans

    The free plan restricts the number of completions, chat requests and access to AI models, being suitable for occasional users and small projects.

  • Diving Deep into .NET MAUI

    Ever since someone figured out that fiddling bits results in source code, developers have sought one codebase for all types of apps on all platforms, with Microsoft's latest attempt to further that effort being .NET MAUI.

  • Copilot AI Boosts Abound in New VS Code v1.96

    Microsoft improved on its new "Copilot Edit" functionality in the latest release of Visual Studio Code, v1.96, its open-source based code editor that has become the most popular in the world according to many surveys.

  • AdaBoost Regression Using C#

    Dr. James McCaffrey from Microsoft Research presents a complete end-to-end demonstration of the AdaBoost.R2 algorithm for regression problems (where the goal is to predict a single numeric value). The implementation follows the original source research paper closely, so you can use it as a guide for customization for specific scenarios.

  • Versioning and Documenting ASP.NET Core Services

    Building an API with ASP.NET Core is only half the job. If your API is going to live more than one release cycle, you're going to need to version it. If you have other people building clients for it, you're going to need to document it.

Subscribe on YouTube