Today I was working with a new library. I wrote a 30 line sample program just to make sure I understood the library semantics, and that it would at least do what I thought in a situation similar to the actual code base.
I called over another developer to sanity check my thinking, and he spent 10 minutes going on how I should have just written tests for it in our codebase instead.
He would not take any of these as valid discussion points:
* I spent nearly 7 minutes on my sample code, writing tests including the appropriate mocks for our codebase would have taken 70.
* I didn't even know we would be moving forward with that library, why start integrating it into our infrastructure?
* I'll write tests of our code using the library, when we figure out what the thing we're building actually does.
* I would have to write that same sample program before I can even write tests, to know how to use the library.
I do know now not to include that guy in my thinking process ever again, if tests aren't perfect, I will lose any time including someone might gain by dealing with his TDD is my holy saviour rants about how I should learn.
Worst part: this guy takes days to write "tested" code that still doesn't actually do what it is supposed to.