Extensive discussions and lots of links: BDD / TDD criticized . I prefer something like https://medium.com/@ckoster22/invariant-driven-development-8231add95e33
I’m with Rich Hickey:
Each of us needs to assess how best to spend our time in order to maximize our results,
both in quantity and quality. If people think that spending fifty percent of their time writing
tests maximizes their results—okay for them. I’m sure that’s not true for me—I’d rather spend
that time thinking about my problem. I’m certain that, for me, this produces better solutions,
with fewer defects, than any other use of my time. A bad design with a complete test suite
is still a bad design.
Someone else (https://blogs.msdn.microsoft.com/ericgu/2017/06/22/notdd/)
Instead of spending time teaching people TDD, we should instead be spending time teaching
them more about design and especially more about refactoring, because that is the important
core skill. The ability to write and refactor code to a state with low coupling, well-separated
concerns, and great names will be applicable in all the codebases that we work in.
