Certifiable

I'm back on the Microsoft certification treadmill again; my original qualification was an MCSE back in the days when Windows NT 4 was putting the moves on Novell Netware. In the interests of getting my career moving in a forwards direction, I've started doing the exams again.

This afternoon was the snappily-titled Microsoft .NET Framework 2.0 - Application Development Foundation exam. I didn't do myself any favours by forgetting the date of the exam - I was just sitting down to some tasty sashimi with Mei when my phone hopefully chimed in to remind me that I had 30 minutes to go. One quick dash to the nearest internet cafe later, and the exam was rescheduled long enough for me to finish my beef teriyaki.

My practice exams had not been encouraging, as they indicated that I would be tested on a whole lot of esoterica that I don't use on a daily basis. Fortunately the revision exams pushed me in the right direction, so I was able to pass, although I had to sweat for it. Next up (some time in January) is the equally titularly-challenged Microsoft .NET Framework 2.0 - Web-Based Client Development, after which I will apparently be considered to be a Technical Specialist. Just one small step on my way to world domination...

You know it's going to be one of those days...

... when your build server suddenly drops off the network. After a little investigation, you discover that it was unplugged by someone who had started working at the desk where the server was, who very kindly unplugged it and moved it halfway across the building to where they used to sit, and then left it unplugged and switched off on the floor.

There are two solutions to this:

1. stick a big fat red label on the build server warning of the dire consequences associated with even touching the server;
2. get a proper server installed in the datacenter, rather than an ageing PC that masquerades as a server, at what at the time was an empty desk.

Care to guess which solution we will be going for?