Keynote
summary
Talk argues that software teams must embrace failure and learn from postmortems, not celebrate lucky successes. Concrete practices shown: continuous integration that build triggers Docker images and runs smoke tests deploy to meta.discourse.org before marking a build passing; alerts feeding into a Discourse category; external uptime checks (Pingdom/StatusCake); and open-source logging with logster /logs. Examples include Chernobyl and Theranos as cautionary postmortems, and a hosting service using these measures to detect queued background-job spikes and avoid repeat outages.
AI-written summary · about
chapters (6)
- 0:00Embracing failure
- 7:48Failure patterns
- 14:04Failure modes
- 20:01Future failures
- 28:46Fixing failures
- 30:53Q&A
related talks
39mKeynote Speakers
01h 04mInspirational stories
28mKeynote - Leading in Open Source, a Strategic Approach
25mLessons Learned from Cultivating Open Source Projects and Communities
05mIgnite: Learning to Share
09mKeynote: What Winning Open Source Looks Like
53mKeynote - Embracing Openness as a Competitive Advantage
15mLessons Learned from Cultivating Open Source Projects and Communities
