Pair Programming Illuminated
||Author: Laurie Williams, Robert Kessler|
List Price: $34.99
Our Price: Click to see the latest and low price
Publisher: Addison-Wesley Pub Co (28 June, 2002)
Sales Rank: 225,047
Average Customer Rating: 4.71 out of 5
Customer ReviewsRating: 5 out of 5
Answers to Common Questions
As the title suggests, Pair Programming Illuminated casts light on many of the frequently asked questions about pair programming. This very readable book helps you to understand why pair programming works, how to implement it, and when to consider not using it. Statements about pair programming are supported by data as well as stories by the authors and other practioners of pair programming. Buy this book if you want to understand pair programming better, implement pair programming in your team, or explain pair programming's benefits to someone else.
Rating: 5 out of 5
I started a bit skeptical on pairing but now a believer...
I started a bit skeptical about pairing until I read this book. After completing the book I realized that I was thoroughly mistaking about my premature conclusions and comments on the topic.
This is a very thorough, interesting and entertaining book. After reading it from cover to cover, I realized that pair-programming is not only a good thing-in many instances for most software processes-but that it addresses a problem that many individual in our field suffers from-and I am a prime examplar of a programmer with some form of the symptoms of that problem:
General lack of social skills, or interest, for interacting, communicating and working in teams to create "good" large software... as well as sharing our knowledge without prejudice and with humility. Not too mention dealing with our not so small egos...
I also realized that in some sense, I have experienced (positively) some form of pair-programming without really knowing it. At the large software company where I work, we do spend a fair amount of time reviewing code and coaching, which reminds me of some of the tactics that is proposed in the book. Further, in a recent project I personally did spend a lot of time in a "coaching" role (as the lead) with the team... and the feedback I got from members of the team was only positive.
I am convinced now that my initial attitude and thoughts towards pairing was wrong and was based on misunderstanding and probably on recollections of "expert-novice" pairing that I had experienced a few times in the past; and which is singled out in the book as one instance where pairing might not work well. Further, my "soloist" programming background coupled with a more introverted personality does not help the matter. However, I do also realize that any decent software system (delivered in competitive business time and quality) has to be done by a team and is not a trivial endeavor-I speak from experience here. So breeding "soloist" programmers is not in the interest of the field nor is it for any company. Finally, as is indicated many times, pairing might also be a lot more fun.
I know now what changes I will be pushing for, in my next project.
Rating: 5 out of 5
The perfect guide for installation and use.
This is a great book that not only covers what is good about pair programming, but also the mechanics for how to do it. Many books of this type fall into the trap of selling the technique at every chance they get (sometimes it seems just to fill pages).
This book keeps the sales pitch to a minimum and when they do tout the benfits of pair programming they do so in a consise and informative manner.
The mechanics for performing pair programming are beautifully covered with both humor and practical tips for success. Many books of this type describe implementation in terms of total success. This book doesn't fall into that trap, but discusses the pitfalls that can acompany pair programming.
I highly recommend this book for those who are actively practicing or attempting to introduce pair programming into their organization.
· Planning Extreme Programming
· Balancing Agility and Discipline: A Guide for the Perplexed
· Testing Extreme Programming
· Extreme Programming Explained: Embrace Change
· Test Driven Development: By Example