Hacker News new | past | comments | ask | show | jobs | submit login

I recently started a new job and whenever I can I try to document the code I contribute with the "whys" instead of documenting self-explanatory parts. I've extended this to parts of the code that I now maintain but did not initially write as this helps me mentally map out the rationale.



Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: