Saturday, January 04 2020 sharpen-the-saw
In today’s post: The story of the Visual Studio Code team turning on strict null checking; Eric Lippert talks about why null is not false; Analyzers for Fluent Assertion users; the PowerToys for Windows are back; Make sure you have five reasons to do anything; Remember IDEAL CHALK when writing code; how to choose a good password generator; retailers need to take responsibility for data breaches; more on programming fonts; fixing your inconsistent sleep schedule; and unit testing at Google.
After earlier defining our logging interface, some readers posed a few questions about how it would work from a consumers perspective. So before we look at implementation details, let’s look at how we’ll instrument our code and what the output might look like.
Saturday, January 18 2020 professional
There’s a very clever piece of design advice that I was taught at university that seems to be less well known than I expected.
To implement the logging interfaces described earlier, there are some issues we need to consider. There are two different usage patterns we need to support, plus we need to support concurrent use, and avoid code duplication.