I know that writing good documentation is hard, and that a lot of devs don't like to do it, but I completely agree with TFA. If the project isn't worth the tim

I know that writing good documentation is hard, and that a lot of devs don't like to do it, but I completely agree with TFA. If the project isn't worth the time to document properly, it's self-announcing that it isn't worth using that code. Why would anyone use throwaway code posted on GitHub? Even if it's been written by a "rock star," the risks are too high. The philosophy of OpenBSD is the correct one, I think: incorrect documentation is a bug and should be fixed with the same energy that is directed toward bugs in code. If it's only going to be used by you, great! Don't be offended if someone else looks at it and says, no thanks because of the lack of documentation.