结对编程的特征之一就是，如果你正确地使用了这种方法，那么在一天结束的时候，你的屏幕上应该会沾满油腻的手指印。
One of the clichés of pair programming is that if you're doing this method right, your screen should be covered with greasy finger-marks by the end of the day.
这就是某个开发者对结对编程的牵强解释。
That's how one developer explained his reluctance to pair program.
他们转向短迭代，回归测试套件和结对编程。
They have moved to short iterations, regression test suites, and pair programming.
结对编程(未改动)。
InfoQ中有更多结对编程的内容，就在这里。
一个极度自信的开发者也可能会抛开结对编程这一方式。
An overly assertive developer can also throw off a pair programming session.
而结对编程时，不顺利的开始和早期犯的错误都会被别人看到。
When pair programming, your false starts and early mistakes are visible to others.
过程部分会涉及测试、问题解决以及结对编程方面的思想，还有其他主题。
The process portion gets into philosophies on testing, problem solving, and pair programming, among other topics.
没试过XP，但我想我们精心地选择了一些实践，比如结对编程。
We never tested XP, but I think we have cherry-picked some parts of it - like pair-programming.
从结对编程开始，到尽早、频繁发布软件，在整个流程中集成了很多反馈过程。
He mentioned that right from pair programming to releasing the software early and often, there is enough feedback built into the entire process.
针对采取结对编程的团队：我们推荐使用接入扩展坞的大型(23英寸)纯平显示屏。
For teams using pair programming: we recommend large (23 inch) flatscreen monitors, connected to the docking stations.
在程序员解释他们为什么认为结对编程很愚蠢的所有原因中，最可怕的原因是他们害怕。
Of all the reasons programmers might give for why they think pair programming is stupid, the scariest one is that they're afraid.
在一些公司某些项目中结对编程会增加产出率，但是在其他项目中却没有受益甚至有反作用。
In some companies and on some projects pair programming will increase productivity. While on other projects there will be no benefits or even degradation.
由于来自同侪的压力而不使用不好的实践，有人已经明确地指出这是有效的结对编程的优势。
Peer pressure not to slip into bad practices is a clearly identified benefit of effective pair programming.
很多开发者不愿意进行结对编程，并不是因为他们不会编码，而是因为他们不熟悉结对编程。
Many developers struggle with pair programming, not because they don't know how to code, but because programming in pairs is such an unfamiliar way of working.
结对编程是一门敏捷软件开发的技术，其目的是让两个开发人员共同在同一个工作站上工作。
Pair programming is an agile software development technique in which two programmers work together at one workstation.
这样我们应该期望，比起单独的编程团队，通过结对编程可以对时间和难度进行更准确的估计。
We should therefore expect more accurate estimates of time and difficulty by a pair programming team than from a solo programming team.
后来我跟Corey一起结对编程，我们用这种方法尝试着写了一些测试驱动代码。
Later I paired with Corey and we test drove some code using this approach.
有个开发者在他的blog中写道：“结对编程会使他们暴露他们真正的知识和技能水平”。
One developer wrote in his blog that pair programming forces developers to show the real state of their knowledge and skills.
结对编程很自然地使开发者向同事敞开胸怀，分享领域知识，并时刻准备把你的方法与大家分享。
Pair programming naturally involves being open with colleagues, sharing domain knowledge, and being prepared to explain your approach.
其他一些人(包括George Dinwiddie)的建议是，花点时间与这个人结对编程。
Various people's advice, including George Dinwiddie, to taking some time to pair program with this person.
当结对编程的人员在某项活动中发现新的需求时，他们可以更新卡片，再回到之前的活动中。
As soon as a pair realizes that there is an additional requirement during the course of an activity, they can update the card and get back to their activity.
作为使用结对编程的开发者，我自己的的经验是这样的，它并非只是一种一个人编码，另一个人观察的技术。
My own experience as a developer using pair programming is that it isn't just a technique where one person programs and the other person watches.
所以，尽管成功的结对编程者通常更多地会关注同样的东西，但是他们也可能会注意到不同的东西。
So, although successful pair programmers will concentrate mostly on the same things, they might notice different things.
作为规则，XP假设团队一直使用所有实践，但团队可以挑选几个实践，并成功使用它们(诸如重构或结对编程)。
XP as a discipline assumes a team is using all of the practices all of the time, but a team can pick a few practices and use them successfully (such as refactoring or pair programming).
值得牢记的是：当你了解了其它团队成员，并且熟悉每个参与者的个性之后，结对编程就会变得容易起来。
It's worth remembering that it gets easier as you get to know other team members and gain a clearer understanding of the personalities involved.
X tremeConnect——一种虚拟的结对技术，可以通过Skype和TightVNC进行远程结对编程。
XtremeConnect - a virtual pairing technique that allows for remote pair programming via Skype and TightVNC.
最内层的级别包括比较底层的实践，比如结对编程、编码标准、单元测试和功能测试、重构、简单设计，以及每周工作40小时。
The innermost level consisted of lower level practices such as pair programming; coding standards; unit and function testing; refactoring; simple design; and the 40-hour week.
而结对编程比较不容易受到不好的实践的影响，因为程序员们会承诺以特定的方式编写代码，并确保两个人都信守承诺。
Pair programmers might be less susceptible to poor practices because they can promise to write code in a particular way and ensure that each other's promises are kept.
与此同时，CoreyHaines开始了他的结对编程之旅，帮助传播软件工艺的思想。迄今他已访问了几十个人、团队和城市。
At the same time, Corey Haines started his Pair Programming Tours, which have helped spread the word about software craftsmanship as he has visited dozens of individuals, teams, and cities.
应用推荐