没有重构过程可以再降低图案的能量级别。
There is no reconstructive process that can lower the pattern's energy level.
当你没有重构时，你同样也不会留意重构的机会。
When you don't have refactoring, you don't watch for opportunities for refactoring as much.
重构：没有重构，要找出可重用的公共工作流块会很困难。
Refactoring: no refactoring, making it harder to identify common workflow chunks for reuse.
我想，一些简单的重构可以在没有单元测试的情形下进行。
I imagine some simple refactorings can be performed even without unit testing in place.
重构不同于自动代码生成，它重新构造了代码，却没有改变其功能性。
Refactoring differs from automated code generation in that it restructures the code without changing the functionality.
服务模型成为SOA中进行敏捷开发的基本工具，因为没有该工具，就很难控制服务重构。
The model of services becomes an essential tool for agile development in a SOA, because without it, it is very hard to control service refactoring.
重构每一项项目上的产品是没有什么效率的。
It is not efficient to recreate these artifacts on each program.
为代码重构所提供的项目模板中并没有包含可用的演示程序，但是在此我们可以使用快速修正教程中所展示的相同技术。
The project template for code refactoring doesn't include a usable demo, but the same techniques shown in the Quick Fix walkthrough can be used here.
与没有相应测试案例的代码相比，经过测试的代码更容易重构、维护和增强。
Tested code is easier to refactor, maintain, and enhance than code without corresponding test cases.
这是英雄般的重构故事，几乎没有人能在经历了这些之后活着讲述这样的故事。
This is refactoring on a heroic scale and few have lived to tell this tale.
没有好的测试集的代码通常有很多问题，难于进行有信任度的改变，并且难以重构。
Code without a good test suite is typically buggy, hard to change with confidence, and poorly factored.
不可想象的准确性，以及它没有代码重构的需求，使得它成为监测现存应用程序(通常存在于当前风险中)的一种切实可行的工具。
The out-of-the-box accuracy, and its having no code-refactoring requirements, make it a viable tool for scanning existing applications (which often present very current risks).
但即便您并没有使用要求进行正式重构的方法，Eclipse的重构工具还是可以在进行一般的代码修改时提供节约时间的方法。
But even if you are not using a formal method that requires refactoring, Eclipse's refactoring tools provide a time-saving way to make common types of code changes.
在添加对其他文件类型的支持之前，应该确保TagLib重构没有破坏已有的功能。
Before you add support for other file types, you should make sure that your TagLib refactoring didn't break existing functionality.
不要害怕扔掉代码.重构和重新编码是两个非常重要的领域.当你遇到已经不存在的需求,或者你没有意识到你能找到比开始编写的代码更好地解决旧问题和新问题的方案,如果你遵循上面的建议,需要重构的代码已经最小化了.如果你没有遵循上面的建议,你可能需要重新编码.
Many developers solve their problem while they are coding, and there is nothing wrong doing that. As a matter of fact, you can do that and still adhere to the above statement.
如果您象按照食谱那样严格遵循这些技术，那么您在学习重构时应该没有太大的麻烦。
If you follow the mechanics closely like a cookbook recipe, you should be able to learn the refactoring without much trouble.
有些时候，甚至不会有第二个开发者：一旦你意识到你可能会有问题（或者，很多问 题），没有人能够阻止你重构你的项目。
Sometimes, though, it might even be the original developer: there's nothing to prevent you from rescuing your own project once you realize that you have a problem (or, more likely, many problems).
尽管该菜单选项只在重构之后的有限时间内有益，但是如果没有该菜单选项，而您更改了所涉及的任何文件的话，您将无法再取消重构。
Although this offer is only good for a limited time after refactoring. If you change any of the files that are involved, you won't be able to undo the refactoring anymore.
您可能还没有在测试第一的开发中成功过，但测试会间接给您带来重构代码的便利。
You may not have success with test-first development, but accumulating test collateral gives you the freedom to refactor your code.
不管你的团队采取何种方法，都没有任何东西可以阻止你对代码进行重构。
So there is nothing to prevent you from refactoring your code no matter the methodology your team might subscribe to.
尽管我使用了一个简单的示例进行说明，但是我并没有要刻意忽略这项重构技巧的复杂性。
Although I'm using a simple example for illustrative purposes I don't mean to trivialize the possible complexity of this refactoring technique.
接着下一个测试必须使用不同的参数值，迫使我们实现正确的算法，以通过所有的测试，即使我们还没有开始下一个环节的重构。
However, the next test might use different parameter values, forcing us to implement a proper algorithm in order to pass both tests, even if we didn't refactor as described next.
在每一次重构之后，程序的外部功能仍然没有得到更改。
With each round of this refactoring, the external functionality of the application remains unchanged.
这将意味着购买更多内存对重构时间没有帮助。
This would mean that purchasing more memory wouldn't help with the rebuilding time.
映射表允许用户执行标量映射，也就是要执行没有组合语义且不更改结构维度的重构。
The mapping table allows the user to perform scalar mappings, which is to perform restructures that do not have set semantics and that do not change the dimensions of the structures.
毕竟，通常没有人能活过32,000岁——而且我相信，即使真的有那么长寿的人，仍然可以重构代码，将该字段改回整型。
People don't generally live beyond 32,000 years, after all — and I think it's safe to suggest that if that does ever become a concern, you'll be able to refactor the code back to an integer field.
而烂程序员写出来的代码连基本的概念完整性都达不到，更何况没有冗余，拥有明晰的层次结构了，所以这样的代码很难去重构。
Bad programmers write code which lacks conceptual integrity, non-redundancy, hierarchy, and patterns, and so is very difficult to refactor.
没有单元测试重构照样能够工作。
边做边修改架构(重构)而没有一些初始的架构设计，对大型企业系统来说是不适合的。
Fixing architecture as you go (i.e. refactoring) without some initial architectural design is not appropriate for large-scale enterprise systems.
边做边修改架构(重构)而没有一些初始的架构设计，对大型企业系统来说是不适合的。
Fixing architecture as you go (i.e. refactoring) without some initial architectural design is not appropriate for large-scale enterprise systems.
应用推荐