Investigate memory problems in production code.
研究产品代码中的内存问题。
It must be kept as clean as production code.
它必须像生产代码一般保持整洁。
We might want to perform error checking for production code.
我们可能想要对产品代码执行错误校验。
Before writing any production code, we'd write our unit tests.
在实际开始编写产品代码之前，我们需要编写单元测试。
Unfortunately, I see this one in production code more times than not.
遗憾的是，我在生产代码中多次？
Note that this overhead processing is not enabled for the production code.
（注意，不要为生产代码启用这种开销很大的处理）。
Speaking of production code, one downside to DI is that it can feel viral.
说到生产代码，DI的一个缺点是它可能感染病毒。
Which one would you rather see in production code that you have to maintain?
在必须维护的生产代码中，您更愿意看到哪一个？
the date of pack which may be shown as a lot number or production code number;
3可能会显示出作为一个批号或生产编号的包装日期;
Which one would you rather see in production code that you have to maintain ?
在必须维护的生产代码中，您更愿意看到哪一个？
Your goal is not to write your eventual production code, at least, not right away.
您的目标并不是编写最终的生产代码，至少现在不是。
In production code, you would change this as dictated by your program requirements.
在生产性代码中，可以根据程序的需求修改这一声明。
Playing with the concepts without worrying about your production code is a lot of fun.
通过示例深入了解概念但又不用考虑生产代码是很有意思的。
Note: Production code should handle requests for attributes that do not exist in the array.
注意：生产代码可以处理对数组内不存在的属性的请求。
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.
我们甚至在试验代码中用了四年之后还很少在生产代码中使用它们。
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%。
With our design artifacts, we can move directly into coding a proof-of-concept, or writing the production code for our system.
通过我们的设计工件，可以直接进入为系统作概念证明编码，或者编写产品代码的阶段。
I will write up a blog entry for each LINQ operator, probably including all of the production code but only "interesting" tests.
我将为每个LINQ操作符写一篇博文，其中将包含几乎所有的成品代码，不过测试代码的话我只会把有趣的部分贴出来。
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 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.
编程对子：所有代码都是坐在同一台机器前的两个程序员共同编写的，因此所有代码在编写的同时就完成了复查工作。
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来预防进入产品代码的内存访问的违规。
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来预防进入产品代码的内存访问的违规。
应用推荐