最内层的级别包括比较底层的实践，比如结对编程、编码标准、单元测试和功能测试、重构、简单设计，以及每周工作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.
由于来自同侪的压力而不使用不好的实践，有人已经明确地指出这是有效的结对编程的优势。
Peer pressure not to slip into bad practices is a clearly identified benefit of effective pair programming.
如果您实在憎恨这个实践(大多数程序员不是喜爱就是憎恨“有争议的”实践，如结对编程)，如果必需的话，发泄一下，但是要克服它。
If you absolutely hate the practice (and most programmers either love or hate the "controversial" practices, like pair programming), vent if you must, but get over it.
而结对编程比较不容易受到不好的实践的影响，因为程序员们会承诺以特定的方式编写代码，并确保两个人都信守承诺。
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.
有些结对编程者认为轮换是实践中可选的部分，而且在小型团队或者是没有几个程序员愿意结对的团队中，可能没有其它的选择。
Some pair programmers regard rotation as an optional part of the practice, and on a small team, or with few programmers willing to pair, there might be little alternative.
作为规则，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).
没试过XP，但我想我们精心地选择了一些实践，比如结对编程。
We never tested XP, but I think we have cherry-picked some parts of it - like pair-programming.
针对程序员的XP实践(如结对编程，pair programming)和针对业务人员的XP实践(如告知详情)需要不同的思路，以便更好地工作。
XP practices for programmers (such as pair programming) and for business people (such as story telling) require a different way of thinking to work well.
针对程序员的XP实践(如结对编程，pair programming)和针对业务人员的XP实践(如告知详情)需要不同的思路，以便更好地工作。
XP practices for programmers (such as pair programming) and for business people (such as story telling) require a different way of thinking to work well.
应用推荐