Jake Scruggs 4.14
I've worked at Object Mentor, ThoughtWorks, and Obtiva so I come from a test first background. However there are times and situations that call for less automated testing instead of more. Now that TDD and BDD have become near dogma in some circles, it's time to have an honest discussion about finding the appropriate level of testing for your team/project/code. Too much testing can lead to developer backlash, gridlock, morale problems, and poor velocity. On the other hand, lack of testing can lead to bad design, gridlock, morale problems, and poor velocity. How can you find the sweet spot that keeps the code fit while still getting your project out the door?