What not to do

Working in a team that isn't heavily invested in documenting requirements and specifications (we usually have a starting set of such things but these soon fall out of step as development evolves) makes it a challenge to know both what is being added to the product and whether it needs to be documented. The development

Faff

I cannot be bothered with faff. This is one personality trait that has definitely changed as I've gotten older, or perhaps it's just a reaction to the years I spent indulging my 'gadget-geek' and allowing myself to think that jumping through 5 hoops to get a simple task done was "OK". My mindset these days

It's not easy being green

Last year I flew to America (visiting Boston and Chicago) and this year I'll be flying to London (twice) and to Singapore later in the year. I'm travelling much more than I used to so I guess it's only natural that I'm pondering how to rebalance my carbon emissions. This definitely played into my decision

TCUK 12

The time has come, so Gordon said, to talk of many things, of slides and chats, and learning facts, and something else that rhymes but I'm rubbish at poetry (with sincere apologies to Lewis Carroll). Enough of that though, what I want to talk about is the Technical Communications Conference 2012 (TCUK12) and why you

All change!

Ever wanted to just throw everything away and start over? I've been tempted by this notion recently and, whilst it may seem a bit ill-conceived, part of me does wonder what would happen if we just, quietly, started removing some parts of our documentation. In fairness, we've done that in the past. Our Development Kit

Back from Tunisia

We did done a holiday! We had a few simple criteria for our holiday. It needed to be under £500 each, it needed to be somewhere hot and sunny, and ideally it needed to be all inclusive. After various online searches, we had it narrowed down to a week in Cyprus, or a week in