I’m a reasonably average bloke in most respects. Wife, kids, cat, career, not much hair on top and unreasonable hairs elsewhere. I’ve been writing software professionally for not far off 20 years, but that doesn’t mean I know even half the answers yet. If experience has taught me one thing, it’s that the right answer depends as much on the people as the requirements.
While I struggle to balance life as a consultant, a husband, and a father, there are times when I find myself wanting to convey my technical ideas and opinions in a forum where I’m unlikely to be shot down for at least an hour or so. Hence, this blog was born.
In all seriousness, there are lots of times that I’m looking for a bit more than ‘how’ to do something. I believe ‘why’ is often more useful, at least from an architectural position. The items I post here have been written because they were a good solution for a situation I found myself in at some point, care should be taken when blindly copying, or equally when immediately shooting me down.
I hope something here proves useful to someone. If any advice leads to total disaster, please let me know – that would be equally good to know.