Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Github is Your New Resume

code.dblock.org

Post reply on HN
Print view View original

11–20 of 152 posts

Re: Github is Your New Resume

#11

Post by gaius »

unshift wrote: post #2

this may be true in startup land, where hires are evaluated by the engineers/managers/founders but it's absolutely not the case in the world of BigCorps. many recruiters (including internal ones) are less technical than anyone would like and have to operate on looking at key words in a resume before deciding what to pass along to managers. a github account with a bunch of code in it would be so confusing they'd just…

Nah, not really, because "a github account with a bunch of code in it" is the signal.

Of course, it can be gamed by someone who just forks a bunch of other people's repos, which a recruiter won't be able to spot but "github" is a keyword that can be searched for on a CV like any other.

Re: Github is Your New Resume

#12

Post by krobertson »

I recently started a new job and their recruiter found me through my Github profile. Aside from that, I put my Github link on my CV and have for a while.

Additionally, when I am interviewing others, I always like to see a Github link or will Google them to find a Github account. Even though people may work a lot in closed source, it is interesting to see the activity history, to see which projects they've forked, patched, written, or contributed to.

It sometimes varies based on the community you're in, but the Ruby community is very collaborative and sharing contributions. Even when I've worked in largely closed source codebases, I'll still encounter bugs in other libraries, fork them, fix it, and send a pull request. Those all show in my repo list and activity feed.

Re: Github is Your New Resume

#13

Post by gaius »

programminggeek wrote: post #9

I like the idea of GitHub as a resume, but most of the code I drop in GitHub is closed source and I don't spend a lot of free time hacking on other people's projects. So, while a GitHub resume is a great idea if you do a lot of open source hacking, it is not nearly as useful if you are working on private code.

Yeah. I mean, accountants and lawyers don't publish accounts and cases they've worked on pro-bono do they?

Re: Github is Your New Resume

#14

Post by jjm »

lucian1900 wrote: post #5

GitHub in particular is problematic for those of us that don't particularly use Git, and use other hosts for their code. Something like ohloh is much better suited to being a CV.

Ohloh has everything but the code.

It reminds me of those "CSS galleries" but for open source projects.

In the end, I'm where the code is, and that place is GitHub.

Re: Github is Your New Resume

#15

Post by timruffles »

If that was to become true, it'd be great to be able to curate your profile. At the moment your repos appear in order of newness, and an unchanged fork of someone's repo could be the first thing potential employers see.

Re: Github is Your New Resume

#16

Post by stevelosh »

lucian1900 wrote: post #5

GitHub in particular is problematic for those of us that don't particularly use Git, and use other hosts for their code. Something like ohloh is much better suited to being a CV.

If you're using Mercurial instead of Git you can create a mirror on GitHub with little effort (unless you're doing something pretty crazy with your DAG): http://hgtip.com/tips/advanced/2009-11-09-create-a-git-mirro...

This also lets git users contribute to your project, so you get the benefit of GitHub's community without having to deal with git.

Re: Github is Your New Resume

#17

Post by icefox »

unshift wrote: post #2

this may be true in startup land, where hires are evaluated by the engineers/managers/founders but it's absolutely not the case in the world of BigCorps. many recruiters (including internal ones) are less technical than anyone would like and have to operate on looking at key words in a resume before deciding what to pass along to managers. a github account with a bunch of code in it would be so confusing they'd just…

Not everyone reviewing resumes at BigCorps are bad. For what it is worth I work for 'BigCorp' and when looking for new guys on my team I do read any code I am given and go out looking for any code on GitHub and elsewhere. Internal transfers are easier as I don't have to do any hunting and just go looking through our internal repository at their commits.

Re: Github is Your New Resume

#18

Post by eropple »

lucian1900 wrote: post #5

GitHub in particular is problematic for those of us that don't particularly use Git, and use other hosts for their code. Something like ohloh is much better suited to being a CV.

Agreed. Git is obnoxious and Github offers me nothing, which is why I use Atlassian's Bitbucket. But the assumption, silly and unpleasant as it is, is that "everyone uses Github." Well, no, they don't. I really could not care less "where the code is," as per the sibling post to this one; I care for "where things don't aggravate the hell out of me," and that's emphatically not Github.

I disagree, however, regarding Ohloh--too chaotic, too messy, too many false positives. I don't think that, right now, there's a good solution. Something to think about, I guess...

Re: Github is Your New Resume

#19

Post by eropple »

stevelosh wrote: post #16
lucian1900 wrote: post #5

GitHub in particular is problematic for those of us that don't particularly use Git, and use other hosts for their code. Something like ohloh is much better suited to being a CV.

If you're using Mercurial instead of Git you can create a mirror on GitHub with little effort (unless you're doing something pretty crazy with your DAG): http://hgtip.com/tips/advanced/2009-11-09-create-a-git-mirro... This also lets git users contribute to your project, so you get the benefit of GitHub's community without having to deal with git.

Interesting, but this doesn't address the other problem--I fundamentally dislike Github! (I use Bitbucket because of consistently stellar support from Atlassian and an overall pleasant working experience.) And going outside my current, working ecosystem for benefits I consider dubious at best--the overwhelming majority of open-source projects get no outside commits, ever, and magic Github pixie dust doesn't really change that--isn't really a good use of time.

For me, Git and Github are both problems with this "GitHub's your resume" thing, not one or the other.

Post reply on HN