…ur library and you go ahead and change things and break their apps, they will not be happy campers. Make updates to your lib in a compassionate way.
Fuck those people.
IF ANYONE EXPRESSES INTEREST IN WORKING ON YOUR LIB, MAKE THEM A MAINTAINER
… built it right. And the next time you build something, you’ll be even better prepared for success. Pat yourself on the back, you fuckin shipped!
Be Bold. Be Confident. Be Ready To Get Your Shit Ripped Apart.
…ou should ALWAYS include a LICENSE.txt, or some people won’t be able to use your repo. Just do MIT. Don’t be cute with some self written bullshit license. Just MIT. Just do it.
…t types are in place. Write your libs with types, export and provide the types, and thank me later. Or let somebody else type it later, third party style, out of date and probably wrong. Do whatever you want.
…at is very explicit and not clever. It makes it easier to contribute to. Name things what they are, don’t do masturbatory functional programming, if you’re going to do a hack, put a comment in about why.
…g yours does, you’ll need something that sets it apart. Lets say you want to build the next lodash. Good fuckin luck (sorry had to get that out of the way). But outside of that, in order to tap into lodash’s market s…
I have the distinct advantages of a) not giving a fuck and b) having a weird amount of unearned confidence, so I just put shit out, but I’ve noticed its hard for a lot of people.