Polyglot, autodidact. OSS author and contributor. Addicted to writing code, seeking my next 'fix'. Love communicating with an audience whose eyes don't glaze over when I get to the 'good parts'.
I authored jquery-csv. It was the first spec (rfc 4180) compliant CSV parser in JS (and really fast) so it gained a fair amount of popularity in its heyday. So far, it has surpassed 1MM downloads.
I have also authored many other libs/tools over the years. Contributed to many other projects, incl bug fixes, features, tests, and documentation. Participated on a Node working group. Discussed future JS standards via TC39 proposals.
Lately, I created a GH group @vanillawc where I've been building open source standard web components. It's good practice and eventually WC will be common place in the FE ecosystem.
The barrier to creating a project is getting over your own ego. Just because you create something doesn't mean it'll ever gain any traction. So, who cares. Put it out there, try to solve a problem that you think needs fixing.
For every one of my projects that gains any traction, there's dozen that don't. That's the 'hard' part.
The barrier to contributing is understanding the process. Read the CONTRIBUTING.md, follow it. Understand that everything you touch probably took 10x more effort than you think to create and maintain. Try to add real value not opinion, opinions are worthless. OSS is about working together. You'll have a much easier time if you approach a project with a 'how can I help' attitude.
If you suck at reading other people's code, then work at it. Good thing there is a gigantic collection of open source codebases where you can practice.
That's really the 'secret'. Practice, do work, get better, try to understand users, collaborate, be helpful.
The entire ecosystem depends on people who do all of these things well. If you'd like to be a part of the conversation. Prove that you can add value.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I authored jquery-csv. It was the first spec (rfc 4180) compliant CSV parser in JS (and really fast) so it gained a fair amount of popularity in its heyday. So far, it has surpassed 1MM downloads.
I have also authored many other libs/tools over the years. Contributed to many other projects, incl bug fixes, features, tests, and documentation. Participated on a Node working group. Discussed future JS standards via TC39 proposals.
Lately, I created a GH group @vanillawc where I've been building open source standard web components. It's good practice and eventually WC will be common place in the FE ecosystem.
The barrier to creating a project is getting over your own ego. Just because you create something doesn't mean it'll ever gain any traction. So, who cares. Put it out there, try to solve a problem that you think needs fixing.
For every one of my projects that gains any traction, there's dozen that don't. That's the 'hard' part.
The barrier to contributing is understanding the process. Read the CONTRIBUTING.md, follow it. Understand that everything you touch probably took 10x more effort than you think to create and maintain. Try to add real value not opinion, opinions are worthless. OSS is about working together. You'll have a much easier time if you approach a project with a 'how can I help' attitude.
If you suck at reading other people's code, then work at it. Good thing there is a gigantic collection of open source codebases where you can practice.
That's really the 'secret'. Practice, do work, get better, try to understand users, collaborate, be helpful.
The entire ecosystem depends on people who do all of these things well. If you'd like to be a part of the conversation. Prove that you can add value.