Jim Coplien and Bob Martin Debate TDD

I feel James Coplien's advice on the question is interesting: ▶ this video TLDW: "refactoring your way out" from a simple but too short-sighted design might take a ridiculous amount of work, compared what would have been necessary if you knew what a "correct" design for this problem was.

Yeah, I agree. TDD is also, you cannot write a single line of code without writing a failing unit test though. Well, I'm not a fan of that either. I mean, sometimes I like writing an acceptance test to begin with and work inwards. People sometimes interchangeably use "TDD" for "testing". Also, just because you do TDD, doesn't mean your code can be great, I've seen people assert pointless things and the unit has gotten so small that people now define them as methods in classes. Which I also think can lead to some crazy maintenance suite of tests. If you're interested, this was a fun discussion about TDD between two professionals: ▶ this video Jim Coplien and Uncle Bob.

James Coplien and Bob Martin have a debate of TDD and unit testing. There is a video of it on YouTube: ▶ this video