Monday 1 October 2007

Lazy Development

For around the past 6 months I have been trying to nail down what the difference in attitude is between developers.

Paul Duvall has summed up what I have been trying to get across to colleagues in his post about troubleshooters and troublepreventors.

I describe myself as a lazy developer to anyone who cares to listen, however this needs some context.
By lazy I mean that I will put more effort into automating a task now rather than have to work out how to do it manually once a fortnight. (DRY)
Couple this with writing unit tests now to allow refactoring to take place safely at anytime in the future and it will aid you in developing great software.

Everytime these upfront payments get dodged it comes back to punish the dev team with obscene amounts of non-value add work.