Saturday, May 05 2018 professional
In our last discussion we talked about the cost of leaving a minor bug in place, versus the cost of fixing it properly. We discovered that the fix might involve half the time investment of leaving the bug in place.
Saturday, May 12 2018 professional
One of the most useful precepts that I use to guide my development is this: when something goes wrong, make sure you fix it twice. This is especially important when the problem impacts on a production environment, but it’s also relevant for staging, testing, and development environments.
Saturday, May 19 2018 smart-code
Long ago, before storing things in the cloud was commonplace or economic, I used an online mirroring tool to replicate all our family photos between my desktop PC and my wife’s netbook. This was both effective and painful - here’s why.
Monday, May 21 2018 sharpen-the-saw
In this issue from October 2017: the ideal length of a function is easier to decide than you think; the next major version of C# is bringing some long overdue changes; six approaches to programming that will change the way you think; recovering access to a PC when it has fallen off the domain and you don’t know the admin password; ten of the worst features of C#, as selected by Eric Lippert; and the Myth of the Genius Programmer.
Saturday, May 26 2018 smart-code
When developing systems that must wait for key things to happen (often, things that are outside their direct control), we need to consider how long we’re willing to wait for an answer.