I know that in my previous blog, that I mentioned I need to learn to get out of my own way and accept this test-driven development stuff. However, I believe I also mentioned that I feel it can sometimes be overkill. I still believe this. Not only is it easy to go overboard with testing but its also just as easy to go overboard with design.

I am discovering this on one of our current projects. I realize that we are using this small project to \"hone our skills\" but at what expense?

Does it make sense for us to disappoint a large customer who could bring us many more thousands of dollars of revenue by missing the timeline we quoted? There comes a time in my mind where you have to say \"enough is enough\" and get the freakin\' show on the road. Especially when you\'ve got a ton more projects working their way down the pipe to your desk.

We\'ve got a larger project ramping up in February and I fear that since I am sure we won\'t be done with the current one, that this larger project is going to start out much the same way as this one...all wrong. The only saving grace is that now, we\'re a bit more versed in how things should go and we can avoid some of the over-engineering pitfalls we ran into with our current project. That being said, I don\'t want to have to re-engineer this even bigger/more profitable project 15 different times along the way...and by re-engineer, I don\'t just mean re-factor, but strip the whole damn thing apart, and rebuild it...two weeks before deadline...