3 ms·
But on the big OSS projects, where making a contribution wins you significant geek cred, is anyone involved in a hire/no-hire decision really going to take a lo
by nl 14y ago
But on the big OSS projects, where making a contribution wins you significant geek cred, is anyone involved in a hire/no-hire decision really going to take a load of time to look through a bunch of commits you made and figure out whether they were any good and what sort of impression they give of you?
This is true, but not the point (at least until automatic tools run through the commit history and rate the contributions automatically).
Contributing to OSS projects gets you through filters, in the same way being Ex-Google will open a lot of doors.
The fact I'm an Apache committer and have code included in Spring gives me some credibility as a Java programmer (even if I haven't been active in either of those roles for years). Hiring managers are more likely to put you on the "worth looking at" pile rather than the "doesn't have a clue" pile based just on that.
- Silhouette 14y agoFair enough, but is the advantage here that you have worked on OSS projects, or that you have worked on big name projects that a recruiter might have heard of?