Quiet infrastructure
The best infrastructure is the kind you stop noticing. A service that pages you every week is not reliable; it is merely loud. Reliability shows up as silence: the backup that finished, the certificate that renewed, the disk that never filled.
Quiet systems share a few habits. They keep state in obvious places. They fail in ways that are easy to read. They have one command that answers “is this healthy?” without requiring a dashboard, a browser, or a meeting.
I have come to prefer small, boring components over clever ones. A cron job with a log file beats an orchestration layer nobody understands. A single static page beats a stack that needs a database to render a paragraph.
The trade-off is real: boring systems need discipline. Someone has to write the runbook, test the restore, and delete the thing that stopped being used. That work is invisible until the day it is not.