4 ms·
I am really, really interested to hear from senior developers about this. Especially their comments on the growing trend of requiring open source experience. (I
by why-el 14y ago
I am really, really interested to hear from senior developers about this. Especially their comments on the growing trend of requiring open source experience. (I for one thing don't have any open source, most of my projects are locked in the university and I currently intern at a company building cool things which, well, I can't open source).
Update: I don't have a problem with this really. I am in fact trying to make some time to code, but I don't like how this can sometimes be required.
- mmahemoff 14y agoI doubt open source is a requirement at any of these companies, but it's a huge asset for any job application if you have some good work to show. It stands to reason that if you're going to be spending most of your day writing to code and interacting with coders, people will be interested to see if you have a good repo and handle issues well. So a good Github repo is a huge asset to any job seeker in this industry. It will also help you to be approached by quality companies if your project's popular/high-profile, as savvy recruiters will look at this kind of thing. And, you're likely to be asked about open source in your interview. So if you can say intelligent things about it and show you care about it, it might improve your interview performance too.
- nvarsj 14y agoI wouldn't worry about it. Any company that requires open source contributions hasn't thought very hard about their hiring process. They would be excluding the vast majority of talented (and especially professional) programmers. It's probably most useful as a bullet point to attract a recruiter's attention. So commit a line of code somewhere and stick it on your resume. Not to say you shouldn't work on an open source project. But do it because it's something that interests you, not for your resume.