Making It Count: Quality is NOT an Option
summary
Lessons from NASA projects show quality means concrete practices not buzzwords: independent verification IV&V catches system-level safety issues exposed by Challenger, Cassini and Mars rovers; common bugs include a race that transfers empty files, an SR latch style flag that breaks upgrades, and async retries that deadlock two sides. Invest in executable specs like TDD and BDD, property based tests, CI/CD and model checking (TLA+) for measurable ROI, and cultivate developer pride, ownership and accountability as the primary driver of reliable systems.
AI-written summary · about
chapters (8)
- 0:00Start
- 8:46Software Quality
- 10:19"Non"-Functional Requirements?
- 11:29What could possibly go wrong?
- 16:38Case Studies
- 17:04100% code coverage
- 17:57Error Handling (is hard)
- 19:08It was Java
related talks
01h 07mBuilt In Quality Reach Beyond the Team
28mWhy Software Quality Is the Key to Scaling AI Development
37mBuilding Quality with Foundations of Mud
53mKeynote:7 Important Requirements for Any Successful Project
29mKeynote: BDD - Bias driven development
25mBuilding Castles, Not Sandcastles: Strategies for Software Architecture Success
42mOut of the Legacy Trap: From Technical Debt to Higher Quality
40mQuality versus Agility: a conflict of interest?