How TDD Missed the Point: Introducing EDD
summary
Argues that experiment driven development actually makes business hypotheses testable by shipping minimal features and running AB tests, shows concrete comparisons with Google website Optimizer and lighter Ruby tools like bingo and vanity, reports conversion numbers (example 15 vs 12 not yet statistically significant), admits metr i project is half baked, stresses one‑line experiment hooks, framework speed and rollback concerns, and calls for reusable Ruby frameworks so experiments are cheap enough to be routine.
AI-written summary · about
chapters (15)
- 0:00Start
- 6:44TDD as SOP
- 9:24Problems in TDD Land
- 11:08Project FAIL
- 14:00Creating Waste
- 18:42But first: MVP
- 19:44MVP → EDD
- 23:37EDD Frameworks
- 27:53Google Website Optimizer
- 28:49Create experiment on GWO site • Add control script • Add tracking script(s)
- 29:367-Minute Abs
- 33:04Experimentation Culture
- 33:56GOAL: Rigorous Experiments becomes as common as TDD
- 34:21One More Thing...
- 37:33Questions & Feedback
