Honda, Jason
March 27, 2006
Pair Programming
Pair programming is the idea where a team of two programmers have one
computer between the two of them. This is an idea that came into light mostly after it was
introduced with eXtreme Programming Software Design Methodology. It requires one
programmer to sit at the computer and be the “driver,” and the other to sit next to them as
the “navigator” helping out the driver. The two will switch periodically usually at half
hour to one hour intervals or when one gets tired. Pair programming has many
advantages and disadvantages.
The disadvantages of programming are many but have little to do with actual
performance. Since the pair is working so closely together, personal and professional
conflicts can brew up quite a storm. Differences in ideas, can lead to better code, or with
more stubborn people can bring the programming to a standstill. A lot of the problems are
due to stubbornness or inflexibility of the programmers. They may not like working with
other people which is a problem, or they may have different schedules that would be
troublesome. This could potentially slow down the team of programmers as a team
member might be less than cooperative. This would only be a problem for a short time as
that person is taken off the team, or their habits are changed to work better in a team
environment.
Pairs or programmers must be a good team, where they are all knowledgeable in
all things, yet specialized so that they can build off each other. Having an extremely
knowledgeable person and a beginner would not be productive, as the beginner would
have no critiques to give, and would slow the process down when they are programming.
