Writing documentation feels like a chore because developers frame it as communication for others. Reframing it as notes to your future self makes it more natural and useful. Key areas to document as you go include technical decisions (focusing on what would invalidate them rather than defending them), manual tasks (step-by-step so you can follow without thinking), and production support fixes. The post also emphasizes actually using your documentation to validate it, and treating good docs as a way to reduce the mental load of project ownership and enable clean handoffs.
Table of contents
Documenting as you goUse your documentationReduce the mental load of project ownership119 Impressions1 Comment