I guess I just need to accept it.... good documentation will never happen...

http://qr.ae/TUGCIj

The problem with good documentation is that everyone has a different idea of what it is. For some, it's a step by step instruction of how to do X, even if it takes 30 pages. For others, it's "implement factory that creates objects conforming to this interface" and off they go.

One thing I think all can agree is, "code snippets are amazing" (and consequently, "not working code snippets are infuriating as fuck").

@piehole well when I look at a class or a function (JavaScript). I'm usually going wtf is this supposed to do. What goes in, out, and why?

I do not want to have to debug in production to find out. (Some Java code can only be run on remote servers because they use 10GB+ RAM...)

And for reusability... Basically someone created a brick...

Maybe that's the standard I should push. If you want to say your code is reusable, at least document your shit.