Pair programming is a software development methodology where two software developers, or a software developer and programmer, work together at a single workstation. One developer, the “driver,” writes code while the other, the “navigator,” reviews each line of code as it is typed in. The navigator also offers suggestions about design and workflow. Pair programming is an effective approach for giving all programmers opportunities to learn from the experience and perspectives of their partners.
The concept was first introduced by Jim Coplien and Neil Harrison in a 1992 workshop at the OOPSLA conference. The team explained the concept as a “social technology,” which has gone on to become a common aspect of the agile development methodologies. The practice has since gained widespread popularity in the developer community.
The benefits associated with pair programming include an increased level of code quality due to a double-check on development process, as well as a greater level of collaboration between team members. The process of two developers working together also provides an opportunity for knowledge transfer, as the more experienced developer can help guide the less experienced one in their development efforts.
However, the practice of pair programming can be time-consuming, and may require developers to work more slowly than they would independently. Furthermore, the cost of pairing can sometimes be cost-prohibitive due to the increased labor cost associated with a two-person setup.
Despite its drawbacks, pair programming remains a common and useful practice for teams developing software. It is an effective way to reduce bugs, improve code quality, and to give all developers a chance to participate in the development process.
