I was listening to a Hanselminutes podcast and he mentioned a reference to the "Who Moved My Cheese" book (not sure if it was intentional!). It's a great little book about managing change in life and specifically at work. Well worth a read even if you think you are ok with handling change. Good stuff, it's a really small if you aren't normally a reader. I think I have already given my copy to someone but it's only a couple of quid so pick it up.
I've been QA'ing quite a bit of work recently and one common theme I've noticed across both Java and C# projects I have been looking at is that we occasionally open ourselves up unessacarily to Exceptions by the way objects are being created. My general rule of thumb (which I have seen mentioned in a Pluralsight video recently but also always re-iterate in various Robust Software talks I have done) is that you shouldn't be able to create an object and then call a method or access a property that then throws an exception. At worst, it should return null (I'm not going to moan about that now). I've created an example below. We have two Dojos, one is good and one is bad. The bad dojo looks very familiar though. It's a little class written in the style that seems often encouraged. In fact, many classes start life as something like this. Then as years go on, you and other colleagues add more features to the class and it's instantiation becomes a second