Serverless architectures are gaining traction in the software industry, and it wouldn’t be surprising to see them rise on a similar curve that we have seen with microservices. But the ephemeral nature of these short-lived units of execution makes it very difficult to debug them. How do you debug code that only throws an exception under very special circumstances, and then disappears?
Infrastructure as code has brought great advances to DevOps. This post is based on a webinar in which I presented how to deploy Ozcode Production Debugger to Azure using Pulumi to reduce C# debugging time. The webinar recording is provided at the end of this post.
We will see how to use Ozcode to search for objects in a very complex object graph.
Learn how Ozcode can be used to search through collections and focus on a subset of records.
Debugging collections can be extremely difficult. Learn how to use conditional breakpoints and stop wearing your finger out hitting F5.
Unit tests are the foundational element in the testing pyramid. In theory, codebases should have more of those than any other kind. Fortunately unit tests area also the fastest to run.
Debugging exceptions in C# can be tricky. Ozcode Visual Studio extension adds a set of tools that point you right to the problem.
There was once a computer programmer. There had been programmers before this one and there were programmers after him. In that way he wasn’t remarkable but in many, many other ways he was. Sir Tony Hoare was the creator of the Quicksort, Hoare logic and, unfortunately, the concept of null. Speaking at QCon in 2009 …
Famed computer scientist Donald Kunth once wrote that premature optimization is the root of all evil. I dare say that the problems the famed algorithmist faced are slightly more advanced than those most of us run into on a daily basis. Nonetheless, the rule has been repeated and passed down from programmer to programmer over …