That's true. It's also very much depending on who's reading the resume what's relevant or not. My, maybe naive, thought on this matter is that anybody that's interested in such things probably looks me up on github, rather than reading it in a resume.
Absolutely true, as long as you link your GitHub on your resume! If you have a lot of contributions though it may be worth directing the employer to ones that are more relevant or impressive.
If I made contributions to a significant project on a regular basis I'd put it explicitely on the resume, but if it's just a few contributions here and there a link to your github is definitely enough imho.
it may be worth directing the employer to ones that are more relevant or impressive.
You can "pin" some repositories on your github page so they always appear first and on your github profile. Everyone should take the time to do it when looking for a job.
Also maybe go through your old pet projects that never went anywhere, have 0 tests and don't reflect your current skills and make them private.
That's true. It's also very much depending on who's reading the resume what's relevant or not. My, maybe naive, thought on this matter is that anybody that's interested in such things probably looks me up on github, rather than reading it in a resume.
Absolutely true, as long as you link your GitHub on your resume! If you have a lot of contributions though it may be worth directing the employer to ones that are more relevant or impressive.
If I made contributions to a significant project on a regular basis I'd put it explicitely on the resume, but if it's just a few contributions here and there a link to your github is definitely enough imho.
You can "pin" some repositories on your github page so they always appear first and on your github profile. Everyone should take the time to do it when looking for a job.
Also maybe go through your old pet projects that never went anywhere, have 0 tests and don't reflect your current skills and make them private.
Great tips, thank you!