Notes
Short entries about maintaining small systems with fewer surprises.
A useful backup is understandable and testable. Saving configuration, a short inventory, and the data that cannot be recreated often provides more confidence than copying an entire machine without knowing what matters inside it.
Names should describe purpose before implementation. A clear label continues to help after tools, addresses, and providers change. Clever abbreviations usually become a tax paid by whoever returns to the system later.
A running process does not prove that a service is usable. Good checks follow the same route as a real request: resolution, connection, negotiation, application response, and the return path.