Why This Stuff Is Hard
summary
Argues systems live in an Adaptive Universe: resources are finite and change never stops, so growth in capacity triggers the law of stretch systems and teams get pushed to full utilization. Uses a Netflix certificate outage (expired cert around midnight UTC) and inverted‑pendulum/Ashby analogies to show defensive fixes add complexity and require more variety to control failures. Calls out dark debt, partial views, and coordination/communication limits, and urges treating operational skill and surfacing work as first‑class strategies.
AI-written summary · about
chapters (37)
- 0:00Intro
- 0:41Or: You aren't actually doing it wrong
- 1:41The adaptive universe and its consequences
- 1:53Dr. David Woods
- 2:071. Resources are finite
- 3:11The law of stretched systems
- 3:56It's really, really hard to build up capacity
- 4:32Production pressure!
- 5:18Double bind
- 5:35Hard to find time to do reflection
- 6:03Planning vs reviewing
- 6:47Unceasing change
- 7:04Keep the system up in the face of change
- 7:24Code freezes
- 11:35What changed?
- 11:58The world changes around US
- 12:33We can't stop change
- 14:11We are prisoners of history
- 14:29II. The inevitability of complexity
- 14:54We eliminate failure modes by adding complexity
- 15:17We're in the control systems business
- 15:59Ashby's Law of Requisite
- 19:47Our understanding is always partial
- 20:03Can't see the interactions by looking at the components
- 20:28Dark debt
- 21:24Something somebody didn't know
- 21:53Getting the info into the heads of the people who need it
- 22:34The moment an action is performed, it ceases to exist.
- 23:23Work is invisible
- 24:18IV. Communication and coordination
- 24:47Incident response is a team sport
- 25:11Communication is hard
- 25:55Especially in a remote/ hybrid world
- 26:08Anyway... we're dead in the water until this figures itself out.
- 27:19Dr. Laura Maguire
- 27:431. We can't escape the adaptive universe
- 27:59We can't step outside our own local perspective
related talks
01h 04mPredictably Unpredictable
29mDeprecating Simplicity
41mYour Systems Aren't Stuck - Your Teams Are
49mSoftware Architecture, Team Topologies & Complexity Science
41m‘Failure’ as Success: The Mindset, the Methods, and the Landmines
14mAntifragility or taming the hydra
47mThe 7 Quests of Resilient Software Design
47mToo Much of a Good Thing: Finding the Balance
