Giving up on test-first development
From the article: <i>Because you want to ensure that you always pass the majority of tests, you tend to think about this when you change and extend the program. You therefore are more reluctant to make large-scale changes that will lead to the failure of lots of tests. Psychologically, you become conservative to avoid breaking lots of tests.</i><p>Interesting. I&#x27;ve often found that the <i>lack</i> of tests leaves me absolutely terrified of making changes to large Ruby and JavaScript applications. I mean, if a test breaks, then I get a nice message right on the spot. But if I don&#x27;t have tests, then the application itself breaks, and I may not find out until it&#x27;s been put into production on a high-volume site or shipped to users.<p>Once an application crosses, say, 25,000 lines of code, it&#x27;s hard to keep an entire program in my head, especially in a dynamic language and with multiple authors working on the code base. Under these conditions, large scale refactorings or framework upgrades can cause massive test failures, but the only alternative is to cause massive, unknown breakage.