Take the 2-minute tour ×  The TDD cycle is test, code, refactor,
(repeat) and then ship. TDD implies development that is driven
by testing, specifically that means understanding requirements
and then writing tests first before developing or writing code.
My natural inclination is a philosophical bias in favor of TDD;
I would like to be convinced that there are other approaches
that now work well or even better than TDD so I have asked this
question. There are other questions that suggest TDD is
expensive, tough to implement, presents challenges ... agreed,
but what are good alternatives?  What are good examples of
perfectly acceptable approaches that do not use/need/require
test driven development?  I can think of plenty approaches that
are not TDD but could be a lot more trouble than what they are
worth ... it's not moral judgement, it's just that they are cost
more than they are worth ... the following are simply examples
of things that might be ok as learning exercises, but approaches
I'd find to be NOT a