Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

The challenge I have these days is deciding what belongs in code and what goes into design documentation and technical manuals.

I generally find that comments in code should explain why the code is doing non-obvious things. “This gets memoized because it’s actually important to maintain referential identity for reason X.”



The problem is, a year later the obvious things are not obvious anymore :D




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

Search: