Continued improvements in refactoring tools.
重整工具中的持续改进。
Writing test cases first lowers your risk in refactoring.
先编写测试用例会降低重构中的风险。
This, coupled with a good tool, makes first steps in refactoring a breeze.
再加上一个好的工具，迈开重构的第一步简直就是轻而易举。
Bill Venners: in refactoring you write, "Before I used refactoring I always looked for flexible solutions."
BillVenners：在《重构》一书中你写道：“在学会重构之前，我总是力图找到灵活的方案。”
Best results in refactoring are achieved if you adopt refactoring in small steps, performing it regularly while you code.
如果你遵循小步重构，并在编码过程中定期执行，就能达到最佳的重构效果。
As most work of refactoring has been done by hand, many programmers have no interest in refactoring the existing code.
目前，绝大部分重构工作仍然得靠手工完成，因为这个原因，很多程序员不愿意进行重构。
The key point Ron makes here is that the "stop and refactor" strategy is NEVER the best choice for a team competent in refactoring.
Ron这里提出的要点是“停下来重构”从来不是擅长重构的团队应该选择的最佳策略。
Luckily, as Pramod Sadalage and I show in refactoring Databases, 1 it's quite straightforward to implement database refactorings manually.
幸运的是，如PramodSadalage和我在重构数据库中所描述的，1手动实现数据库重构是非常直接的。
Therefore, if this is true — and I'm quite sure it is true — the stop to refactor strategy is never the best one for a team skilled enough in refactoring.
因此，如果这是对的——我也非常确信它的正确性，那么对于已经精通重构的团队来说，“停下来重构”策略从来就不是最佳策略。
Bill Venners: in Refactoring, you write: "I write tests to improve my productivity as a programmer." What about robustness, quality, and reliability?
比尔：在《重构》这本书中，你写道：“通过写测试，我提高了作为一个程序员的工作效率。”能谈谈对鲁棒性、质量和可靠性的影响么？
Unfortunately, almost no automatic tools about refactoring can be in hand for benefit of our development at present, as has been the intractable problem in refactoring field.
遗憾的是几乎没有自动化的重构工具对它提供支持，这也是工程实践中运用重构技术的最大障碍。
No wonder than that .Net community is lagging behind in refactoring adoption and that there is still a lot of confusion regarding the whole issue of refactoring and its usefulness.
无怪乎.Net社区对重构的引入会大大地滞后，因为我们对于重构的所有问题及其作用，依旧混乱不堪。
Bill Venners : You say in Refactoring, "The secret to fast software in all but hard real time contexts is to write tunable software first, and then to tune it for sufficient speed."
你在《重构》一书中写道：“编写能快速运行的软件的秘诀就在于先编写可性能调优的软件，然后对执行速度进行调优。”
Bill Venners: in Refactoring, you talk about a development team you once encountered in which each team member was publishing interfaces to others and going through lots of conniptions.
比尔：你在《重构》一书中提到，曾经碰到过一个团队，所有成员都将自己的接口发布给其他成员，结果大家常常是不堪其苦。
If I want to validate this code in a white box manner, I have to separate UI-specific code from business code, which requires some refactoring.
如果我想以白盒方式验证这段代码，就必须将特定于用户界面的代码与业务代码分开，这就需要进行重构。
However, these differ from refactoring in that they add new functionality.
不过，这些特性与重构不同，因为它们添加了新功能。
If the refactoring causes problems in other methods, these are ignored and you must fix them yourself after the refactoring.
如果这种重构在其他的方法中引发问题，就直接忽略这些问题，您必须在重构之后亲自修改。
Refactoring support is currently lacking in all of the IDE plug-ins.
目前，所有的IDE 插件中都还缺乏对重构的支持。
This type of refactoring is especially useful in moving classes from one package to another.
此类重构在将类从一个包移到另一个包中时尤为有用。
In addition, refactoring an operation will update the corresponding message in a Sequence diagram, even when the Sequence diagram is in a closed model.
此外，重构一个操作将会更新序列图中相应的信息，即时当这个序列图在一个被选择的模型中。
Listing 8 shows the corresponding refactoring that occurs in the view.
清单8显示了该视图中发生的相应重构。
You might want to put off new development in only that area while you repay any technical debt in that section (refactoring code, updating documentation, and so on).
您或许想要仅在那个范围内推迟新的开发，同时在该部分内偿还技术债务(进行代码重构，更新文档等等)。
In this article, I talk about how to use refactoring to find underutilized design lurking hidden in your code.
在本文中，我将讨论如何使用重构技术来查找隐藏在代码库中的未得到充分设计的代码。
Internal refactoring to remove wrinkles in architecture.
内部重构以除去架构中的瑕疵。
The short "code, test, code, test" cycle of TDD invites refactoring in these cases, which continually drives the development of uncomplex code.
在这些情况下，TDD的简短的 “代码、测试、代码、测试”循环将导致重构，而这将继续驱使非复杂代码的开发。
As mentioned previously, in cases where this refactoring results in an error, whether flagged or not, you can continue by simply correcting the errors on a case-by-case basis.
前面提到过，在重构引发了问题的情况下，不管问题是否被标出，您都可以一个一个地修正这些问题，以继续下去。
In that sense, refactoring insists on some less tangible, but decisive characteristics of software like design, simplicity, improved source code comprehension, readability and alike.
从这个意义上讲，重构坚持在一些不太明显，但却具有决定性作用的特征上作文章，例如设计、简单性，以及改善源代码的可读性，便于理解。
To some extent, the situations I describe in the refactoring guidelines are fairly vague notions of aesthetics.
从某种意义上说，我在重构准则中所给的那些条条框框也是一种模棱两可的美学原则。
Because it's often mentioned as one of the pillar techniques in agile methodologies, refactoring is interpreted as working only for teams adhering to these principles.
在敏捷方法学中，重构是被频繁提及的其中一项关键技术，因而通常的解释是，重构只有在遵循敏捷原则的团队中才能如鱼得水。
Because it's often mentioned as one of the pillar techniques in agile methodologies, refactoring is interpreted as working only for teams adhering to these principles.
在敏捷方法学中，重构是被频繁提及的其中一项关键技术，因而通常的解释是，重构只有在遵循敏捷原则的团队中才能如鱼得水。
应用推荐