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.
Saturday, September 23 2017 powershell
While NuGet provides all the power needed to explicitly control every aspect of a package (something the exacting control freak in me really appreciates), a simple project like this doesn’t need anything more than the standard conventions.
Monday, September 18 2017 sharpen-the-saw
In this edition: The Single Responsibility Principle; keeping a log in notepad; Visual Studio 2015 Update 2 RTM; NCrunch; Killing solid communication; Social engineering; Rejecting stereotypes; and What is agile anyway?
Saturday, September 16 2017 powershell
Perhaps the most significant problem with the simplistic versioning system we put into place last time is that we can get the same version number generated on different branches. Fortunately, semantic versioning gives us room to fix this by adding a descriptive suffix to the build number.
Saturday, September 09 2017 powershell
Version numbering is an odd detail - one we can (and should) easily ignore at the start of a project. There comes a point, however, where we find that version numbering is vitally useful. At that point, we usually discover that we should have started versioning things about six months ago … and now we have a mess to clean up.
Saturday, September 02 2017 powershell
To simplify the use of our build scripts, and to make it easier for someone new to the project to work out how things work, we’ll create some convenience PowerShell scripts to launch the build. We’ll create three scripts, for three different purposes: one for moment to moment use by a local developer; one to do a release build when the project is ready for distribution; and one for our continuous integration server.
|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|
|In defense of XML||25 Apr 2017|
|Static Analysis tools for the Win||15 Apr 2017|
|What's the value of a failing unit test?||08 Apr 2017|
|What's the value of a passing unit test?||02 Apr 2017|
|You keep using that word: Mandatory||19 Mar 2017|
|Why Immutable Types?||11 Mar 2017|
|Immutable Type Miscellany||05 Mar 2017|
|Testing Immutable Types||25 Feb 2017|
|Restored Posts||19 Feb 2017|
|Factory Methods||18 Feb 2017|
|Sharpen The Saw #10||13 Feb 2017|
|Queue Concatenation||11 Feb 2017|
|Complex Immutable Queues||04 Feb 2017|
|The Problem with the Simple Immutable Queue||28 Jan 2017|
|Enumeration of Immutable Queues||21 Jan 2017|
|Reversing Immutable Stacks||14 Jan 2017|
|Simple Immutable Queues||07 Jan 2017|