Speaking of production code, one downside to DI is that it can feel viral.
说到生产代码，DI的一个缺点是它可能感染病毒。
This is a great idea when debugging, but you probably won't want to use it in production code.
虽然在调试时这是一个不错的想法，但是您可能并不希望在产品代码中这样使用。
Note that in production code you will want to include proper error handling among other things.
注意，在生产代码中，还需要包括适当的错误处理代码。
We have rarely used them for production code, even after four years of usage in experimental code.
我们甚至在试验代码中用了四年之后还很少在生产代码中使用它们。
You are not allowed to write any production code unless it is to make a failing unit test pass.
在写完“红色”(无法通过测试)的单元测试代码之前，不允许写任何的产品代码。
In production code, you would not want that; but for early testing, something like what I do is helpful.
在产品代码中，您将不会希望有这样的选择；但对于早期的测试，就象我所做的这些，是很有帮助。
Each target object that you test must have at least two clients: your production code, and your test case.
进行测试的每个目标对象必须具备至少两个客户机：生产代码和测试用例。
Remember: this is an example to show the concepts and should not be implemented in production code like this.
请记住：这是一个展示概念的示例，不应在生产代码中这样实施。
This means that you can use it in any number of different circumstances: unit tests, production code, and so on.
这意味着您可以在不同的情况下使用它：单元测试、生产代码，等等。
The best Ruby programmers I know all suggest coverage of production code of over 80%, and some strive for 100% coverage.
所有我认识的优秀Ruby程序员都建议产品代码的覆盖率要高于80%，有的甚至建议要尽力达到100%。
You could get around this by catching and rethrowing, but then you've got boilerplate in your production code again.
你可以通过捕捉并积极解决这个问题，但是你有样板生产代码中再次。
With our design artifacts, we can move directly into coding a proof-of-concept, or writing the production code for our system.
通过我们的设计工件，可以直接进入为系统作概念证明编码，或者编写产品代码的阶段。
In everything we do, whether writing tests, writing production code, or refactoring, we keep the system executing at all times.
我们在做任何事情时(无论是写测试、写产品代码还是重构)，都要保证系统能够一直运行。
I will write up a blog entry for each LINQ operator, probably including all of the production code but only "interesting" tests.
我将为每个LINQ操作符写一篇博文，其中将包含几乎所有的成品代码，不过测试代码的话我只会把有趣的部分贴出来。
Merging results will sometimes fail if you have recompiled your production code between the tests whose results you want to merge.
如果在要合并结果的测试之间，您重新编译了实际执行程序码，有时候合并结果会失败。
What if every line of production code were reviewed by somebody who was intimately familiar with what the code was supposed to be doing?
如果每行生产代码都被一个对代码的意图非常熟悉的人复查过会怎样？
So, if you've been wondering how Scala applies to your production code, you should now be ready to take your first steps to finding out.
因此，如果您想知道如何在您的生产代码中应用Scala，就应该准备好迈出探索的第一步。
During the rest of the iteration, the team will implement the features they signed up for, pair programming on all production code.
在迭代周期的其他时间内，团队要实现他们所登记承担的任务，所有代码由编程对子一起完成。
During the rest of the iteration, the team will implement the features they signed up for, pair prog - ramming on all production code.
在迭代周期的其他时间内，团队要实现他们所登记承担的任务，所有代码由编程对子一起完成。
Pair Programming: All production code is written by two programmers sitting at one machine. Essentially, all code is reviewed as it is written.
编程对子：所有代码都是坐在同一台机器前的两个程序员共同编写的，因此所有代码在编写的同时就完成了复查工作。
If you change your production code between tests, you cannot merge results from testing the original code with results from testing the changed code.
如果您在测试之间变更实际执行程序码，便无法合并原始程序码测试结果和变更过的程序码测试结果。
On C or C++ projects, we always made it mandatory to run Purify on components to prevent memory access violations from making their way into production code.
在C或者 C++项目中，我们已经强制在组件上运行Purify来预防进入产品代码的内存访问的违规。
This exception will be caught specifically in your production code so that your application can respond graciously when a user supplies an incorrect password.
在生产代码内这个异常应被明确捕获以便应用程序在用户提供了不正确的代码时能够进行恰当的响应。
These errors should not be a problem in your final production code as long as the entire application is rebuilt for the released version of your product.
只要为产品的已发布版本重新生成了整个应用程序，这些错误在您最终的生产代码中应该不会成为问题。
Profiling memory problems in production code is greatly simplified by using the "attach to process" feature, along with the ability to import memory dump files.
通过使用“依附进程”特性，以及导入内存dump文件的功能，极大地简化了对产品代码中的内存问题的概要。
In production code, this probably shouldn't be taken for granted, but for a simple example like this, it's going to be OK 99.99 percent of the time. Caveat emptor.
在生产代码中，可能无法保证这种情况，但对于这样的简单的例子，99.99 %没有问题。
Authentication criterion SA8000, incorporating the core content of ILS, is the way ILS spread across the globe and one of the forms of modern production code.
SA8000认证标准融合了国际劳工标准的核心内容，是国际劳工标准在全球推行的方式和现代生产守则运动的形式之一。
For production code, validating and transforming textual input is better handled by back-end code (a servlet, for example), rather than by means of JSP custom tags.
对于生产代码，文本输入的验证和转换最好由后端代码(比如servlet)来处理，而不是通过jsp定制标记来处理。
For production code, validating and transforming textual input is better handled by back-end code (a servlet, for example), rather than by means of JSP custom tags.
对于生产代码，文本输入的验证和转换最好由后端代码(比如servlet)来处理，而不是通过jsp定制标记来处理。
应用推荐