TDD for Your Soul: Virtue and Web Development
summary
Applies the TDD cycle as a literal method for character change, mapping red–green–refactor onto personal habits and the four classical virtues — self-control courage justice wisdom — as concrete targets. Argues shame blocks self-testing, shows pair programming as a vulnerability that requires courage, and describes a built habit: a half-hour time limit on being stuck then asking for help, which succeeds and later gets refactored away into steadier behavior.
AI-written summary · about
chapters (30)
- 0:00Introduction
- 1:28What is TDD
- 3:07Writing tests
- 4:28Selfdirected technology
- 5:25Simple things in life
- 6:54Virtues
- 7:04Selfcontrol
- 7:40Developers condition oscillation
- 8:06Lack of selfcontrol
- 8:45Soft control
- 9:27Self control
- 10:23Courage
- 11:25Richard Feynman
- 12:00Pair Programming
- 13:07Ruby
- 13:39The Solution
- 15:17Justice
- 16:33Unjust Code
- 19:41Obligations
- 20:44Wisdom
- 20:59Design Patterns
- 22:13Confucius Quote
- 24:06Recap
- 24:33Test
- 27:10Shame
- 27:41Am I good enough
- 27:54You have failures and weaknesses
- 28:16A different way to look at failures
- 28:44The Shepherd Book
- 30:53The Blues
related talks
13mTDD for Your Soul: Virtue and Web Development
41mTDD For Your Soul: Virtue and Software Engineering
43mTDD For Your Soul: Virtue Through Software Development
28mTDD for Absolute Beginners
43mTDD — Things I Learned in the Last 12 Years
20mCraft, TDD, DDD... Should I Feel Guilty for Not Doing Them?
58mTDD my recipe notebook
42mTo TDD or not to TDD: that is the question!