spaceblog

There's an important advantage to Test Driven Development that I don't think was covered on list or by Rob at his talk.

By having a test suite, you can code after a heavy liquid lunch and be sure that you're not decreasing the quality of existing code. It makes it easier to focus on a specific task and write code to solve that problem. Having something do all the work for you when testing is a massive bonus, because obviulsy the side-effects of a pub lunch are that you are easily distracted and lack the willingness to focus on the task at hand. Test suites lower the barrier of entry to getting work done.

Who'da thought that best practices would also be best for drinking practice?