Keep things understandable
A reliable system starts with a few clear responsibilities. Prefer useful defaults, simple interfaces, and changes that are easy to explain.
Field Notes
Small observations on building software, understanding systems, and making room for curiosity.
Leave a trail
Write down the reason behind a decision. Good notes make it easier to return to an idea, question an assumption, and share what you learned.
Make time to explore
A small experiment can answer a question better than a long list of possibilities. Start with something observable, then follow the evidence.