| 1. | Pair programming : are two heads better than one
成对编程：两个头脑优于一个 |
| 2. | Won ' t pair programming cut productivity in half
难道两两组合编程不会让生产率减半吗 |
| 3. | Some programmers object to pair programming without ever trying it
很多程序员在还没有尝试过的情况下就反对成对编程。 |
| 4. | Pair programming requires you to think two heads are better than one
结对编程需要您知道“三个臭皮匠，顶得上一个诸葛亮” 。 |
| 5. | Collective ownership provides another level to the collaboration begun by pair programming
共享代码从另一个层面提供了对配对编程中协作的支持。 |
| 6. | Won ' t pair programming interfere with “ flow ” , which requires solitude and silence
编程对子会不会干扰到”顺畅性”呢？它可是需要的孤独和安静的环境。 |
| 7. | Pair programming encourages two people to work closely together : each drives the other a little harder to excel
配对编程鼓励两个人紧密协作：每个人促使另一个更加努力以图超越。 |
| 8. | Ninety percent of programmers who learn pair programming prefer it , so we highly recommend it to all teams
百分之九十的学习过成对编程的程序员都会喜欢这样，因此我们向所有的团队强烈推荐它。 |
| 9. | Research into pair programming shows that pairing produces better code in about the same time as programmers working singly
研究表明成对编程在让程序员们单独工作相同的时间内会得到更好的代码。 |
| 10. | With pair programming and collective code ownership , how are programmers supposed to be recognized and compensated
在编程对子和代码所有权归于集体的情况下，程序员们的工作是如何被认定和给于报酬的呢？ |
