结对编程是极限编程（XP）的主要实践之一。 它的字面意思是两个人在一台计算机上工作，通常一个人负责键盘（通常称为驱动程序），另一个人负责操作（称为乘客或猎枪）。 它被认为可以提高生产效率和生成代码的质量，并强制执行代码的组所有权——这是 XP 的另一个宗旨。
Pair programming is one of the main practices in Extreme Programming (XP). It does literally mean two people working on one computer, usually one at the keyboard (often referred to as the driver) and a partner (referred to as the passenger or shotgun). It is reputed to improve productivity and the quality of the generated code as well as enforce group ownership of the code - another tenent of XP.
Pair programming is a software development technique in which two programmers work together at one keyboard. One types in code while the other reviews each line of code as it's typed in. The person typing is called the driver. The person reviewing the code is called the observer1 or navigator. The two programmers switch roles frequently (possibly every 30 minutes).
While reviewing, the observer also considers the strategic direction of the work, coming up with ideas for improvements and likely future problems to address. This frees the driver to focus all of his or her attention on the "tactical" aspects of completing the current task, using the observer as a safety net and guide.
When in doubt, ask Wikipedia: Pair Programming. The general idea is to have one person writing code while the other scans for mistakes and cohesiveness.
Paired programming is when two developer work on the same story card sharing a single computer and keyboard. It is considered an extreme programming practice. Extreme programming takes something positive, in this case a code review, and takes it to the extreme. The benefits beyond the continuous code review are as follows:
Improved quality: A pair of active programmers working on the same story card will complete the card with less defects
Improved productivity: a pair is less likely to be slowed down if not outright blocked when solving a problem. Furthermore, it is harder to take an email or web vacation when you are working with a partner ... you don't want to let the partner down. You will solve the problem with a cleaner design and less lines of code when working as a pair
Eliminate silos of knowledge: With rotating pairs, you will learn application and domain business knowledge across the team. The team is less likely to be blocked because Sue when on vacation and no one else knows her code.
Knowledge Transfer: Rotating pairs teach new skills (engineering and domain) to each other as they work together. The level of the team will rise for everyone and the knowledge propagates through the team.
Team self selects: The team learns one anther's skills and will quickly weed out someone that is not performing.
发布评论
评论（5）
结对编程是极限编程（XP）的主要实践之一。 它的字面意思是两个人在一台计算机上工作，通常一个人负责键盘（通常称为驱动程序），另一个人负责操作（称为乘客或猎枪）。 它被认为可以提高生产效率和生成代码的质量，并强制执行代码的组所有权——这是 XP 的另一个宗旨。
Pair programming is one of the main practices in Extreme Programming (XP). It does literally mean two people working on one computer, usually one at the keyboard (often referred to as the driver) and a partner (referred to as the passenger or shotgun). It is reputed to improve productivity and the quality of the generated code as well as enforce group ownership of the code - another tenent of XP.
http://en.wikipedia.org/wiki/Pair_programming
http://en.wikipedia.org/wiki/Pair_programming
如有疑问，请询问维基百科：结对编程。 总体思路是让一个人编写代码，而另一个人则扫描错误和凝聚力。
When in doubt, ask Wikipedia: Pair Programming. The general idea is to have one person writing code while the other scans for mistakes and cohesiveness.
测试驱动开发的实践者有时使用的结对编程扩展是乒乓球配对。
Ping Pong Pairing 的工作原理类似于：
Ping 的好处之一Pong Pairing 的特点是，任何一个开发人员都很难睡很长时间;-)
An extension of Pair Programming sometimes used by practitioners of Test Driven Development is Ping Pong Pairing.
Ping Pong Pairing works something like:
One of the benefits of Ping Pong Pairing is that it's tough for either developer to sleep very long ;-)
结对编程是指两个开发人员共享一台计算机和键盘，在同一张故事卡上工作。 它被认为是一种极限编程实践。 极限编程需要一些积极的东西，在本例中是代码审查，并将其发挥到极致。 持续代码审查之外的好处如下：
Paired programming is when two developer work on the same story card sharing a single computer and keyboard. It is considered an extreme programming practice. Extreme programming takes something positive, in this case a code review, and takes it to the extreme. The benefits beyond the continuous code review are as follows: