Strategic TDD
summary
Argues that TDD is a goal–outcome–feedback loop and not just writing tests first, showing concrete uses: use input mapping to pick the next feature, measure impacts with metrics, create a skeleton architecture and validate non‑functional needs with automated fitness functions, and run quick MVP/user‑research loops for strategic choices. Gives a mobile‑ads example, describes building small outcomes (user stories, skeletons, MVPs) and iterating until metrics or user feedback confirm or refute assumptions.
AI-written summary · about
chapters (14)
- 0:00Strategic Test-driven Development
- 3:39How can Development be driven by Tests?
- 4:25What is the next test to write?
- 6:09learn the most about the problem
- 7:12Another Big Decision is hidden in plain sight
- 7:36Write just the code that yo need to pass the new test
- 8:45TDD is a goal oriented decision-making tool based on tests
- 9:34What is a Test?
- 12:56TDD is a goal oriented decision-making tool based on feedbacks
- 25:43What is the goal of Softwa Architecture?
- 28:27What are the feedback fo Software Architecture?
- 29:30What is a small outcome for Software Architecture
- 29:40A Walking Skeleton is a tiny implementation of the system that performs a small end-to-end function. It need not use the final architecture, but it should link together the main architectural components. The architecture and the functionality con then evolve in parallel.
- 32:23What kind of feedback do need?
