Security Chaos Engineering

I’ll admit: I groaned when I saw the runtime. Eighteen hours on security engineering? But *Security Chaos Engineering* earned every minute—mostly because it’s *not* a traditional security book. Kelly Shortridge’s approach is radical in the best way: she argues that resilience isn’t about preventing failures (impossible) but *mastering* them. The audiobook’s structure reflects this—early chapters dismantle sacred cows (like "defense in depth" as a panacea) before rebuilding a framework that treats outages as data. Narrator April Doty nails the tone: authoritative but never condescending, with a knack for making jargon like "steady-state hypothesis" sound like common sense. Her delivery during the "GameDay" exercises—where teams intentionally crash systems—is particularly vivid, almost making you feel the war-room tension. That said, this isn’t a casual listen. The depth is both its strength and its Achilles’ heel. The dive into *cognitive load* during incidents (Chapter 7) is brilliant but dense; I rewound three times to grasp the interplay between alert fatigue and mean time to repair (MTTR). And while the real-world examples (e.g., how Slack’s chaos experiments uncovered latent dependencies) are gold, the audiobook occasionally bogs down in repetitive emphasis on "shift left" principles. Production-wise, the audio is clean, though Doty’s cadence can feel rushed during code snippets—a minor gripe, but noticeable if you’re following along with the PDF companion. Still, for engineers weary of security theater, this is the audiobook equivalent of a red pill. Just budget time for note-taking—you’ll want to pause and debate its ideas with your team.