Good Pair

Describe GoodPair here.

A GoodPair is a pair that works well together for whatever reason. The causes of forming and maintaining a GoodPair is of interest to anyone interested in adopting PairProgramming. It can be argued that some necessary conditions include good communication, mutual respect for each others opinions, and not holding onto grudges.

Some believe that it is mandatory to PairPromiscuously, but CornFieldEffect suggests that WardAndKent work better together than separately. This provides at least one counter-argument to saying that you must PairPromiscuously, and points out the benefits of leaving good pairs alone for extended times.

---

The best pair is

• A> introvert vs introvert,
• B> people free to, uh, express differences of opinion,
• C> physically enabled to code without ridiculous hardware impediments, and
• D> PairPromiscuously, so nobody gets married.

That just leads to two people who either kill each other, or simply write the same code as a Solo coder would.

While a GoodPair that remains together for extended periods of time may become like a married couple do married couples think the same? So it is highly unlikely that the GoodPair will lead to two programmers writing code the same way a single programmer would.

But see HowToPissOffYourPair, for other strategies to encourage less pairing at your workplace.

---

Previously http://zeekland.zeroplayer.com/Uncle_Wiggilys_Travels/43

---

---

---

http://zeekland.zeroplayer.com/Uncle_Wiggilys_Travels/47

---

Please do attempt to keep ThreadMode here and lower and reserve the beginning for DocumentMode. Awesome comic, but I am confused, especially aboutt he foot comment at the end. -- AndrewRicketts

That's why you gotta read the rest of the plot - it's a SMASH CUT. The link is right there.

Nope, read it and still confused, oh well was still enjoyable -- AndrewRicketts

---

Related to PairProgramming

Opposite of BadPair and HowToPissOffYourPair