Comments by "Dean Schulze" (@deanschulze3129) on "Why Hasn't TDD Taken Over The World?" video.

There is no evidence that TDD works better than anything else. He won't admit this, however. Where are the metrics to back up his claims? After 25 years there should be metrics or at least examples of TDDs superiority. He claims that TDD is a design strategy that results in code that is more testable. But he doesn't even mention other aspects of design: cohesion coupling scalability maintainability intuitive design and APIs It's a mistake to ignore these and just focus on testability, which is what TDD advocates do.
2
@QmunkE - Software iterations are a good way to resolve these kinds of ambiguities. Make your best estimate of what the end users want and implement. Show it to them and get feedback. Repeat. TDD would definitely show you down in this case. Very little of your original code will survive so there's no reason to test it thoroughly at first.
2
@JordanEdmundsEECS - I appreciate your insights onto the difficulties of testing UIs. But have you ever written a backend that was a distributed system? Unit tests are worthless on distributed systems. You need to test the entire system as it will be deployed in production.
1
Or how about if TDD advocates started explaining TDD properly instead of just complaining that all explanations are wrong. Unit tests are worthless in a distributed system. You need to test the entire system deployed the way it will be deployed in production. I've yet to hear a TDD advocate explain how to TDD a distributed system. They can't seem to get past unit testing.
1