I was chatting with a buddy of mine yesterday who recently has started a new job. His new company has built a new team to start a 'green field' project and they are currently in the 'debate' stage of planning. The team is currently trying to decide what tools, technology, methodology, etc to use.
One of the topics for discussion is whether they should take a TDD (or simply having unit tests) approach. He tells me that some on his team want this while others do not. It sounds to me from talking with him that there is not a lot of experience on his team in terms of writing unit tests. Of course when there is not a lot of experience writing tests, it is easy to be 'swayed' by the people that don't understand the value of witting tests. The main argument right now for NOT writing tests is.... wait for it.... wait for it.... 'Unit tests take too much time'. All I can say to that is WTF.
It has been my experience that writing unit tests do 'take time'. It is time you will be saving later. It is time you will be able to spend on other things in the future. I guess I just don't understand how educated developers can think this way.
I would love to speak with this team, it would be great to hear all the 'excuses' they come up with. Oh well. Maybe someone on the team can talk some sense into them. Or maybe after they deliver a shitty product with poor quality they will wish they had written tests.
Like the old saying says. You an lead a horse to water, but you cannot make it drink.
Till next time,
09-27-2007 7:38 AM