4 ms·

Pair programming was invented and evangelized by developers, and are its most ardent defenders at every vendor I know that offers Agile services. ThoughtWorks'

• plinkplonk 14y ago
  Even ThoughtWorks has/had developers who don't particularly like or believe in pair programming, but go along because it comes under the company's proclaimed orthodoxy umbrella most of the time. (ex TWer, so I know whereof I speak). I used to champion pairing when I used to work at TW, and used to be puzzled at why some (very talented) TW developers thought it was all hogwash, but TW is a fine company in many ways and you eventually learn to tune out the extremes of the company's (Roy's ;) )eccentricities and get on with the work. You need to do this at any company, nothing specific to TW really. In many teams, pairing is loosely practiced.In others, 100% pairing is the norm. So it all depends, even at TW. That said, you have a point in that TW has some very strong and vocal proponents of 'pure' pairing. I used to be very gung ho about agile dev when I was at TW. These days I know better. just my tangential 2 cents, and not really contradicting anything you said, just qualifying it a little.
  • shaydoc 14y ago
    I would say 100% pair programming would be a highly draining experience! may result increased productivity, but at what cost!
• juan_juarez 14y ago
  Pair programming's biggest win is that it keeps me on task & not arguing online about whether or not Agile practices work.