Live data from Hacker News

GitHub Résumé

resume.github.io

71–80 of 110 posts

Re: GitHub Résumé

#71
post #63

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.

You're probably right that most forks aren't very interesting - I wonder if it would be possible to parse out actual diffs made by the user on the fork. I've contributed a fair amount of code to BioPython, which is going to be impressive to people in my field. To contribute you work on your own fork and submit a pull request. Under this scheme a single person is getting credit for all the work of the BioPython developers on their own development forks that gets merged into the main repo (or maybe no one is getting credit, as the central repo is owned by an organization.)

Re: GitHub Résumé

#72
It would be nice if it included gists, because I have some interesting non-trivial snippets on there that it doesn't make sense to put into a full repo on Github.

Re: GitHub Résumé

#74
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…

Wouldn't be an active github user devote less time to the work's projects? Personally I know that after my 8-9 hours work day, I barely (no at all) have energy for a side project. How these people can spent almost full time working on the OSS project? (I know some of the developers' job is to work on OSS project, but what about others?)

Re: GitHub Résumé

#75

On the related note - if you need a solid looking offline resume and don't want to spend hours formatting it, check out Almagreta Resume Templates - set of 5 great looking Word templates with some cool features. http://almagreta.com/resume-templates/

Or just use free ones of you are unemployed and spend the money on food.

Re: GitHub Résumé

#76
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…

There's an entirely different reason for using github as a filter. But isn't one of the major reasons we look for a github portfolio, really as an ideological filter for finding cofounders? I wouldn't go so far as calling it communist, but contributing to open-source projects requires a dedication to the 'common good'. If it is communist, it is a great filter for people who would like to own the means of production (…

The biggest contributor to open-source are companies like IBM. Calling IBM communist, is well weird.

If you remove extremists of each movements, seeing value in common-good has nothing to do with communism or socialism or capitalism.

The only filter you apply by looking at github is social. You select individual based on how involved they are in a community. If your company evolve in the same community that can be beneficial. If not, well it is only slightly a bit more relevant than looking at hiring a plumber based on how recognised he is in the car modding community.

Re: GitHub Résumé

#77
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…

FizzBuzz is also extremely easy, yet somehow a lot of applicants seem to fail that. So, any running code would probably elevate you above people without any code.

Re: GitHub Résumé

#78
post #52

Earlier quoted context omitted.

OSS doesn't mean writing for free. A very large chunk of the code on Github was writing on paid time.

It seems like mostly a place where people store config files, mirror code, and dump half-assed work in progress. But would "I wrote this code, and someone posted it on a website" really make someone better than "I wrote this code?"

Not better, just easier to verify.

Re: GitHub Résumé

#79
This is great.

It reminds me that I need to clean up my github account.

Unfortunately I use github for two separate functions -- putting up projects some other people may be interested in and for throwing up scratchpad projects. So I end up with a lot of garbage on my account.

The bulk of my really interesting stuff is in private accounts.

Re: GitHub Résumé

#80

To be useful, this needs to also crawl the projects I contribute to, not just the ones under my account. I am a maintainer of a project under another github account but that completely escapes this tool.

Agreed. My modest contributions to widely used projects are at least as important as my personal projects that nobody uses.
Post reply on HN