3 ms·
Well, I was just about to publish my first library to npm but just changed my mind. I have enough performance anxiety as it is and when I know people think I'm
by Kiro 12y ago
Well, I was just about to publish my first library to npm but just changed my mind. I have enough performance anxiety as it is and when I know people think I'm destroying the scene with my "sub-par code" I definitely won't publish.
- drderidder 12y agoAw, come on, you really should. You know what happens when you publish something to npm? Approximately nothing. Your module gets in there with a bazillion others. Maybe someone will use it. Maybe not. Man if you could see the lame-ass library I first published to NPM you would laugh. The only way you get better is by putting yourself out there and just keep doing it.
- HCIdivision17 12y agoPublish it anyway! There's a worst case of no-one noticing, which will hopefully be a great relief for the anxiety (and yet you can say you published your code), and a next worst case that it's never used and is simply inspiration for a better library! Of course best case is people use your code, modify, expand, and build upon it. You'll be credited in their libraries as part of their inspiration, and the state of the art moves forward. There are many that want deeper curation on quality; it's hard to deal with all the noise out there. But it's critical to remember that we can always layer curation on top of the bazaar at no additional cost. As the scene settles into its grooves, the better curators will stand out.