1·The question then becomes How do I know when I should refactor?
那么问题就变成了“我怎么才能知道什么时候该进行重构呢？”
2·Any new code should not be developed depending on these options being set, and you should look for ways to refactor your existing code away from using them if possible.
不应当基于被设置的这些选项来开发任何新代码，而且可能的话，您应当寻求方法来重构您的现有代码，避免使用它们。
3·Do you refactor that test immediately, mark it as ignored until you finish the current story and cycle back to the ignored one?
你是否会立刻重构那个测试，还是把它标记为“忽略”，等你完成当前的故事再回过头去处理那个被忽略的测试？
4·An important thing to note here is that you should either design and write new code, or refactor existing code.
这里要注意的重要一点是，您应该要么设计并编写新代码，要么重构现有的代码。
5·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.
因此，如果这是对的——我也非常确信它的正确性，那么对于已经精通重构的团队来说，“停下来重构”策略从来就不是最佳策略。