2 ms·
Sure, anything you can list as a contribution is potentially going to come up at interview, and anything you can honestly say you've contributed to is potential
by Silhouette 14y ago
Sure, anything you can list as a contribution is potentially going to come up at interview, and anything you can honestly say you've contributed to is potentially valuable on a CV/resume, particularly early in your career. I'm not disputing either of those things at all.
But if you get to the point where you're discussing your contribution in an interview, you've already got past one of the big hurdles, and the guys interviewing you are now going to be forming opinions based on what you actually say to them personally. In that respect, contributing to an Open Source project or hosting something on GitHub didn't convey any particular advantage just because in theory the recruiters could look you up, and just giving a link to a GitHub account rather than highlighting specific contributions isn't really worth much at all.
My advice to someone wanting to stand out in those early days would simply be "Make stuff, preferably stuff that looks interesting". Whether you contribute to an OSS project or build something else makes little difference IME, and so I think the cookie-cutter "You simply must have a GitHub account and contribute to OSS" wisdom is just plain bad advice.