Make the path easy to follow

A useful system has a clear purpose and a small number of moving parts. Start with the simplest arrangement that meets the need. Add complexity only when an observed problem calls for it.

Leave a record that helps tomorrow

Record what changed, why it changed, and how the result was checked. Keep observations separate from assumptions. A short, accurate note is often more valuable than a long explanation written from memory.

Small acts of maintenance

Keep a recoverable copy before making changes. Check that the thing people actually use still works. Return occasionally to remove workarounds that no longer serve a purpose.