The Redundancy

The engineer's instinct is to eliminate redundancy. Every duplicate path is waste — an extra wire, a backup pump, an unused capacity. The clean system has no fat, no slack, nothing that doesn't earn its keep. Lean and taut, running at the edge of capacity, every component doing exactly one thing.

But the engineer's instinct misses something. When the lightning strikes or the pipe corrodes or the operator makes the 3 AM mistake, the lean system has nowhere to go. It was already running at the boundary. There is no margin for error, no escape hatch, no second path. Each component a single point of failure wearing the mask of efficiency.

The redundant system, by contrast, has options. Not efficient options — that's precisely the point. When the primary fails, the secondary kicks in. Not as good, maybe. Not designed for continuous use. But present. Available. The system limps along rather than collapsing entirely. What looked like waste becomes survival.

Nature knows this better than engineers. The genetic code is famously redundant — multiple codons mapping to the same amino acid, backup pathways for protein synthesis, entire gene families that can substitute for each other. The body doesn't ask whether this maximizes efficiency. It asks whether it survives. Efficiency is a luxury of stable environments; redundancy is a necessity of uncertain ones.

There is a deeper truth here, about what it means to be robust rather than optimal. The redundant system carries its past inside it — every backup pathway a lesson learned from some previous failure, some ancestor's catastrophe encoded into the architecture. The extra capacity isn't waste. It's memory. It's the system's record of what went wrong before and might go wrong again.

And the lean system? It has no such memory. Each optimization erases the reason for the previous state. It becomes a creature of its current environment, perfectly tuned to present conditions and helpless when those conditions change. The pursuit of efficiency is a kind of forgetting.

This is the paradox: redundancy looks like carrying more than you need, but it's actually carrying exactly what you need — just distributed across time rather than space. The extra capacity sits unused until the moment it becomes essential. You could say it's always in use, always doing the work of waiting. The lean system, meanwhile, has outsourced its margin to some external rescuer that may not arrive.