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

How to present a GitHub project for your resume (2016)

thehftguy.com

Post reply on HN
Print view View original

71–80 of 89 posts

Re: How to present a GitHub project for your resume (2016)

#71

Post by concede_pluto »

ibejoeb wrote: post #55
funkaster wrote: post #33

> Conclusion: Noone cares about GitHub. Noone is gonna read it. Everyone is gonna ask for it nonetheless, cause it’s hype. True. We don't ask for GitHub links because they are pointless from a screening perspective. I'm happy to talk about them during an interview, but if I see a github link in a CV, there's little chance I will visit it. (Source: I'm a hiring manager at a tech company, have been in a similar positio…

>I would have no time at all to do anything if I start looking at all my candidates' github links. How do you decide to get the candidate in the pipeline? Presumably you're reading a CV and a letter, then having a phone call, etc. You don't think it would add context and clarity if you took 20 minutes from those activities and devoted them to examining a specimen? Do you do whiteboard interviews? I've never done one…

If your published code is bad I can quickly learn whether I'm wasting my time, but if it's good I still need to see you code in person. Neither GitHub nor homework proves you did the work.

Re: How to present a GitHub project for your resume (2016)

#72

Post by dpritchett »

ashark wrote: post #9

If you expect the people reviewing it to be developers: 1) Tell me how to run it locally (docker is a good idea, if relevant) and where the code's entry point is. 2) Don't use a framework. I don't want to spend time figuring out which of the 20+ code files here have actual code you wrote and which are auto-generated or boilerplate. I'd much rather see something simple but well-written using the language's standard li…

I failed a interview for a job I'd like to have gotten by trying to impress the reviewers with more handrolled stuff and nothing bloated. I asked and the folks who passed just used Rails. My submission was alternately perceived as underwhelming and trying too hard.

Re: How to present a GitHub project for your resume (2016)

#73

Post by ioddly »

MaxLeiter wrote: post #47
paradite wrote: post #42

Earlier quoted context omitted.

Fantastic profile for someone still in high school! One unsolicited suggestion: You can fetch the number of stars of each repo to showcase the their significance, recruiters are more attracted to quantified numbers.

Thanks. I was thinking about that but really enjoy not requiring JavaScript, however maybe its worth it. I'll try it out

I've just been using this: https://shields.io/

Re: How to present a GitHub project for your resume (2016)

#74

Post by humanrebar »

dsacco wrote: post #43
humanrebar wrote: post #3

Earlier quoted context omitted.

Yeah. Code is the product. It's like saying, "we don't sell ingredients, we sell meals".

...which is true. Restaurants sell meals, not ingredients. Chefs don't give you ingredients to eat, they craft the base ingredients into something worth selling, preferably with a good experience. I get your point, but that analogy has backfired on your point. I'd rather cook something that tastes really good using whatever ingredients are around and then improve the ingredients (among other things) later on.

The meal is made up of the ingredients. You can't make a good meal from spoiled meat.

Restaurants sell meals. Because of that, they have to pay attention to their ingredients. At least to make sure they won't make anyone sick. And, if they are making a premium product, they need high quality ingredients to make a high quality product.

You can't just replace the fresh mozzarella with Kraft singles and still sell pizzas for a premium price.

Re: How to present a GitHub project for your resume (2016)

#75

Post by brooklyn_ashey »

TheCowboy wrote: post #61
acidus wrote: post #58

Earlier quoted context omitted.

And how can you get better at it?

Writing. When you engage in writing out your thoughts you quickly realize that you may not have as coherent or clear explanation as it may feel to you. You end up doing some research and thinking about how to express it. At the very worst, you come away with a better way to express one specific thing. Even just trying to provide quality explanations to comments on Reddit is a good practice. That won't always help whe…

I agree. Writing helps. Murakami thinks so too! Have you read What I talk about when i talk about running? It might be interesting for swes. He writes about how writing helps him refine thought and relates this to training in running. Great book.

Re: How to present a GitHub project for your resume (2016)

#76

Post by andybak »

ashark wrote: post #9

If you expect the people reviewing it to be developers: 1) Tell me how to run it locally (docker is a good idea, if relevant) and where the code's entry point is. 2) Don't use a framework. I don't want to spend time figuring out which of the 20+ code files here have actual code you wrote and which are auto-generated or boilerplate. I'd much rather see something simple but well-written using the language's standard li…

> Don't use a framework.

I'd like to see people using the appropriate tools for the task at hand. I can imagine slapping my head and asking "Why the hell didn't they just use x". I wouldn't want to pay someone to reinvent the wheel and I'd want someone to demonstrate both their awareness of and their ability to evaluate appropriate code from the relevant ecosystem.

Re: How to present a GitHub project for your resume (2016)

#77

Post by brobinson »

mnutt wrote: post #54

Often when I see candidates' github accounts they are mostly forked repos with no changes and projects with rails scaffolding. There might be something there but it's really hard to dig through and find. I would suggest candidates build their own projects using documented pull requests and point the hiring manager to the closed PR page of their project. Or even better, point them to a substantial PR they completed on…

Are you just looking at the master branch on their forks? If you want to send a PR to another repo, you _must_ fork that repo.

I have 43 repos, but 21 of them are forks. I've never committed anything on master on any of the forks, but I've created my own branches in order to open PRs on 18 of them.

The easiest thing to do is use the "Sources" option from the drop down on their repos page (shows only _their_ repos) and use something like https://showmyprs.com/ to see their external contributions.

Re: How to present a GitHub project for your resume (2016)

#78

Post by oliv__ »

humanrebar wrote: post #74
dsacco wrote: post #43

Earlier quoted context omitted.

...which is true. Restaurants sell meals, not ingredients. Chefs don't give you ingredients to eat, they craft the base ingredients into something worth selling, preferably with a good experience. I get your point, but that analogy has backfired on your point. I'd rather cook something that tastes really good using whatever ingredients are around and then improve the ingredients (among other things) later on.

The meal is made up of the ingredients. You can't make a good meal from spoiled meat. Restaurants sell meals. Because of that, they have to pay attention to their ingredients. At least to make sure they won't make anyone sick. And, if they are making a premium product, they need high quality ingredients to make a high quality product. You can't just replace the fresh mozzarella with Kraft singles and still sell pizza…

Fast food begs to differ: you can make some pretty tasty stuff with terrible terrible ingredients.

It's tasty alright... Just don't expect to wake up feeling great the next morning.

Re: How to present a GitHub project for your resume (2016)

#79

Post by dozzie »

ashark wrote: post #9

If you expect the people reviewing it to be developers: 1) Tell me how to run it locally (docker is a good idea, if relevant) and where the code's entry point is. 2) Don't use a framework. I don't want to spend time figuring out which of the 20+ code files here have actual code you wrote and which are auto-generated or boilerplate. I'd much rather see something simple but well-written using the language's standard li…

> 1) Tell me how to run it locally (docker is a good idea, if relevant) [...]

Actually no, Docker is not a good idea for an instruction on how to run the code. First, if I don't use Docker, I have no fsckin' way to tell which magical --switches are for Docker and which are for the program. Second, if your program cannot be easily run without Docker, you have vastly overcomplicated the whole thing.

Re: How to present a GitHub project for your resume (2016)

#80

Post by [deleted] »

deadsy wrote: post #19

As an engineer hiring engineers, if a candidate gives me a guthub url then I'm going to take a look. There are too many people coming through the door who are marginal coders, so if I can get a sense of what they do for something other than a white board problem then that's a good thing.

[deleted]
Post reply on HN