Live data from Hacker News

Github is Your New Resume

code.dblock.org

31–40 of 152 posts

Re: Github is Your New Resume

#33
post #25
post #19

Earlier quoted context omitted.

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 ch…

So BitBucket is your resume. Where's the problem?

My resume is my resume. My personal code is closed-source, with the exception of a couple of bits for presentations and an archived project for which I am a maintainer. You could say that "well, that one archived project is your resume," but that would be foolish (not that you are saying that, but it does follow from all of this) because it has little to do with what I actually do.

More than anything, though, I kind of find all this "anoint the buzzwordy startup as the new X" stuff silly. Maybe one company in ten would actually follow a link to Github or Bitbucket on my resume, regardless of the content. At least for now, the resume is the new resume.

Re: Github is Your New Resume

#34
post #23

While this works for freelancers/students/startupers, it doesn't work very well for people working in bigger companies. If your interests are related to your day job, I think it's quite risky to put your code on GitHub, even if the code is not "official". While I do have a GitHub account with some code in it, that code is not really representative. If having a relevant GitHub account becomes a pre-requisite, you may…

> you may be overlooking some good people.

Every heuristic overlooks good people.

This heuristic has the advantage of having next to no false positives, even though it allows for lots of false negatives. Given that false positives are absolutely disastrous while false negatives are merely unfortunate, it's a trade-off I'm happy to make.

Re: Github is Your New Resume

#35
post #30
post #19

Earlier quoted context omitted.

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 ch…

I'm sure a bucket full of your source code on bitbucket will serve the same purpose when interviewing. I'm on the job hunt and in interviewing with some YC startups we haven't really gotten to my github, since they more were interested in some of the closed-source projects I've done at other jobs. I think the overall point of the article is to be able to show people you can code rather than just list it as a bullet p…

The assumption, however, that everyone uses Github results in processes having a dependency on Github. Which is stupid.

Re: Github is Your New Resume

#37
post #4

I came to this conclusion a while ago and tossed Github Badge ( http://drnic.github.com/github-badges/ ) on my personal site.

cool, similar to coderwall

Ah - I just gave coderwall a try this time. Github's authorization prompt is much clearer now as to what I'm allowing access to.

Re: Github is Your New Resume

#38
post #27

What about: - those that use different VCSs? - people who don't have the time (due to their job or other circumstances) to work on things they can open source? - people who work at companies that essentially own everything they might do so you can't work on open source? and - companies where hiring goes through HR who won't know what the hell Github is? Having work on Github is probably a good idea for college studen…

While this post talks about GitHub, i think it very well applies to any distributed version control system.

Having an open source project is another means of visibly showing your enthusiasm, and even skill set. Notice how I don't say actual 'skill'. That is always subject to the eye of the beholder.

By your definition, someone better tell https://github.com/jeresig & https://github.com/zedshaw they're JR developers and should go back to school.

Re: Github is Your New Resume

#39
post #35
post #30

Earlier quoted context omitted.

I'm sure a bucket full of your source code on bitbucket will serve the same purpose when interviewing. I'm on the job hunt and in interviewing with some YC startups we haven't really gotten to my github, since they more were interested in some of the closed-source projects I've done at other jobs. I think the overall point of the article is to be able to show people you can code rather than just list it as a bullet p…

The assumption, however, that everyone uses Github results in processes having a dependency on Github. Which is stupid.

We use github, but have a fallback server.

Re: Github is Your New Resume

#40
post #27

What about: - those that use different VCSs? - people who don't have the time (due to their job or other circumstances) to work on things they can open source? - people who work at companies that essentially own everything they might do so you can't work on open source? and - companies where hiring goes through HR who won't know what the hell Github is? Having work on Github is probably a good idea for college studen…

Github is to coders what an online portfolio/web presence is for designers. Look at the design industry... corporate designers and grads and freelancers used to all have a hard copy, artfully crafted portfolio on sensual-to-touch paper stock.

That's gone. And no one cared if the corporate designers didn't have time to create a website. Even if you still have an amazing portfolio (which is the resume for the designer), you better have something online (whether they are personal projects done outside of work, or glimpses of projects done at work).

The paper resume is going away anyway. And then when HR finally gets up with the times, do you really think they are going to say, "Aww, it's ok, we understand you didn't get on Github because you were waiting for us..." No.

HR people hiring designers using their online portfolio is a lagging indicator. And the same will go for HR people hiring developers based on Github.

Post reply on HN