News for hackers. Stuff that matters.
Re:Too Many Tools and Frameworks (2015) by ffggvv on Tuesday October 04, 2016 @03:22AM (#12633854)
Nope they won't, because then your are just another contributor.

There are thousand working on linux (the kernel). How many of them do you know?

Re:Too Many Tools and Frameworks (2015) by raverbashing on Tuesday October 04, 2016 @05:53AM (#12634374)
Which is better (for your CV), be a contributor to Angular.js (example) or create your something.js that left-pads and right-pads at the same time?
Re:Too Many Tools and Frameworks (2015) by nitely on Tuesday October 04, 2016 @11:40AM (#12636337)
I think a better example would be: be a contributor to Angular.js or be the creator of Aurelia.js.
Re:Too Many Tools and Frameworks (2015) by ebiester on Tuesday October 04, 2016 @09:16AM (#12635231)
From what I can tell, something.js if the amount of code is equivalent.

Having a patch or two in angular doesn't seem to move the needle.

Re:Too Many Tools and Frameworks (2015) by raverbashing on Tuesday October 04, 2016 @09:22AM (#12635263)
No. Because nobody knows about your something.js

Getting something on Angular means you were able to get your changes approved and merged (team work)

Situation is better if you can have a bigger project or more people using your something.js

Re:Too Many Tools and Frameworks (2015) by bungle on Tuesday October 04, 2016 @11:25AM (#12636220)
Well, left pad was quite famous. And especially famous when the author removed it. You never know.
Re:Too Many Tools and Frameworks (2015) by alxndr on Tuesday October 04, 2016 @07:29PM (#12640497)
Was it famous before the author removed it?
Re:Too Many Tools and Frameworks (2015) by thewhitetulip on Wednesday October 05, 2016 @05:44AM (#12642622)
It actually helps if you contribute to an existing project, because it is like, you worked with others on an existing codebase and contributed features in a big project which has high visiblity and is being used in real life by real people.

Much of what we work is all with people and on large codebase, so if you are contributing to existing project, it is actually helpful for interviews. Also it takes weeks to get a PR accepted, so if you actually were successful in getting your feature accepted, it shows your resolve to contribute the feature because you want to contribute and not because you want to do a PR stunt for your career (and not get annoyed by the constant changes which the authors ask, which are close to a million)