This summary is derived from “All
Need to Know about Pair Programming I Learned in Kindergarten.”,
by Laurie A. Williams Robert R. Kessler.
You are welcomed to read the full paper. It starts with lots
of data supporting
the use of pair
programming, some of it with computer jargon you do not need to worry
beginning programmers. It elaborates on many of the points
more than I do in the summary.
Share everything. All contributions, whether leading to great results or errors, are “ours”, not “yours” or “mine”.
Play fair. One person “drives” (has control of the keyboard or is recording design ideas) while the other is continuously reviewing the work and planning ahead. Even when one programmer is significantly more experienced than the other, it is important to take turns “driving,” lest the observer become disjoint, feel out of the loop or unimportant. The person not driving is not a passive observer, instead is always active and engaged, checking over the work and thinking ahead.
Don’t hit your partner. But make sure your partner stays focused and on-task.
Put things back where they belong. Put negative judgments in the trash: Be positive about you and your partner. For both, this is an opportunity to improve.
Clean up your mess. Watch over the shoulder and you are really likely to find a large number of your errors!
Don’t take things too seriously. If your partner picks out a bunch of errors as you type, be glad there are two of you. But do not always agree. Have healthy disagreement/debate. Finding the fine balance takes adjustment.
Say you’re sorry when you hurt somebody while moving furniture. Sit side-by-side and program, simultaneously viewing the computer screen and swap the keyboard and mouse back and forth. Slide the keyboard -- don't move the chairs.
Wash your hands of skepticism before you start. Being skeptical can be a self-fulfilling prophesy. Buying in and “jelling” as a team can lead to a whole that is greater than the sum of the parts.
Flush. If you work on some parts independently either discard them (flush) and start over together or have the partner very carefully review the work with you.
Warm cookies and cold milk are good for you. Periodically, taking a break is important for maintaining the stamina for another round of productive pair programming.
Be aware of the power of two brains. Experience show that, together, a pair will come up with more than twice as many possible solutions than the two would have working alone. They will then proceed to more quickly narrow in on the “best” solution and will implement it more quickly and with better quality.Also see the administrative details for when pair programming is working, and when it is not.