Re:Resumes are dangerous
by 286c8cb04bda on Monday April 30, 2012 @05:53PM
(#3911748)
> There are however multiple projects that I think deserve priority when looking through my github, but as far as I can tell, there is no way for me to make it clear what those are.
You should use your user page[1] to draw attention to the things you think are most important.
> Additionally, if I fork a project, it's likely just so that I can add a fix and issue a pull request, that's additionally something I don't think people need to see.
I disagree. Finding your way around a foreign code base enough to make the changes you need is an essential skill for a developer. Repositories you've forked and made pull requests for are a great way to demonstrate that.
> I disagree. Finding your way around a foreign code base enough to make the changes you need is an essential skill for a developer.
Sure, but a whole lot of the forks are like one line changes, they sit there taking up an entire repo, and aren't particularly useful.
If you're sending a resume to a potential employer, don't just provide a link to your Github account. Provide a few links directly to your best projects, the ones you think are worth looking at.
There are however multiple projects that I think deserve priority when looking through my github, but as far as I can tell, there is no way for me to make it clear what those are.
Additionally, if I fork a project, it's likely just so that I can add a fix and issue a pull request, that's additionally something I don't think people need to see.
I worry that someone going through my GitHub profile will see all of my old, incomplete work, and leave before they get to my better projects, any thoughts on how to resolve this.
As an example, here is a link to my GitHub: https://github.com/Arelius