- Interfaces suddenly seem like a good idea.
- You stop using singletons and static methods.
- Private makes less sense than it used to.
- You pass dependencies in the constructor (the so called 'fat constructor')
- Smaller methods are the norm.
- You read tests before the code; it better explains the intention.
- Usability trumps cleverness.
- Premature performance optimisation is bad (YAGNI)...
- ... but test performance is crucial.
- Dependency is bad; you avoid 'God classes' and 'global hubs'.
- 'Clever' is dead. 'Clever' is hard to refactor. 'Clever' is hard to isolate, hard to internalize, hard to phrase in tests.
- Your IDE is only good if it allows you to do quick write/build/test cycles.
Thursday, August 30, 2007
I've just stumbled upon a fantastic blog post Testing Will Challenge Your Conventions, by Tim Ottinger. In it he lists a number of ways that doing TDD fundamentally changes the way you code:
Posted by Mike Hadlow at 1:11 am