The two ways of registering event handlers are completely the same, the only difference is that the second one clutters your code less.
这两种事件注册的方式其实完全一样的，只是第二种方式会使代码看起来凌乱一点。
Give things names that are long and clear enough that you understand what they are, but not so long and awkward that they make the code less readable.
所给出的命名应该尽量长且足够清晰以便您能理解其含义，但也不能过长或太过怪异，如果这样，代码的可读性就会受到影响。
Using stored procedures is one way to make the code less depending on the exact data layout, and allows you to make changes without a lot of down time.
使用存储过程是使代码不依赖于精确的数据布局的一种方法，让你没有很多时间的变化。
This model requires both parties to stick to a programming convention that may not be relevant to the software's basic functionality and, in general, can make the code less reusable.
这种模型需要双方都坚持一个可能与软件基本功能无关的编程约定，而且在一般情况下，这个编程约定可能使代码更加不可重用。
Third, the model to model authoring has also been much improved, with a lot of new capability available directly from the mapping tool, which means you have to revert to code less often.
第三，模型到模型创作也得到了很大改善，大量有用的新功能可以直接从映射工具中获得，这意味着您不需要转换成代码。
By handling content in this way, you have much less code in each of your handler methods.
通过以这种方式处理内容，每个处理程序方法中的代码就要少得多。
As you can see, this data is far more useful than a single error code and less work to troubleshoot.
正如您所见，这些数据远比单个错误代码有用，并且所需的错误诊断工作也更加少。
As a result, less code is downloaded, and as illustrated in the preceding architecture contrast, this approach results in a reduced number of transactions.
因此，只需加载更少的代码。在与前面的架构的对比中，我们看到这个方法减少了事务的数量。
Reusing other people's code means you often end up writing less code - and less code in all likelihood means fewer defects.
重用其他人的代码意味着您常常只需编写更少的代码—而更少的代码意味着更少的缺陷。
The way you fight this complexity is with less software. Less software means less features, less code, less waste.
战胜这种复杂性的方法就是要更精简的软件，这意味着更少的特性，更少的代码和更少的浪费。
The less code you write, the less you have to maintain, the fewer bugs you're responsible for, and the better off you'll be!
编写的代码越少，维护工作就越少，所产生的错误也就越少，这样您的工作就越是得心应手！
When you learn to work this way, you may find that new implementations occur to you, and you will write far less code than you did before adopting TDD.
当掌握以这种方式工作时，您可能会发现新的实现，并且编写的代码要远远少于采用TDD时编写的代码。
Less code and queries improve throughput.
较少的代码和查询将提高吞吐量。
You can examine the coverage analysis data to help you determine which subset of the automation suite needs to be run, allowing you to validate the new code in less time.
这时您就需要检查覆盖率分析的数据，以帮您确定哪些自动化测试的子集需要运行，这样就可以让您在更短的时间内验证新的代码。
Services built using ROC have proven to be small, simple, flexible and require less code compared conventional approaches.
使用ROC建立的服务被证实是小巧、简单、灵活的，并且和传统方式相比较需要实现的代码更少。
Compared with most other languages and frameworks, it takes less code to accomplish most common tasks.
与其他语言和框架比较起来，它使用了更少程序去达到更多常见的任务。
But they're still worth using, because they'll help you identify potential problems in your code in much less time than a manual search.
但是使用它们仍然是值得的，因为与手工查找相比，它们将帮助您在短得多的时间内识别出代码中的潜在问题。
You should do whatever possible to increase the productivity of individual programmers in terms of the expressive power of the code they write. Less code to do the same thing (and possibly better).
我们应当“不择手段”地提高程序员个体的生产力，使他们写出具有很好表达力的代码。
The trade-off is that connecting to an in-memory database will take little more unit test time, but there will be less code and development effort.
虽然连接到内存数据库会多花点时间，但代码相对要少很多，开发代价也小。
Applications built using ROC have proven to be small, simple, flexible and require less code compared to other approaches.
与其他方式相比，使用ROC构建的应用已被证明是小巧的、简单的、灵活的，并且无需太多代码。
The disadvantage is that users may not want to edit code, and the code becomes less clear.
缺点是用户可能不想编辑代码，代码变得更加不够清晰。
Optimized code is often less maintainable than slower but more natural equivalents.
与更慢但更自然的代码相比，优化后的代码通常更难以维护。
More-expressive languages make it easier to find idiomatic patterns because the code contains less noise.
表达性更好的语言可以帮助开发人员更加轻松地发现惯用模式，因为代码中包含的无用信息更少。
This code USES more or less the same methodology as the code editor in Listing 2.
上述代码采用了与清单2内的代码编辑器相同的方式。
Note that the rest of the code is more or less the same as Listing 11.
注意，这段代码的其余部分类似于清单11。
Using this approach, as Rails does, you get the best of both worlds: concise code with less repetition without sacrificing flexibility.
像Rails那样使用这种方法，您可以两全其美：具有较少重复的简洁代码而不会失去灵活性。
All of this translates into less code (which is always a good thing), fewer chances for bugs, and decreased maintenance.
所有这些都可帮助减少代码(这始终是一件好事)，出现错误的几率就越小，维护工作量也减少了。
You were able to develop it rapidly and had to write less code because you took advantage of Grails.
由于利用了Grails，因此您能够快速开发该应用程序，而且只需编写较少的代码。
Instead, Sitebricks lets you create Web applications while writing a lot less code.
而Sitebricks允许在创建Web应用程序时编写相对较少的代码。
Groovlets make controller coding a snap: they require less code and provide needed objects automatically.
Groovlets使得编写控制器变得非常简单：它们需要更少的代码并自动提供了所需的对象。
应用推荐