Technical notes age better when they preserve decisions, constraints, and tradeoffs instead of only listing commands. Commands can drift. The reason a team chose one direction over another tends to remain useful longer.
A useful shape
Start with the problem. Name the constraint. Show the tradeoff. Then include the implementation detail that helped. This order makes the note readable even after the exact library or framework version changes.
123
!@#
Keep the note small
The best personal knowledge base is not a second job. A note that captures one decision clearly is more useful than a large document that tries to remember everything.