Software Quality Is Not Just Code and Tests
summary
The talk argues that software quality failures usually stem from people and communication, not technologies, frameworks, or tools. It identifies recurring human problems—not admitting mistakes, not asking for help, and not sharing feedback—and describes mechanisms that fail and several high-profile incidents caused by poor communication.
AI-written summary · about
chapters (7)
- 0:00Introduction
- 1:02Who we build software for
- 2:48Enemies of software quality
- 5:14Lessons from production errors
- 8:49Handling failures
- 9:31Three steps to better quality
- 10:56Summary and Q&A
related talks
52mSoftware Quality === Health
26mSoftware Quality in Software Houses? Yes! (SQISHY)
48m...because quality starts in your head
23mCommunication is just as important as Code
05m“Quality is a Team Responsibility”
43mWhat Comes After SOLID? Seeking Holistic Software Quality
13mCommitting to quality
46mProject Culture and Team Responsibility for Quality