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

GitHub Résumé

resume.github.io

Post reply on HN
Print view View original

61–70 of 110 posts

Re: GitHub Résumé

#61

Post by Kudos »

ultimoo wrote: post #16

> As a software startup owner I really enjoy when people send us their résumés and they include their github account so we can see tangible work they have done. I sometimes feel very insecure when I read statements like this. I consider myself a good and a passionate programmer with "above-average programming skills", if there is such a thing. However, I have (so far) never been able to manage contributing to open so…

The guy you're quoting hired me around the time he made this, and I have next to zero OSS chops.

All of my free time that I put towards software selfishly goes into my side project, but it does mean I have some interesting stories to tell on problems I've solved.

Re: GitHub Résumé

#62

Post by bennyg »

seivan wrote: post #59
bennyg wrote: post #58

As a guy who routinely has his resume tossed because of a lack of technical degree, Github is a godsend for the auxiliary benefit of companies that want to take me serious can find my code there. I routinely have stuff trend in Objective C and it's slightly frustrating when interviewers think the toughest question is what's different between an NSArray and NSMutableArray because my resume says "Majored in Graphic Des…

Same here man. http://osrc.dfm.io makes me sound good as well, top 2% Objective-c

Woah that's awesome! I'd never seen that site before. Top 5% here.

http://osrc.dfm.io/bennyguitar

Re: GitHub Résumé

#63

Post by chalst »

bendmorris wrote: post #55

Unfortunately, this ignores forked repositories. The open source contributions I'm most proud of were to projects that I didn't start, so none of them are listed here.

I think that's probably by design. From the point of view of "project as CV items", most forked items have very little in the way of useful contribution to them - that doesn't defeat your point that some forks are very cool indeed.

Re: GitHub Résumé

#64

Post by danielweber »

evanspa wrote: post #57
ultimoo wrote: post #16

> As a software startup owner I really enjoy when people send us their résumés and they include their github account so we can see tangible work they have done. I sometimes feel very insecure when I read statements like this. I consider myself a good and a passionate programmer with "above-average programming skills", if there is such a thing. However, I have (so far) never been able to manage contributing to open so…

But what about personal projects? For me, the best way for learning new programming languages, libraries, techniques, etc, is to build something with that language. Naturally, I put this type of work into a public repo on Github and slap an OSS license on it. It's a great way to learn, but also to showcase your work to potential employers (or fellow hackers, etc).

"Here is my very first project" seems like a horrible thing to show off to potential employers. My first projects in any language are full of hacks and "just-get-it-working" type stuff until I figure out the Right Way to do things.

Putting up half-finished junk like that doesn't serve anybody's interest. At best it is ignored. At worst it is just pollution being dumped into the world in that any newbie seeing it would become actively dumber.

Re: GitHub Résumé

#65

Post by hackula1 »

jmduke wrote: post #12
rcthompson wrote: post #4

Hmm. This is missing my most popular repo, https://github.com/DarwinAwardWinner/ido-ubiquitous Probably because for historical reasons, my repo is not the "root" on GitHub (it started out an an anonymous snippet on EmacsWiki and someone else put it in its own GitHub repo, which I later forked).

(Submitter but not the author.) It looks like that's because its using GitHub's timeline API, which -- in addition to GitHub's general repository API -- only retrieves repositories which are actually rooted at the given user. Sort of a shame; I feel like most people's most interesting/important open source activity is on repositories which they don't own.

At the same time, this probably cuts down on "me too" contributions. I have a repo that has been gaining popularity lately and have been flooded with pull requests that do nothing but add a jshint file or other dev environment changes.

Re: GitHub Résumé

#66

Post by prawks »

10098 wrote: post #44
_pmf_ wrote: post #42

Earlier quoted context omitted.

> which doesn't prevent them from being awesome But how can they be awesome if they don't tell the Internet about it? It's unfathomable!

To be honest, there's a little bit of "I'm too old for this shit" attitude among them. They have have demanding jobs and families, and probably couldn't care less about what internet thinks. I also have to note that I've never met a person my age (early twenties) who I could call a great engineer. Promising - yes, talented - yes, but not great. You know, the type of people that you shut up and listen to when they tal…

