4 ms·
If there are some things that are really useful, you can quickly call them out in the readme, but even if you don't people will browse and figure out how to use
by Jach 9y ago
If there are some things that are really useful, you can quickly call them out in the readme, but even if you don't people will browse and figure out how to use them anyway if they want to. There are plenty of projects with poor or entirely absent documentation that still see use.
In some ways I could see how going through the effort of attempting to have documentation might just make things worse because then people might have an expectation that you're going to keep working on it or respond to filed issues. Anyway I thought the more common excuses were "eh, this isn't that useful, no one will look at it let alone use it", or "I'd have to go through everything and make sure I didn't leave my password in a comment or something stupid", or maybe the most common "there's a lot of hacky code, I don't want to have random people / a potential future employer see this and think I suck at coding..."