Jim Coplien and Bob Martin Debate TDD
Channel:alexsmail · Length:20:58 · Published:2012-10-24 · Views:163518
Summary
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 HN recommends it
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, 2016
Testing, debugging & developer tools · Software practice, open source & careers
Subtitles (excerpt)
this is Floyd minescu and I'm here with Jim Copan and Bob Martin at the ja conference and here we have two very interesting Divergent uh opinions on uh what is the value of tdd so we'll open up the floor and uh let each one um have a couple minutes of say and then let's hear you guys talk about it okay so uh first thing I need to say is I'm sitting next to one of my heroes uh I read um Jim's book in 1991 92 uh changed the way I thought about soft sofware changed the way I thought about C++ in particular uh so it's a great honor for me to be here uh I think we have a disagreement I'm not sure possibly it may be a difference in persp perspective but my thesis is that it has become infeasible uh in light of what's happened over the last six years for a software developer to consider himself professional if he does not practice test development well maybe good because you did this at your keynote yesterday you said what you mean by test D and development so you know I I've adopted a very strong position against what the particularly the XP Community is calling test driven development and I've audited this you know versus a lot of tutorials at uh gosh at about four conferences at uril at urv at cuon here and one other in the past six months and they they give
On Hacker News
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 a… — lobut, 2016-11
I feel James Coplien's advice on the question is interesting: [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. — Ace17, 2017-10
James Coplien and Bob Martin have a debate of TDD and unit testing. There is a video of it on YouTube: [VIDEO] — lgunsch, 2014-03
Related videos
- RailsConf 2014 - All the Little Things by Sandi Metz · Confreaks · 38:47
- "Testing Distributed Systems w/ Deterministic Simulation" by Will Wilson · Strange Loop Conference · 40:20
- 🚀 TDD, Where Did It All Go Wrong (Ian Cooper) · DevTernity Conference · 1:03:55
- Bret Victor - Inventing on Principle · Rui Oliveira · 54:20
- Bret Victor The Future of Programming · Joey Reid · 32:55
- Solving Problems the Clojure Way - Rafal Dittwald · Clojure/north · 1:02:26
- Debugging Under Fire: Keep your Head when Systems have Lost their Mind • Bryan Cantrill • GOTO 2017 · GOTO Conferences · 52:34
- "Performance Matters" by Emery Berger · Strange Loop Conference · 42:15
- "Uncle" Bob Martin - "The Future of Programming" · Paul Stringer's Mobile Tech · 1:18:21
- A Tour of the Acme Editor · Russ Cox · 23:16
- Tech Talk: Linus Torvalds on git · Google · 1:10:15
- Tim Ewald - Clojure: Programming with Hand Tools · ClojureTV · 58:39
- "How NOT to Measure Latency" by Gil Tene · Strange Loop Conference · 42:59
- Ruby Conf 12 - Boundaries by Gary Bernhardt · Confreaks · 45:55
- Using Python to Code by Voice · Next Day Video · 28:17
- Transforming Code into Beautiful, Idiomatic Python · Next Day Video · 48:51