> Software, as an industry, generally profits the most when it can identify an existing need that is currently solved without computers, and then make it 10x+ m

> Software, as an industry, generally profits the most when it can identify an existing need that is currently solved without computers, and then make it 10x+ more efficient by applying computers. >In this situation, the software doesn't need to be bug-free, it doesn't need to do everything, it just needs to work better than a human can. Well said, these statements underscores importance of FINDING the PROBLEMS/TASKS that are done by HUMANS/MANUAL that can be AUTOMATED with COMPUTERS that can yield 10X efficiency . Here are few gems from the original article https://blogs.msdn.microsoft.com/ericgu/2017/06/22/notdd/ https://blogs.msdn.microsoft.com/ericgu/2017/06/22/notdd/ The ability to write and refactor code to a state with low coupling, well-separated concerns > TDD Skills 1/ Design on the fly is a learned skill. If you don’t have the refactoring skills to drive it, it is possible that the design you reach through TDD is going to be worse than if you spent 15 minutes doing up-front design. 2/ I think that’s a good summary of why many people have said, “TDD doesn’t work”; if you don’t have a design with low-coupling, you will end up with a bunch of tests that are expensive to maintain and may not guard against regression very well.