Defence at the Boundary of Acceptable Performance
summary
Applies Jens Rasmussen’s Dynamic Safety Model to tech companies and claims the economic boundary is the strongest and the performance boundary the weakest, driving operations to the edge; cites layoffs, budget cuts, burnout and even “~10 SE‑0s in two weeks” as triggers. Recommends concrete experiments: chaos engineering techniques like load‑shifting, synthetic tests, injecting latency with Linux traffic control and terminating servers to measure the true error margin and then reinforce it so systems and teams regain buffer.
AI-written summary · about
chapters (9)
- 0:00Introduction
- 1:06Model purpose and relevance
- 6:23Three performance boundaries
- 7:28Economic boundary forces
- 12:23Workload and human performance
- 16:13Performance boundary defense
- 21:07Strengthening with local knowledge
- 26:50Key lessons for systems
- 30:03Emotional impacts and conclusion
related talks
48mPerformance culture through the looking-glass
41mA Defence of Technical Excellence
19mDevOps, but you don't need to be an enterprise
29mEconomies of Speed
50mCreating Performance Impact in a Changing Tech Landscape
43mBetter Software Development Systems through Stress
27mMind the gap: Navigating the staff+ performance cliff
36mMove fast Build things… Safely!