Take the 2-minute tour ×
Programmers Stack Exchange is a question and answer site for professional programmers interested in conceptual questions about software development. It's 100% free, no registration required.

I've made significant, well written code contributions to an open-source project.

Unfortunately, the project as a whole is both unpopular, and, to put things mildly, not particularly flashy. Unlike the poster of this HN message, I'm in the opposite boat - I'm proud of my contributions, but embarrassed by the end product.

How would you weigh the quality of your contributions versus the quality of the end product versus the popularity of the end product when deciding if you should include it on your resume/portfolio or not?

share|improve this question

closed as primarily opinion-based by Snowman, Bart van Ingen Schenau, Kilian Foth, durron597, GlenH7 Apr 8 at 21:00

Many good questions generate some degree of opinion based on expert experience, but answers to this question will tend to be almost entirely based on opinions, rather than facts, references, or specific expertise. If this question can be reworded to fit the rules in the help center, please edit the question.

2 Answers 2

up vote 5 down vote accepted

Always include it in your resume or portfolio because it shows where you have chosen to spend your time, regardless of the project's success and how interesting it may be.

I don't think anyone doing the recruiting will bother to look through each contribution you've made to the open-source project, but it demonstrates that you have volunteered your efforts in your spare time for whatever reason (e.g. helping out a project, honing your technical skills, gaining experience, etc.) As a result, this shows your passion about what you do.

share|improve this answer

I'd definitely include the contributions, but I might put a different spin on it. Rather than linking to the project itself, I might add some samples from your revision history (I'm assuming that at least RO source is available publicly?). Of course, you should also include a link and brief description of the project in its entirety, but listing the revisions may shift the focus from the app as a whole to your individual contributions.

I know that if I was reviewing a resume that had links to the candidate's individual contributions (or a subset of), I'd be very inclined to review those, and just glance at the product as a whole, rather than looking at the project overview and using that as the barometer of the candidate's abilities.

Maybe it's just me though :)

share|improve this answer

Not the answer you're looking for? Browse other questions tagged or ask your own question.