Prefer boring recovery procedures
A recovery path should use fewer moving parts than the system it restores. Keep the instructions short, test them periodically, and store a copy away from the primary machine.
FIELD NOTES
Small, practical notes for building dependable systems.
Short references on software maintenance, networking fundamentals, and operational habits.
Measure before changing network settings
Record latency, loss, DNS behavior, and the exact route before tuning. A small baseline makes it easier to distinguish an improvement from a temporary change in conditions.
Configuration is part of the product
Version configuration alongside the software, validate it before activation, and keep the last known-good release available for rollback.