I'm at the point where I want to see docs on any non-private properties/fields, methods, parameters, classes, etc. I think there's nearly always value to be ad

I'm at the point where I want to see docs on any non-private properties/fields, methods, parameters, classes, etc. I think there's nearly always value to be added: * Explaining required fields, if null/blank/0 is allowed, where an ID comes from (db vs app-generated), if string values are formatted or require formatting (credit card, phone numbers), max length or other restrictions * If a class/method is thread-safe or not (when not obvious and misuse is dangerous), error conditions, timeouts. * Any external or indirect dependencies for use (config, packages, etc) * Links to other docs/wikis or tickets is hugely useful. When you're writing/working on the code you already know all this stuff, and it takes only a couple minutes to document. When someone else (or you, 6 months later) comes along to use or modify it, figuring everything out from scratch can take hours -- or worse, bug reports from QA or customers. Docs shave this down to seconds and directly avoid bugs. The other huge benefit I often experience is through trying to write docs for something I realize there's a better, more obvious name that makes it easier to use and requires less explanation (less docs). This happens on easily 5-10% of the things I write docs for.