2. When pair programming, the most regularly used names to distinguishing which person is currently typing are:
c. Driver and Navigator. Some say the Driver types, while the navigator looks at the broader problem / real world level. I (Sallyann) dispute this though
3. In Jim Coplien and Neil Harrison’s book “Organisational Patterns”, pair programming is referred to as:
c. Developing in pairs. Illustrated with a lovely ‘Two Amigos’ picture.
4. Pair programming has not been shown to have a helpful effect on:
b. Pair programming has actually been shown to lengthen the amount of effort required to develop a feature, however this is considered a cheap price to pay for the eventual time saved through not having to fix the extra defects found in solo-developed code.
Do you want to learn more about PairProgramming?
Brian Marick wrote a nice post about pairing with Corey Haines
A Pair Programming Experience by Randal Jenson
You might want to spend a while on Wikiwiki: (If you have never been to the first wiki, make sure you take some time to look at everything written here.)
- //pairwith.us/ is nice if you want to see remote pairing in action
- VS Anywhere (remote paring for Visual Studio)
You can also find these links and other on my delicious page for PairProgramming