Thursday, September 1, 2011

Life After Pair Programming | Jay Fields' Thoughts

Jay Fields' Thoughts: Life After Pair Programming
When I first joined DRW I noticed that the vast majority of developers were not pair-programming. I was surprised that a company that employed so many smart people would just simply disregard a practice that I considered to be so obviously beneficial.
note: it's so easy to judge people who don't pair-program, isn't it? You can write-off their behavior for so many reasons:
  • They simply haven't done it enough to see how much value it provides.
  • They've used the wrong setup, and turned a positive ROI into a negative ROI situation in the past.
  • They must be anti-social or not team players.
  • They must guard their code because they are too proud or believe it's job security.
Never once did I consider that their behavior might be correct based on their context. There was no context in which pair-programming wasn't the right choice, right?
Almost 3 years later, and on a different team, I basically never pair.
Extreme Programming Explained: Embrace Change (2nd Edition) Planning Extreme Programming Extreme Programming Installed

No comments:

Post a Comment