What if your survival depended on…
summary
Using a post-apocalyptic survivor metaphor, the talk maps six survival rules to software testing practices: get external reviews (code review), isolate units early (unit testing/mocks), use disciplined exploration to improve architecture (systematic testing and refactoring), run mutation testing to ensure tests catch regressions, prioritize testing efforts strategically, and enforce automated policies that remove code failing tests (CI/CD gates). It ties these concrete tools and methods to the goal of keeping code reliable so it remains usable.
AI-written summary · about
chapters (9)
- 0:00Code quality introduction
- 3:02Rule 1: Never work alone
- 8:23Rule 2: No blind trust
- 12:58Rule 3: Revisit decisions
- 17:31Survival practices summary
- 18:35Rule 4: Don't trust the dead
- 27:01Rule 5: Avoid reckless risks
- 35:44Rule 6: Be strategic
- 38:34Conclusion & Q&A
related talks
47mIs Survival of the Fittest Only for the Fastest?
23mChaos Survival Guide: Start testing in any conditions
42mUse testing to Develop Better Software Faster
01h 04mBuilding on Success, Beyond the Obvious
48mA Reflection on Software Testing
49mThe Secret to Successful Testing
24mDemystifying Code Through Testing
58mTesting Strategy - New Model, Better Outcomes