Why should you do pair programming? There are a number of reasons:
- Solving the right problem – two persons that has understood the problem has a better chance to solve the right problem and not the problem one person has misunderstood.
- Quality – the co-driver will assist the driver to develop the algorithm and act as a guard against mistakes.
- Knowledge spread – both participants in the pair will have a great knowledge about the solution when it has been developed in co-operation.
- Constant code review – instead of having code reviews from time to time you have them all the time. The co-driver will constantly review the code that is being written and suggest improvements.
- Reduced costs – bringing new developers into the team is expensive. If they are brought in using pair programming then they will learn fast and can soon be productive. A new developer is productive
- within minutes instead of weeks or even months.
- Single point of failure – what happens if only one person knows about a certain area of the code and chooses to quit or has an accident on his way to work? Keep your bus count higher than 1. The bus
- count is the number of buses needed to erase the knowledge your team has.
- Spread knowledge about the tools being used – every developer knows something different about the development environment and will therefore constantly learn new things from his partner.
- Discipline – it is really hard not to focus at the task at hand while pair programming. You will therefore get more work done.
- Focus – your partner will ensure that you focus on the task at hand and not a random page on the web.
- Direction – your partner will act as guide to ensure that you don’t stray away from the proper path by accident.
Casiano Rodriguez León