> Getting stuff out there to be noticed is difficult, a lot of work, and going the the last 10% does not guarantee any more success. If your benchmark is numbe

> Getting stuff out there to be noticed is difficult, a lot of work, and going the the last 10% does not guarantee any more success. If your benchmark is number of stars on Github, then yes, things might get depressing when "JS toy framework number 45" easily gathers hundreds of stars. But, personally, I have half a dozen reasonably polished projects on less trendy topics. While not huge, I know they were useful to other people. Some are packaged in linux distributions, others I've got requests for improvements, or were used as cross-reference for concurrent implementations, or were forked and continued a life of their own. It's not huge, but by spending ~30% more time on things like documentation, tests, proper build system, a post here or on Reddit, I've enabled these projects to be more than an unapproachable pile of code. And if it saves even one person the effort of implementing these projects, that's a result well worth the ~30% more effort for polishing the project in my book. Lastly, users/interested people are often not developers. Personally, I have two websites related to a video game (one displaying some stats, the other being a loot box simulator). Both projects sit a 0 star on Github, but the access logs tell a different story, there has been thousands of (non-bot) visits since both went live, being useful to quite a few players of this particular game. It's hard to measure impact, but it's extremely easy to underestimate it.