I was talking to a friend not so long ago about documentation. My argument is that writing external documents in order to define the behaviour and interactions of software is (or should be) covered by the business/stakeholders in their requirements or with the acceptance tests that have been defined for the application. There is of course a need to document the technical details, such as why you did something the way you did, and I feel this is best covered from self describing, well written, Unit Tests. More...

Introduction

Whilst working in India, I had to persuade our development team why we should pair program and what benefits it is currently giving our UK Teams. Here are a few of my thoughts used to persuade our development team, enough to give it ago.

Pair programming is where two developers work on the same machine. One person is the driver, the other the navigator. The driver performs the coding whilst the navigator is continually reading, spell-checking and reviewing the driver’s code; continually offering input and thinking through problems. More...