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这里提出的要点是“停下来重构”从来不是擅长重构的团队应该选择的最佳策略。
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?
比尔：在《重构》这本书中，你写道：“通过写测试，我提高了作为一个程序员的工作效率。”能谈谈对鲁棒性、质量和可靠性的影响么？
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 : 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."
你在《重构》一书中写道：“编写能快速运行的软件的秘诀就在于先编写可性能调优的软件，然后对执行速度进行调优。”
应用推荐