I have finally sorted out my blog! It has resulted in me returning to my original blog on blogger.com. After leaving Posterous, I attempted to just host my blog on my Raspberry Pi but unfortunately barely a day went by when the Pi wasn't unplugged for some reason so I decided to move it again. There was a degree of foolery involved, I had to export my blog to a wordpress site then convert it to a blogger site then import it. Anyway! Hopefully blogging shall now commence!
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