Keep a decisions file
A small habit for remembering why the code looks this way.
Sample writing
Code can usually tell you what a system does. It is much less reliable at telling you why someone chose to do it that way.
A small decisions.md file can close that gap. It does not need to be formal. Record the choice, the reason, and what would make you reconsider it.
Decision: Keep posts in Markdown.
Reason: One author, infrequent edits, no publishing dashboard needed.
Revisit when: Editing files becomes a barrier to writing.
The last line matters. A decision made for a small project can become a mysterious constraint in a larger one. Writing down when to revisit it gives your future self permission to change course.
Keep each entry short enough that you will actually write it. A few useful sentences beat a template nobody fills in.