This post of Jesse Liberty is the first of two parts on
Test Driven Development.
It seems reasonable to many developers to create unit tests for
their code; but the presumed high cost of doing so implies for waiting
for a project that is not in “crunch mode.” Most developers will be
waiting a long, long, long time.
Experience indicates that TDD actually saves time – you spend less time debugging and more time coding. Unfortunately, that sounds like “a good theory” and we all know that in theory, theory and practice are the same, but in practice, they never are.