This risk reduction needs to be balanced with the value of the running code and the value created by forcing hard decisions to be taken early on.
这种风险的减少需要用运行代码的价值，和由迫使及早进行困难的决定所创造的价值来平衡。
Now that you've seen all the hard ways to code EJBs, the next section will show you how to turbo-charge your productivity and optimize your application.
通过上述内容您看到了对EJB进行编码的困难之处，下一部分将显示如何提高工作效率和优化应用程序。
As it turned out, this wasn't too hard to do, as I had worked on compilers and code generators in the past.
果不其然，这并不是很困难，因为我过去从事过编译器和代码生成器的工作。
With all that repeated code, you're bound to have inconsistencies, and it will be hard to maintain.
对于所有重复的代码，一定会出现不一致性，因此将很难进行维护。
At best this caused hard to maintain code and at worst brittle code that fails when new types in the enterprise extend existing types.
即使最好的情况下这也会带来代码维护的困难，而最坏的情况当企业扩展现有类型而引入新类型时，脆弱的代码就会失效。
However hard you try, it's difficult to make this kind of bootstrapping code neat, tidy, and easy to read.
无论多么努力地尝试，使此类引导代码优雅、干净、易读也是非常困难的。
Reading code and following tutorials is fine, but until you actually try to solve some of your pain points in a given library, it's hard to know which one is right for you.
跟着教程阅读代码是不错，但是，在您用一个给定库实际解决自己的问题时，很难知道哪个适合您。
It's not hard to handle that situation, and adding the code won't take long, but we'll resist the urge to do more than we have to for right now.
处理那种情况并不难，而且添加代码不会花很多时间，但是我们不会做现在不需要做的事情。
The hard issues of parallelism and the optimizations needed to produce effective code just don't fit into the time available for a single course in compiler construction.
并行性的难题和生成有效代码所需的优化不适合在单个的编译器构造的课程中讲。
However, many situations are hard for ProGuard to analyze correctly and it might remove code that it thinks is not used, but your application actually needs. Some examples include.
但是，对于混淆器来说，大多数情况做出正确的分析是困难的，并且它或许会删除在它看来是无用的，但对于程序来说却确实需要的代码。
That’s fine for small sites, but it can quickly get out of control, resulting in reams of messy code that is hard to understand and to maintain.
对小网站来说这ok，但是很快你就会失去控制，乱七八糟的程式码将很难理解与维护。
If you simply dive in and start developing application code, you'll quickly be up to your eyeballs in scribbled notes, hard-to-find bugs, and templates that are sometimes updated and sometimes not.
如果一个猛子扎进去开始开发应用程序代码，眼前很快就会充满杂乱的注释、难以寻找的bug，以及有时已更新有时没更新的模板。
You now have a stable version and your program code has withstood the close gaze of many hard working people.
你现在有了一个稳定的版本，而你的程序代码已经经受住许多勤奋工作的人的密切注视。
While metaprogramming is powerful, using it well takes experience and the resulting code tends to be hard to understand, maintain, and debug.
元编程十分强大，但是使用它需要经验，而且会导致代码变得难以理解，维护和调试。
Since WSDL is the interface you are using between service providers and service consumers it is hard to get it "right" before any code it written.
由于WSDL是服务提供方和服务使用方之间的接口，所以很难在写任何代码之前一次就把它完全正确的定义下来并一直使用。
We weren't writing this code for our own amusement. We were a tiny startup, programming as hard as we could in order to put technical barriers between us and our competitors.
我们写这些宏不是为了自娱自乐-我们是个小创业公司，我们必须疯狂写程序，这样才能与竞争对手之间构筑技术上的壁垒。
But with innovative tools like fMRI and transcranial magnetic stimulation, and projects that are re-engineering a model of a human brain, scientists are working hard on cracking the neural code.
但伴随着功能磁共振成像和穿颅磁刺激术这样的新技术手段出现，以及人类颅脑建模计划的实施，科学家们已经在努力破解人类神经的密码。
Overly complex code is hard to test and maintain, which means it usually has a higher incidence of defects.
过于复杂的代码难以测试和维护，这通常还意味着更高的出错率。
As the GDM code says, "it's hard to be event controlled while maintaining state," so we add our own state-monitoring variables and data structures to process the keystroke-dynamics functions.
如GDM代码所示，“维护状态时很难控制事件”，因此添加我们自己的状态监视变量和数据结构来处理击键力学函数。
The reason that "continuous integration" is a central mantra for many lean and agile software engineering practices is because integrating large swatches of code is really hard to do.
“持续性集成”的理由，对于许多简洁且敏捷的软件工程来说是一个咒语，因为将大量的代码集成到一起，是一项十分具有挑战性的工作。
The idea here is to avoid duplicating and hard-wiring code.
这里的想法就是要避免复制代码以及硬编码。
It is extremely hard to predict and comprehend these possibilities and scenarios just by inspecting source code.
因此，仅仅通过检查源代码是很难预测和理解这些错误发生的可能性和发生的情景的。
POSIX thread programming has many benefits, but if you're not clear about some basic rules, you run the risk of writing hard-to-debug code and creating memory leaks.
POSIX线程编程有诸多优势，但是如果您不明确一些基本规则，就有可能编写一些难以调试的代码并造成内存泄漏。
Memory errors also can be insidious in a way common to few other classes of errors: They're hard to reproduce and symptoms often are difficult to localize in the corresponding source code.
与少数其他类型的常见错误一样，内存错误还是一种隐性危害：它们很难再现，症状通常不能在相应的源代码中找到。
Creating a simple, traditional decorator for each case is too cumbersome, and it would add so much syntax to your code that it would be hard to determine which unit of work you're aiming for.
为每个操作创建一个简单的传统修改器过于麻烦，并且会向代码添加大量语法，从而造成难以确定目标工作单元。
In the past, code generation for data drops was based on templates; however, the templates were quite complicated, difficult to understand, and hard to change.
过去，数据拖动的代码生成是基于模板的；然而，这些模板都十分复杂，很难理解，并且不易更改。
That’s hard to swallow in an industry where “a buck” is code for $1 million, and where top producers can pull down 20 or 30 “bucks” a year, or even more.
很难想象一个行业里，一头雄鹿意味着1百万美元，那些顶层的高管们得到20或30头雄鹿一年，甚至更多，除非你在华尔街工作。
The layout of data allocations in memory is complex and subtle to reproduce, so any symptoms might be hard to connect back to the specific error at the level of source code.
内存中数据分配的布局非常复杂并且难以再现，所以任何症状都不可能追溯到源代码级别的具体错误。
Testing gets complicated and usually new developers have a hard time trying to understand what the code does.
测试将变得复杂，新开发人员通常要花很长时间才能明白这个代码是做什么的。
Testing gets complicated and usually new developers have a hard time trying to understand what the code does.
测试将变得复杂，新开发人员通常要花很长时间才能明白这个代码是做什么的。
应用推荐