- Paperback: 288 pages
- Publisher: Addison-Wesley Professional; 1 edition (July 8, 2002)
- Language: English
- ISBN-10: 0201745763
- ISBN-13: 978-0201745764
- Product Dimensions: 7.3 x 0.7 x 9.2 inches
- Shipping Weight: 1.1 pounds (View shipping rates and policies)
- Average Customer Review: 11 customer reviews
- Amazon Best Sellers Rank: #228,823 in Books (See Top 100 in Books)
Enter your mobile number or email address below and we'll send you a link to download the free Kindle App. Then you can start reading Kindle books on your smartphone, tablet, or computer - no Kindle device required.
To get the free app, enter your mobile phone number.
Pair Programming Illuminated 1st Edition
Use the Amazon App to scan ISBNs and compare prices.
Frequently bought together
Customers who bought this item also bought
From the Back Cover
Pair programming is a simple, straightforward concept. Two programmers work side-by-side at one computer, continuously collaborating on the same design, algorithm, code, and test. It produces a higher quality of code in about half the time than that produced by the summation of their solitary efforts. However, nothing is simple where people and personalities are involved--especially people who are accustomed to working alone. The leap to pair programming for a variety of software development projects is one that yields many benefits. However, it is also one that requires careful thought and planning.
Written as instruction for team members and leaders new to pair programming and as an improvement guide for experienced pair programmers, Pair Programming Illuminated explains both the principles underlying this method and its best practices. The authors, drawing on their own extensive experience, explain what works and what does not, what should be emphasized and what should be avoided. Two case studies further illuminate pair programming in practice: one in the context of extreme programming (XP), with which it often is associated, and one linked to a more disciplined software engineering process.
Key topics include:
Special appendices include:
With this book in hand, you will quickly discover how pair programming fits the needs of your own organization or project. You then will see exactly how to get started with this method, and how to do it right.
About the Author
Laurie Williams has applied the XP methodology to various projects. She is an organizer of the main XP conferences held thus far.
Robert Kessler is a professor in the School of Computing at the University of Utah, from which he holds his Ph.D., and a past department chair. Bob has founded a number of technology companies and is on the board of several others.
Top customer reviews
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.
- how to spread the pair programming practice across our organization,
- how to argue with the people who did never try pair programming but was against it,
- how to overcome management resistance to pair programming,
- how to gain support and acceptance from our peers,
- how to organize workplace layout in details, how to rotate pairs ...
This book has answered all the questions.
The authors did the awesome homework analyzing lots of books related to project management, software development and human relations. You will find lots of references. However, the book contains only a few authors' own assertion. The authors prefer to base on someone else's books and publications, logically combining and deducing them.
The most valuable aspect of the book is that the authors have interviewed lots of Pair Programming experts, who gave the answers to most specific questions.
This book is purely focused of pair programming, so if you have not had an exposure to extreme programming I recommend you read "Extreme Programming Explained: Embrace Change" by Kent Beck and Cynthia Andres first.
We started practicing XP in our development team. Our manager got several copies of XP Explained book for us. As I have already read it, I read another book about XP: "Extreme Programming Applied: Playing to Win." After that, I found this one and let me tell you, it is a real treasure. Some of the times, when I came to the office and we had the stand-up meeting, we discussed how we could make XP work better for us. There were so many things from real life that were in this book!
This book is very easy to read and very true to practices of pair programming. You won't be disappointed.