18 Dec '12, 8am

how to never refactor with broken tests

The third step of “red, green, refactor” is an important one. The feature is not done if you skip this step. The whole point of “green” is to get to “refactor”. But it can be easy to lose sight while doing this step; it’s easy to start re-implementing irrelevant parts of the system. When going down this path it’s good to consider another option: back out the “green”—go back to the failing test—and make a change to the existing system in preparation for the implementation.

Full article: http://robots.thoughtbot.com/post/38216457455/refactor-in...

Tweets

X-47B Unmanned Combat Air System Completes Firs...

navy.mil 18 Dec '12, 7pm

USS HARRY S. TRUMAN, At Sea (NNS) -- The X-47B Unmanned Combat Air System (UCAS) demonstrator completed its first at-sea t...