There's for sure a difference in people I would call brilliant "hackers" and people I would call brilliant "architects".

I think it's very difficult to be the latter without having constructed a handful of large systems, and those take significant time even if you do them back-to-back.

Re: GitHub Résumé

#67

Post by parennoob »

Any employers looking to use this to seriously evaluate candidates -- you are wide open to having your analytics gamed by people looking to get their foot in the door. And commits are much easier to fake out and automate than degrees. :)

Re: GitHub Résumé

#68

Post by prawks »

icelancer wrote: post #28
ultimoo wrote: post #16

> As a software startup owner I really enjoy when people send us their résumés and they include their github account so we can see tangible work they have done. I sometimes feel very insecure when I read statements like this. I consider myself a good and a passionate programmer with "above-average programming skills", if there is such a thing. However, I have (so far) never been able to manage contributing to open so…

>Do startups really look at github contributions as the ultimate measure of one's tech chops or are looking for people who go that extra bit and make time in their schedules for contributing back to the community? When I was hiring, yes. There is no easier and simpler way to evaluate someone before bringing them in for an interview than checking their verifiable OSS contributions. It's low friction. Doesn't mean we d…

> people who actually could prove they had done work went to the head of the line

Isn't that usually sorted out by the resume piece of the puzzle? By listing placed an applicant has actually worked?

I know it's not your full hiring procedure you've outlined here, but I just see that kind of filtering as very naive. You'd have to make a huge number of assumptions to go from someone's OSS contributions to anything about their work ethic.

Re: GitHub Résumé

#69

Post by evanspa »

danielweber wrote: post #64
evanspa wrote: post #57

Earlier quoted context omitted.

But what about personal projects? For me, the best way for learning new programming languages, libraries, techniques, etc, is to build something with that language. Naturally, I put this type of work into a public repo on Github and slap an OSS license on it. It's a great way to learn, but also to showcase your work to potential employers (or fellow hackers, etc).

"Here is my very first project" seems like a horrible thing to show off to potential employers. My first projects in any language are full of hacks and "just-get-it-working" type stuff until I figure out the Right Way to do things. Putting up half-finished junk like that doesn't serve anybody's interest. At best it is ignored. At worst it is just pollution being dumped into the world in that any newbie seeing it woul…

Maybe, maybe-not. Couple things: some of my "personal projects" are more than just learning some new things. Often the project is for scratching an itch, and is a useful thing to me. That's the type of stuff that I will "polish." This forces me to not only learn the new language, but to write code idiomatically, write unit tests, etc.

For "junk projects" that are solely to play around with some new thing, I think it's okay to make that clear in the README of the project and still put it in a public repo. If I'm an employer, I'm going to like the fact that you're actively learning new things; if it's a "play" project, made clear in the README, I wouldn't hold against you writing crappy code. Instead, I'll be more impressed that you're actually learning new things. Just my $.02.

Re: GitHub Résumé

#70

Post by tokenrove »

prawks wrote: post #68
icelancer wrote: post #28

Earlier quoted context omitted.

>Do startups really look at github contributions as the ultimate measure of one's tech chops or are looking for people who go that extra bit and make time in their schedules for contributing back to the community? When I was hiring, yes. There is no easier and simpler way to evaluate someone before bringing them in for an interview than checking their verifiable OSS contributions. It's low friction. Doesn't mean we d…

> people who actually could prove they had done work went to the head of the line Isn't that usually sorted out by the resume piece of the puzzle? By listing placed an applicant has actually worked ? I know it's not your full hiring procedure you've outlined here, but I just see that kind of filtering as very naive. You'd have to make a huge number of assumptions to go from someone's OSS contributions to anything abo…

Unfortunately it's easy to make claims on one's resume that are hard to refute. Yes, you worked there, but what did you actually do? What did the code you wrote look like?

Every writer who advocates FizzBuzz or something related has specifically mentioned these are candidates with resumes that got them to the interview stage, but who couldn't actually write code.

Looking at open source code or a portfolio is an extension of that, since one doesn't really have time in an interview to do anything more complex than FizzBuzz.

Post reply on HN