Skip to main content

Free ebook - Practical debugging for .NET Developers

Even with the introduction of AI in the software development process, debugging remains an important part of our job. Being able to investigate difficult problems efficiently and find solutions fast is an important skill to master. The good news is that it is a skill you can learn and the even better news is that you can get help through the ‘Practical Debugging for .NET Developers’ book by  Michael Shpilt that is now available for free!

 


I like to share a fragment of the introduction:

The best software engineers I know are excellent at debugging. They find solutions to difficult problems where no one else can. They accomplish this by using the right tools, knowing what to look for, and having a deep understanding of both their own domain and the .NET ecosystem. Moreover, they conduct a systematic investigation using proven debugging methodologies. Debugging is not an art—it’s something that can be taught, and this book is going to do exactly that. This book is all about perfecting your debugging skills, saving you time, and increasing your productivity.

Can’t agree more! So don’t hesitate and grab your copy here:

PDF | MOBI | ePub + Video lessons

More information

https://michaelscodingspot.com/free-book/

Popular posts from this blog

Podman– Command execution failed with exit code 125

After updating WSL on one of the developer machines, Podman failed to work. When we took a look through Podman Desktop, we noticed that Podman had stopped running and returned the following error message: Error: Command execution failed with exit code 125 Here are the steps we tried to fix the issue: We started by running podman info to get some extra details on what could be wrong: >podman info OS: windows/amd64 provider: wsl version: 5.3.1 Cannot connect to Podman. Please verify your connection to the Linux system using `podman system connection list`, or try `podman machine init` and `podman machine start` to manage a new Linux VM Error: unable to connect to Podman socket: failed to connect: dial tcp 127.0.0.1:2655: connectex: No connection could be made because the target machine actively refused it. That makes sense as the podman VM was not running. Let’s check the VM: >podman machine list NAME         ...

Azure DevOps/ GitHub emoji

I’m really bad at remembering emoji’s. So here is cheat sheet with all emoji’s that can be used in tools that support the github emoji markdown markup: All credits go to rcaviers who created this list.

Cleaner switch expressions with pattern matching in C#

Ever find yourself mapping multiple string values to the same result? Being a C# developer for a long time, I sometimes forget that the C# has evolved so I still dare to chain case labels or reach for a dictionary. Of course with pattern matching this is no longer necessary. With pattern matching, you can express things inline, declaratively, and with zero repetition. A small example I was working on a small script that should invoke different actions depending on the environment. As our developers were using different variations for the same environment e.g.  "tst" alongside "test" , "prd" alongside "prod" .  We asked to streamline this a long time ago, but as these things happen, we still see variations in the wild. This brought me to the following code that is a perfect example for pattern matching: The or keyword here is a logical pattern combinator , not a boolean operator. It matches if either of the specified pattern...