This brings up a really good point. Hyperlinking to Github, or other work, in your resume is important. You should make it as easy as possible for the reviewer to say 'yes' in a short amount of time.
What sucks is that even if it's hyperlinked, people probably won't click it. I don't have clickthrough data for resumes (if someone does, that'd be awesome), but anecdotally, clicks won't happen unless you really call out to the reader that it' worth their time.
When you're reading resumes you go into awful zombie mode (I do this too). If you're writing one, pretend your audience is a braindead zombie that needs to be spoonfed everything. If you have cool projects, list them and describe them concisely in a way that makes clear that they're interesting and a big deal. And link to each project if possible to increase odds of click.
Obviously everyone is different in how they review resumes, but I am Software Engineer and whenever I see a resume with a github, I'll usually visit that first before even reading the rest of their resume.
Since I work in and around Github and open source, usually someone's Github will tell me what I really want to know about them (not always, but really good candidates have a Github profile that stands out).
Very true. Although candidates also need to be careful to link in moderation. It's all about adding the most interesting/relevant projects and then knowing when to stop. If you give a zombie too many links to click (like on the web), he/she will most likely click none of them and move on.
I've been writing my programming blog for nearly 10 years and always put it up top on the resume, in all that time only two people actually read anything on the blog, and both hired me. The rest of people who actually read my resume (itself rare) never even looked it up.
