Combat Chaos-Driven Delivery By Thinking Like An OS
summary
Teams map OS scheduling to delivery: blend priority and round-robin policies, dedicate fixed capacity to work classes and reserve flex generalists, and break todos into small but valuable pieces (called fizz good). This cuts context‑switching costs, prevents job starvation, and accepts measurable trade‑offs: no one strategy is perfect, duration estimates remain unreliable, and success depends on enforcing chunked work and capacity slices.
AI-written summary · about
chapters (4)
related talks
56mDefending against CDD: Chaos-Driven Delivery
47mChaos Engineering Bottom Up
39mPractical Container Scheduling: Juggling Optimizations, Guarantees, and Trade-Offs at Netflix
38mScientific and Safe Chaos Engineering
10mCombine Support and DevOps work in an Agile team
20mChaos: breaking your systems to make them unbreakable
54mControlled Chaos: The Inevitable Marriage of DevOps & Security
48mHarnessing Chaos; the hidden ingredient behind building better systems
