Jim Coplien and Bob Martin debate test-driven development and unit testing in an InfoQ video that grew out of a JAOO 2007 dispute. They also touch on design and architecture.
Why Hacker News points people here: HN points to it as a fun, substantive exchange between two experienced practitioners on TDD's value.
“this was a fun discussion about TDD between two professionals”HN comment, 2016
“this was a fun discussion about TDD between two professionals”
Fun discussion on TDD between two professionals.
Full comment
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.
Cites itlgunschMar 2014
“James Coplien and Bob Martin have a debate of TDD and unit testing.”
Debate between Coplien and Martin on TDD and unit testing.
Full comment
James Coplien and Bob Martin have a debate of TDD and unit testing. There is a video of it on YouTube: this video
Cites itAce17Oct 2017
“I feel James Coplien's advice on the question is interesting”
Coplien's advice on short-sighted design versus refactoring effort.
Full comment
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.
