Ramblings of an aging IT geek
← Ramblings of an aging IT geek
personal

the book that taught me to leave slack in the system

A short note on a systems book whose idea of buffers and slack quietly rewired how I think about capacity and resilience.

A coffee cup beside a stack of books

I read a lot of books that promise to change how I think and deliver a clever phrase and nothing else. This one actually stuck, and the idea that stuck was slack.

The argument is that a system run at one hundred percent utilisation has no room to absorb anything. No spare capacity, no buffer, nothing between a small disturbance and a cascade. We are taught to see slack as waste, the idle worker, the half-empty queue, the headroom on the box. The book reframes it as the thing that lets a system bend instead of break.

Once you have that, you see it everywhere. The team running flat out with no recovery time that falls apart the moment someone is ill. The disk at ninety-five percent that turns a routine log spike into an outage. The motorway that runs beautifully until it hits capacity and then jams for an hour over nothing. Same shape, every time.

It changed how I size things. I now leave headroom on purpose and defend it when someone wants to optimise it away, because the slack is not waste, it is the part that keeps the rest standing up when something goes wrong. A short book, and that one idea has paid for it many times over.