Your Software is Mission Critical
summary
Argues that everyday systems must use mission‑critical practices: static analysis (PHPStan, Psalm) reads the PHP abstract syntax tree, continuous testing (GitHub Actions, CircleCI) runs suites on every change, and value objects plus domain design prevent real‑world errors. Gives concrete harms — autopilot failures and a customer losing a mortgage because billing was tied to a property not a person — and shows tools and tests that reduce those failures rather than vague design platitudes.
AI-written summary · about
chapters (7)
- 0:00The impact of software
- 3:11Mission-critical failures
- 8:46Implementing robust testing
- 13:46Static analysis and safety
- 16:48Design and domain modeling
- 23:51Humans, diversity, and teams
- 28:32Humility and lessons learned
related talks
40mBullet-proof projects
41mLiving the Best Life on a Legacy Project
25mTypes & static analysis are good in PHP
50mPractical Advanced Static Analysis
45mTesting Strategy with the Help of a Static Analyzer
50mTools of the Trade
55mSquash Bugs with Static Analysis
44mStatic analysis as an additional barrier against bugs
