结对编程 in English translation

• pair programming
• to pair program

Examples of using 结对编程 in Chinese and their translations into English

我工作过的公司尝试过的方法的一个例子-就像快速删除一样-是结对编程（不要与PEAR编程混淆）。
One example of a methodology that a company I worked for tried- and just as quickly dropped- is pair programming(not to be confused with PEAR programming)..

如果在结对编程中应用番茄工作法技术（Pomodoro），那就需要你们有规律地互换你们的角色，这可以始你们保持醒觉，并且更加投入。
The Pomodoro technique, when applied to pair programming, will enable you to switch roles regularly, in order to remain alert and truly engaged.

程序员经常说他们更喜欢结对编程。
Programmers often state that they prefer pair programming.

然而在结对编程时TDD是单独进行的。
TDD comes into its own when pair programming, however.

但在结对编程中，人们持续地一起工作。
But with pair programming, people continually work together.

所有的代码应使用结对编程（PairProgramming）.
All production code is pair programmed.

另一方面，有一些情况会破坏结对编程的效率：.
On the other hand, there are some situations which can undermine the effectiveness of pair programming.

结对编程可以提高软件质量，而且还不会影响交付进度。
Pair programming increases software quality without impacting time to deliver.

开发人员也看到了结对编程的明显好处。
Solar installers also have seen the benefits of the program.

结对编程提高了软件质量，却并不会影响交付时间。
Pair programming increases software quality without impacting time to deliver.

更有甚者，我喜欢它的哥哥--结对编程。
And even more, I like its older brother better: Pair programming.

但是，有一件我一直被排除在外的事是结对编程。
But one thing that I have always felt shut out of is pair programming.

非常适合那些想与他人一起学习或结对编程的人。
Great for those who want to study with others or do pair programming.

瞬时的代码审查，也称为结对编程(pairprogramming)；.
Instant code review, also known as pair programming;

但是我们能说在所有情况下结对编程都是最好的方法吗？?
But can we say that Pair Programming is the best method in all situations?

结对编程是两个开发人员在一个工作站上编程的实践。
Pair programming is a practice where two developers program together at one workstation.

DaveNicollete用数字说话，告诉大家结对编程是如何省钱，而不是浪费钱的。
Dave Nicollete offers some quantitive ideas to help show how pair programming can save money, not waste it.

不幸的是，结对编程是一个代价高昂的错误。
Failing to plan is a costly mistake.

我认为不到20年，我们将看到一些颇明智且复杂巧妙的结对编程模式。
In 20 years, I suspect that we will see some pretty clever and sophisticated remote pair programming styles.

结对编程是代码评审的有效替代抑或只是增加了商议沟通代价?
Is pair programming a superior replacement for code review or just a way to inflate consulting rates?