Reliable Systems Make Failure Legible
A system is operable when it explains how it broke.
—Reliability isn’t the absence of failure. It is the ability to see failure, contain it, and recover without inventing a story under pressure.
Most systems become mysterious by accumulation. A retry conceals a timeout. A fallback conceals a retry storm. A dashboard averages away the one tenant having a terrible morning. Each local improvement makes the whole harder to explain.
The cure is rarely another abstraction. Keep state transitions explicit. Put ownership in the log. Prefer a failed request with a durable reason over a successful request nobody can account for.
That standard extends beyond software. Measurement changes the work whenever a proxy becomes a target. Operational metrics stay useful only while they preserve inconvenient detail.
At three in the morning, elegance is whatever leaves enough evidence to make the next decision.
Revised