Document Everything

Future me (and future teammates) will thank present me. If I can't explain it clearly, I probably don't understand it well enough yet.

What This Means in Practice

Every project I work on gets documentation — not because it's required, but because writing things down forces clarity. When I document a system, I often discover gaps in my own understanding.

Good documentation isn't just for others. It's for the version of me who comes back to this code in six months and has no idea what I was thinking.

Why It Matters

• Writing forces you to truly understand what you've built
• Makes onboarding teammates infinitely easier
• Reduces "bus factor" — the project survives without you
• Saves debugging time when you forget why you did something