Comedy Talk
summary
Material asserts that bugs scale with code and even offers a mock formula (lines × files × statements × conditions summed to infinity) that only yields zero bugs when there is no code. Slides show a dataset where deleting a large chunk of code paradoxically spikes defects, recount a decision to fire the engineer and restore the code, and promote tactics like cutting network access and removing developers entirely—replacing them with managers and rebranding release 2.3 as 3.0 as a way to “fix” quality (remove the internet).
AI-written summary · about
chapters (20)
- 0:00Introduction
- 1:29Talk title and joke
- 2:53Speaker
- 5:21Certificate of quality
- 6:29Defining quality
- 8:14Quality metrics
- 9:17Equivalence theorem of code
- 10:39Where bugs live
- 11:22Who writes the bugs
- 12:03Code-bug correlation
- 13:27Believable solutions
- 14:36Code review process
- 15:58Product management supervision
- 16:43Work hours and bugs
- 17:03Making up the data
- 17:45Reorganizing the org
- 19:07Role of managers
- 20:10Corporate realization
- 20:52No engineers no bugs
- 21:48Q&A