It's one of the paradoxes of blogging that most every blogger (including me) is sharing what they know right now (let's ignore those who blog purely for the traffic and visibility). Since everyone is learning, this can result in poor or misleading information being shared just as much as good information. Keep this in mind as you read any blog - how experienced is the writer and how well do they really know what they're talking about.
I'm just as flawed as other bloggers, so you should feel encouraged to check my ideas for yourself.
Monday, November 20 2017 sharpen-the-saw
In this episode from October 2016: Why it matters how quickly you create new bugs; an extension for VS2015 for editing and previewing markdown; how to write great code that’s not brilliant; Brian Krebs hit with record setting DDOS; typography for user interfaces; and, F# for the rest of us.
Saturday, November 18 2017 powershell
On my previous post on code coverage, someone asked if the coverage report could highlight areas where coverage decreased. It turns out that ReportGenerator can do this, but there’s room for improvement.
Monday, November 13 2017 sharpen-the-saw
In this episode from August 2016: Fact or fiction about agile documentation; using C# as a scripting language; easy to miss code smells; deprecation of the RC4 stream cypher; analogue computers make a comeback; and, Q&A with Scott Hanselman.
Saturday, November 11 2017 powershell
For diagnostic purposes, it can often be useful to know when specific build tasks started and how long they took to execute. This information can help you spot anomalies and resolve odd issues.
Monday, November 06 2017 sharpen-the-saw
In this episode from July 2016: Learning a healthy fear of legacy code; git 2.9.0 released; the myth or reality of 10x programmers; TeslaCrypt ransomware developers terminate project; the danger of specifying specific thresholds; and Bill Wagner talks about what might be in C# 7.
|The day my Psake build broke||04 Nov 2017|
|Sharpen The Saw #17||30 Oct 2017|
|NuGet, .NET Core and Psake||28 Oct 2017|
|Sharpen The Saw #16||23 Oct 2017|
|.NET Core with Psake||21 Oct 2017|
|Sharpen The Saw #15||16 Oct 2017|
|Pass implementations, not representations||14 Oct 2017|
|Sharpen The Saw #14||09 Oct 2017|
|Test Coverage Reporting with Psake||07 Oct 2017|
|Sharpen The Saw #13||02 Oct 2017|
|Test Coverage with Psake||30 Sep 2017|
|Sharpen The Saw #12||25 Sep 2017|
|NuGet packaging with Psake||23 Sep 2017|
|Sharpen The Saw #11||18 Sep 2017|
|Semantic versioning with Psake||16 Sep 2017|
|Versioning with Psake||09 Sep 2017|
|Launch Scripts for Psake||02 Sep 2017|
|Controlling build types with Psake||26 Aug 2017|
|Unit Testing with Psake||19 Aug 2017|
|Readable output from a Psake build||12 Aug 2017|
|Finding MSBuild in a Psake build||05 Aug 2017|
|Build Automation with Psake||29 Jul 2017|
|Avoiding the Singleton Pattern||22 Jul 2017|
|Implementing the Singleton Pattern||15 Jul 2017|
|Custom Inspection Patterns in Resharper||08 Jul 2017|
|Getting Started with FsCheck||01 Jul 2017|
|Shrinking and Equality Testing with FsCheck||24 Jun 2017|
|Property Testing with FsCheck||18 Jun 2017|
|High CPU Usage by Windows Update on Windows RT||04 Jun 2017|
|Finding source code in .NET Core||10 May 2017|