No this isn’t about how Haskell evaluates stuff, but how people design and write code. There’s a mobile phone ad showing in the UK at the moment about how it’s the impatient people that drive towards new innovation and in software at least I strongly disagree. On the contrary, lazy programmers rule. I’m a lazy programmer, I can’t bear writing the same code more than a couple of times and when I recognise the second instance I refactor it into a function.

One of the reasons I started this blog was to write down some of the stuff I’ve learnt over the past couple of years on how to structure my development environment so that it’s easy to use and ties in nicely with things like continuous integration and automated testing. So this is sort of a “head-up” of the topics I think I will be covering over the coming weeks.. Tools choice Source control Project structure Binary dependencies Continuous Integration It won’t necessarily be in this order and I may throw some other stuff in if I find the inspiration

Well I finally gave in and joined the blogging community. This will be a general rant on technology, running a small software consultancy business and anything else that takes my fancy. To give you all a bit of background I’ve been writing software for about 30 years now, having started on a mixture of home built (anyone remember the Tangerine MicroTan 65?) and early home computers includinng the Commodore Pet, Amstrad 1512, BBC Micro and Atari 1040ST.