The one that got me every single time is that 'it won't work in the real
world'.
That was before a management imposed 'embrace tdd' phase. Now I hear
* I spend more time writing/fixing my tests than my code.
* Writing tests for this code is impossible.. and I don't have the
authority/time to change the design
* Writing tests is boring, my code works.
* Maybe the test is wrong.. the best one I heard was 'I don't trust
automation'
All deeper systemic issues than deficiencies of TDD. Convincing everyone is
tiring.. There are no winners in verbal arguments.. I feel some teams just
aren't ready for TDD.
Waiting for people to turn around is usually slow enough as to warrant a
management push in most BigCos...but that leads to what I call 'compliance
TDD' or 'just enough to let me check in TDD' leading to tests that resist
change (instead of enabling them).
Maybe that's a source of the 'no creativity in programming anymore' - I
guess some people miss the speed at which they could write code that mostly
works, only they and the compiler could read and chuck it over the wall to
the testers. TDD absolutely chokes that one.
</Rant>
