An alternative CV strategy

This is my second attempt at writing this. Memo to self: after hitting the Post button, make sure the post has actually been published before navigating away from the page… I’ve been reading a fair number of CVs recently, and I’ve been struck by just how much experience everyone seems to have. At least, everyone claims to have a breadth of experience that I just can’t match. I haven’t counted, but I suspect most of the CVs I’ve been looking at have listed over 100 technologies. In light of this, I’ve been considering how I’ll market myself when I’m next … Continue reading An alternative CV strategy

Elegant comparisons with the null coalescing operator

A while ago I commented on how I’d like a return? statement, which only returned if the return value was non-null. The purpose of this was to remove the irritation of implementing Equals and IComparable.CompareTo on classes with several properties. For an example of the kind of thing I mean, consider an Address class with properties Country, State, City, ZipCode and HouseNumber. (Apologies to readers who aren’t American – while I feel a traitor to my country for using state instead of county and zip code instead of post code, I’m guessing there are more readers from the US than … Continue reading Elegant comparisons with the null coalescing operator

Broken windows and unit testing

There’s quite possibly only one person in the world reading this blog who doesn’t think it’s got anything to do with Vista. The windows in the title have nothing to do with Microsoft, and I’m making no assertions whatsoever about how much unit testing gets done there. The one person who understands the title without reading the article is Stuart, who lent me The Tipping Point before callously leaving for ThoughtWorks, a move which has signficantly reduced my fun at work, with the slight compensation that my fashionable stripy linen trousers don’t get mocked quite as much. The Tipping Point … Continue reading Broken windows and unit testing