什么时候要重构呢？
Let's refactor this code a bit.
让我们稍微对该段代码进行重构。
Stop feature development and refactor.
停止开发特性，进行重构。
什么时候进行重构呢？
They refactor code to make it more testable.
他们重构代码，让代码更加易于测试。
Unit tests make your code safe to refactor.
单元测试使您能够安全地重构代码。
However, I prefer to refactor existing code instead.
但是我更愿意重构已有的代码。
With closures, you can also refactor from the outside in.
有了闭包，您也可以从外到里进行重构。
With this step, you refactor the code that causes the problem.
在这一步中，您将重构导致问题的代码。
The question then becomes How do I know when I should refactor?
那么问题就变成了“我怎么才能知道什么时候该进行重构呢？”
You can refactor the code to make the stylesheet much simpler.
您可以重构代码以简化样式表。
In this case, refactor the code to remove the dependency.
在这种情况下，请重构代码以移除依赖关系。
In part 3, you'll refactor the rock star application built in this part.
在第3部分中，您将重构本文所建立的摇滚巨星应用程序。
You should refactor the code to separate the various application layers.
应当重构代码以分离各个应用层。
A laudable goal for any project is a code base that is easy to refactor.
对任何项目来说，值得称赞的一点就是拥有可以轻松进行重构的代码库。
Before you build that stylesheet, let's look at how to refactor the code.
在构建该样式表之前，我们来查看一下如何重构代码。
The key concept is a development workflow called red-green-refactor.
关键概念是一种叫“红-绿-重构”的开发工作流。
To make this program double-buffered, you need to refactor the code slightly.
为了让这个程序进行双缓冲，需要对代码略加重构。
Refactor Database Code and Data.
重构资料库程序码和资料。
重构代码。
Refactor your original code to look like this.
重构您的原始代码，使其看起来如下所示。
Refactor your original code to look like this.
重构您的原始代码，使其看起来如下所示。
应用推荐