Working Software Is the Primary Measure of Progress
summary
Examines why working, well-tested software is the principal measure of progress by focusing on user-facing consequences of bugs in critical domains (aircraft, medical devices, banking). Presents concrete examples and advocates for practices like automated tests, Test-Driven Development, and clean code to ensure reliable, high-quality results.
AI-written summary · about
chapters (7)
- 0:00Introduction
- 7:31Poor software costs
- 10:04Quality software delivery
- 15:02Test pyramid
- 19:18Agile vs waterfall
- 21:46TDD practical example
- 25:59Summary and Q&A
related talks
42mwhy software development is an engineering discipline
41mComputer Science, Software Engineering, and the Scientific Method
45mTaking Back "Software Engineering"
36mHow Good Is Your Software Product? (Evolving "Quality"Throughout The SDLC)
40mBuild Better Software
38mIntro to Empirical Software Engineering: What We Know We Don't Know
17mThe Way of The Software Craftsman
24mThe more we test, the worse?
