Rebuilding my Developer Platform – For the Last Time!

I have finished enough of a ground-up rebuild of a developer machine to take stock. The rebuild process went something like this:

Step 1 – Start long running installation

Step 2 – Wait for installation to complete

Step 3 – Go back to Step 1. Rinse and repeat …

Hard Learnt Lessons

• Building a Windows based developer workstation takes more TIME than you imagine

• Long periods of WAITING for installations to complete is WASTEFUL

• Rebuilding workstation machines is REPETITIVE

One more point on the the manual build process. I will never have to do it again!

Advertisement

Wtf is Amber? Release only on a Green Build

Sounds completely sensible.

Why would you do anything else? That would just incur unnecessary risk surely?

No, we would definitely not do that.

Yes you would, and from what I see, in surprisingly large numbers too.

TODO Comments have no place in Master

Don’t get me wrong, as a professional C# developer I love using TODO markers in my code. They document minor details that I need to revisit and allow me as a coder to keep moving with the aim of getting an overall structure in place. I do this in feature branches and I often do a git rebase -i to tidy up all of my local commits into something more meaningful to merge back into the develop or master branch.

As you are reading this I hope that you will agree with the next few points that I make about source code best practices. So here are my views on what I believe to be a sensible perspective on how you treat releasable code.

If the Dev Team fails to own the Build

You are dead in the water.

As a developer friend likes to say, these people are Zombies. They are dead but just don’t know it yet.