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

41–50 of 89 posts

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

#41

Post by stevekemp »

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…

> Noone cares about GitHub.

It's funny I used to get interview-offers from people who'd seen some of my C++ code, despite the fact that I'm not really a developer.

Shortly after that I moved the project into a Github organization, just for neatness, and those emails stopped. It's like people searching for C++ code don't see "me" any more, just the faux organization-owner.

I'm a little amused that people are emailing random github developers with enticing offers of interviews, yet can't handle the extra layer of indirection. But anything that cuts down on random spam (No I don't want to relocate to America, thanks) is probably a good thing!

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

#42

Post by paradite »

MaxLeiter wrote: post #20

Here's my solution: http://maxleiter.com Also have the same repos on my pinned repositories on github. On the site, for the projects I contribute to, I mention the majority of what I actually worked on and provide links to the PRs. Also, the "contributor" badges lead to a Github search of my name on the project.

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.

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

#43

Post by dsacco »

humanrebar wrote: post #3
nawitus wrote: post #2

"Nobody cares about your code" That's a peculiar claim about people who hire employees to create code. "It’s not the code that counts, it’s the product" So is everyone only hiring programmers who write code which can be sloppy and full of technical debt and impossible maintain, as long as the product works okay for now?

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.

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

#44

Post by dsacco »

humanrebar wrote: post #18
cubano wrote: post #10

Earlier quoted context omitted.

So not really, right? Code is just symbols on a screen. It's the abstractions that count.

Code is how we realize abstractions. They complement each other. The point is that the code is a key part of the product, so saying it's an afterthought is to misunderstand the product.

I think the context matters here. The underlying point is not to be taken so literally. It means don't prematurely optimize your code until you have a functional, enjoyable piece of software. Then sure, work on maintainability and improved performance.

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

#45

Post by Sekhmet »

Walkman wrote: post #22

The last part is definitely not true at all. I skipped the coding part of the interview process for my current job because I had good code on GitHub. Also got job offers out of the blue because I contributed to multiple projects. I feel there are companies looking at only GitHub (for a good reason IMO) nowadays for candidates.

I got my current job just with GitHub. I was asked to only show my GitHub profile. I didn't need resume at all. Some companies might not care about your GitHub, but they are always some that do.

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

#46

Post by GordonS »

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 can see how it wouldn't be relevant if you do a lot of hiring.

In my case however, I hire maybe 3-4 devs each year and would definitely spend time looking at candidates' github repos... if any of the CV I got ever actually mentioned any!

For me at least, the more filtering I can do before interviewing, the better. A GitHub repo would also be a great discussion point during interviews.

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

#47

Post by MaxLeiter »

paradite wrote: post #42
MaxLeiter wrote: post #20

Here's my solution: http://maxleiter.com Also have the same repos on my pinned repositories on github. On the site, for the projects I contribute to, I mention the majority of what I actually worked on and provide links to the PRs. Also, the "contributor" badges lead to a Github search of my name on the project.

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

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

#48

Post by isaac_is_goat »

humanrebar wrote: post #3
nawitus wrote: post #2

"Nobody cares about your code" That's a peculiar claim about people who hire employees to create code. "It’s not the code that counts, it’s the product" So is everyone only hiring programmers who write code which can be sloppy and full of technical debt and impossible maintain, as long as the product works okay for now?

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

Code is not the product. Code is part of the assembly line that becomes the product. An innefficient/bad quality assembly process will result in a sub-par product. Developers don't build the product, they build the assembly line.

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

#49

Post by abelM »

bigtoine123 wrote: post #37

"Nobody cares about your code" piece of advice doesn't make sense to me. There are people who cares about your code, I had projects in GitHub I'm really proud of

In general, I would look at it like this ... Your coding style is your opinion and how you understand a program works. Until, I am required to understand it or until you grab my attention, I or anyone won't care. It is nutting personal but time constraints and also, we (developers) are the only ones who care about code quality. If product needs to be built fast then code quality is placed in the backlog.

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

#50

Post by XYawqd »

cjcenizal wrote: post #38
B73kkww wrote: post #34

Earlier quoted context omitted.

I often see an inverse correlation between being able to "talk about code" and actually producing good code. That is not only between persons: I can get myself into a talker's mindset in a couple of days just by reading, drawing diagrams and generally doing anything that increases self confidence. My actual coding abilities drop in the process because the ability to see abstract graphical patterns decreases. On my be…

I think there's a correlation between being able to explain something and fully understanding it. Being able to think clearly and communicate clearly are interconnected -- if you're programming by instinct then you're not thinking critically about the problems you're solving.

I'm more with Feynman: If you are able to do something, you understand it.

Natural language quite primitive when it comes to math/programming. Explanations are full of holes and gloss over important things.

It is funny that you mention "critical thinking". The vocabulary of a music critic/philosopher like Adorno is astounding and impressive.

This did not prevent Celibidache (a famous conductor) from calling Adorno the "biggest blowhard of the 20th century".

Intuition always rules in the discovery phase. Often others come and "explain" the works they did not create, because the creator is already busy doing his next thing.

Post reply on HN