Category

Obie Fernandez writes a blog post about how pair programming is not for the masses.  I find it interesting that his post addresses many of the items that were not discussed at the Agile 2009 session on how to debug pair programming. Three ideas identified by Obie are common...

Thanks to Lisa Crispin for pointing out this article on pair programming in the Jobs section of the New York Times.  In the article, they do a profile of a company in Florida that uses pair programming.  It’s a very first person description of the practice, the benefits and...

Mat Wayne ran an interesting session about overcoming resistance to pair programming organized around personas.  On each table there was a description of a different persona and some ideas on why that persona might resist pair programming.  Our job was to discuss in groups why...

William Pietri has come up with a list of ways to do pair programming badly.  My favorites – #4 and #8.  Seriously though, these are anti-patterns to avoid, not to emulate.  Pair programming is a very powerful tool, we just need to get eliminate some of the misconceptions...

Jim Shore has linked to an excellent discussion on pair programming from the perspective of an experienced programmer being asked to pair full time.  Short summary – everything you thought pair programming was, it is not.  This blog entry is definitely worth a read!

… but don’t prohibit other people from giving it a try. I heard the MOST ignorant statement the other day while facilitating a workshop. “Pair programming is useful when you’re 23.  When you turn 24, there is no need for pair programming.” From the...

In Boston, I attended a session lead by Neal Ford from Thoughtworks.  He shared his company’s experience of applying XP in a variety of domains.  Thoughtworks almost exclusively uses XP on all their consulting engagements.  Here are some thoughts on three pieces of misinformation...