To TDD or not to TDD: that is the question!
summary
Claims that TDD alone is not enough and must be paired with BDD acceptance tests, CI/CD, walking skeleton and automated deployment, collaborative pairing and simple design; concrete result: a two‑person craft team takes an untouched upstream backlog and gets the project green in months, backlog cleared in four months and funding restored. Cites a 349‑candidate stat: 100% claim TDD, 18% can’t write a test, 56% test after code, 24% test before, 2% follow classic TDD correctly. Practical lessons and tooling are prioritized.
AI-written summary · about
chapters (19)
- 0:00Intro
- 0:45A story of ordinary madness
- 2:05How it happen
- 3:50The challenge
- 5:55What is TDD
- 6:25History of TDD
- 8:17How many tests do we need
- 11:53TDD
- 15:37Classic TDD
- 19:02Acceptance Test
- 21:10The Ding Krueger Effect
- 22:40Ding Krueger Effect in our industry
- 23:48The enemy of knowledge
- 24:08The Danny Krueger effect
- 26:18Working Skeleton
- 27:43Simple Design
- 31:57Education
- 32:53Teamwork
- 38:00Collective mindset
related talks
16mNot Really a TDD Person? Come Discover Canon TDD
43mTDD — Things I Learned in the Last 12 Years
28mTDD: When the thrill has gone
13mTDD for Your Soul: Virtue and Web Development
58mTDD my recipe notebook
20mCraft, TDD, DDD... Should I Feel Guilty for Not Doing Them?
41mTDD For Your Soul: Virtue and Software Engineering
28mTDD for Absolute Beginners