Each of these localized assemblies contains only resources and no code.
每个本地化程序集只包含资源，不包含代码。
New tenants can be added by adding new routing rules using configuration steps only and no code development is required.
可以通过添加新的路由规则添加新租户，这只需使用配置步骤，且不需要代码开发。
This behavior can now be changed on the fly by changing the policy in the registry, and no code changes or redeployment of code is required.
现在可以通过更改注册中心的策略来动态更改该行为，并且不需要进行任何代码更改或代码重新部署。
Running the engine or compiler for the presentation technology converts it to the proper format, and no code changes have to be made (in the typical case).
运行表示技术的引擎或编译程序将标记页面转换为适当的格式，并且不需要修改任何代码(典型情况下)。
And this all can be done with no mutable state in the client code.
在客户代码中，这些都可以在不使用可变状态的情况下就能做到。
What if you only wrote enough code to get the test to pass, and no more?
如果您只编写足够通过测试的代码，而不写多余的代码会怎样？
In my opinion, code has no place in configuration files anyway, and allowing users to execute arbitrary code is a bad idea.
在我看来，配置文件中无论如何都不应该存在代码，并且允许用户执行任意代码是个坏主意。
A method without much code and with no loops at the top of a profile is probably being called very frequently.
如果一个只有少量代码并且不包含循环的方法位于配置文件的顶部，那么它可能正被频繁调用。
This is all transparent to the user and no special code needs to be written.
这对于用户来说是全透明的，不需要任何额外的代码需要编写。
As a result, crosscutting concerns like logging, transactions, and security no longer intrude on your application code.
因此，横切关注点(如日志、事务和安全)不会再干扰应用程序代码。
Write just the code you need and no more. Your app will be leaner and healthier as a result.
只写你需要写的代码，绝不多写。结果你的应用将更加精简和健康。
The code runs as expected, no compiler errors or issues and - most usefully - the code is self-documenting: the intention is clear.
代码的运行结果与预期一致，没有编译错误，最重要的是这段代码的可读性非常好：其意图是非常清晰的。
Without a transaction there is no trigger for the ORM to generate SQL code and persist the changes, so the method simply ends - no exceptions, no updates.
没有事务，就不会触发orm去生成SQL代码和保存更改，因此只会终止方法—没有异常，没有更新。
Basically, you just write format conversion code, and have no ability to affect either the input or output format.
基本上就是编写格式转换代码，对输入和输出格式都无能为力。
This behavior came back to haunt me as the project deadline grew near and still no usable code appeared.
结果项目截止期限临近，却没有写出可用的代码，这可把我吓坏了。
We could demonstrate fantastic progress in writing code, and no progress on delivering code.
我们或许可以在代码编写上显示卓越的进步，但在代码提交上却显然不足。
There is virtually no unbreakable code, given enough Red Bull and a dedicated hacker.
事实上，只要有足够的红牛和一个有恒心有毅力的黑客，世上便没有牢不可破的代码。
There is no need to write and test code during a method development project, but there is still a need for testing all links and usage threads.
在方法开发项目中，没有必要编写和测试代码，但是仍然需要测试所有的连接。
The design considerations for switches like these are challenging: extreme reliability, no downtime (hot code upgrades), and massive concurrency.
设计这种交换机很有挑战性，需要考虑几个因素：高可靠性、无停机时间(热代码升级)、大规模并发性。
We have found with Eclipse that we go through the wizard and then take it from there -- no copying and pasting of code is necessary.
使用Eclipse，我们发现可以遍历向导，然后从那里获取代码 —不必复制和粘贴代码。
Jubula tests are quicker to develop and more robust as there is no code to maintain.
Jubula测试的开发速度很快，健壮性也更好，因为它根本就没有什么代码需要维护。
Source and target matching no longer requires processing on the server, and the technique also removes menu generation code from the server.
源和目标的匹配不再需要在服务器上匹配，而且该技术还从服务器上删除了菜单生成代码。
Even those who find no sense in that code understand and can easily accommodate it.
甚至那些对此规则没感觉的人也会理解并能很容易地适应。
Reading and writing code is no different.
阅读和编写代码没什么不同。
Because there is no need to add code and complexity to deal with these limitations, development can proceed much faster.
由于不需要添加代码和复杂性以处理这些限制，开发可以更快地进行。
There is no visualization or harvesting of models from existing source code — and without a merge as identified previously, there is certainly no notion of round-trip engineering.
如果没有对已有源代码的可视化或者获取模型的—并且没有对之前被识别的代码进行合并，就不会有双向工程的概念。
But it is fair to ask: Why don't we scale back the obsession with "bubbling things in" and challenge students everywhere - no matter their ZIP code - to show their innovation and creativity?
但是问一问是公平的：问什么我们不成比例缩减对“泡沫事物”的痴迷，向四处的学生挑战——不管他们的邮政编码——以激发他们的革新力和创造力？
The challenges in static analysis come from the fact that it has no visibility into modules and code that it does not see or understand.
静态分析中的挑战来自它对没明白或者理解的单元和代码没有可视性的事实。
Once you have given out your code and you no longer have access to all the clients, then you're in the API business.
一旦你给出了你的代码就不再访问所有的客户的话，那么你就是使用了提供API的这种模式。
As for source code and internal implementation, there's no relationship at all, of course.
至于源代码及其内部实现，当然，根本就没有关系。
应用推荐