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

The greatest difficulty I run into as an indy developer is lack of internal documentation.

I often write something and don't look at it for a long time thereafter; In the intervening period, I forget some important aspect of how this code works. Or I inherit a piece of code from another developer, and I have no idea why it was implemented the way it was.

I would love it if developers wrote a line of comment or two per function, just laying out what's happening and why the code was written that way.




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

Search: