111–120 of 226 posts
From experience, not much. I have an open source project with millions of downloads and thousands of stars on the top of my profile. Never once got asked about it across at least 10-15 interviews with both startups and large companies.
Earlier quoted context omitted.
"error: n/a is not a valid URL"
how about www.idonthaveaninterestinggithub.com
I would hazard a guess that most pure recruiters aren't looking at your GitHub profile other than ensuring that you've provided one. The hiring manager or interview team, however, might be interested in it. Here are some things that I check for in a GitHub profile, as a hiring manager and as a recruiter (hooray startup roles!): 1. Repos that aren't just forks. I've seen plenty of profiles where the majority or entire…
Perhaps you are not aware of the workflow many fs developers use when creating pull requests? You start out by forking the project's repository and create a branch in it where you put your bug fix. Then you submit a pull request using the github UI. End result is that your profile contains a lot of repos appearing to never have had any activity unless you dig into them.
It also appears that you are using candidates github profiles more for finding negatives rather than positives, which is disheartening.
Earlier quoted context omitted.
Everything you say makes sense on the surface. But it scares me a little bit. Do you ignore all my half-done prototypes and junky hacks and experiments?
Or your proprietary work you don't own IP to. Ironically, some look to GitHub to somehow correlate with employment history. Many employed are too busy sinking development time in source that's never releasable. Some companies may contribute to certain OSS projects publically but a lot of their core business code base is protected.
Earlier quoted context omitted.
It's mostly a bikeshed and a signaling thing. Only a "noob" wouldn't know about enumerate(), right? The program could be brilliant in much higher level ways, but mid/senior only-knows-Python hot shot will jump on your anti-idiom like a dog on a dropped hamburger. Including such anti-idioms in your public code can filter out people like that.
Where are you meant to learn this?
Earlier quoted context omitted.
how about www.idonthaveaninterestinggithub.com
URL must start from https://github.com/
Something I really try to find is how they communicate when writing bugs, responding to questions, differences in opinion etc. If you find someone who can respond to an angry user of their library because their feature wasn't implemented, or that can politely turn down a PR for example, that's really good sign.
As a recruiter I can answer this! I do not speak for all recruiters. As a recruiter who is also a programmer, my approach may be nonstandard. * I want to see thoughtful README files. If the README is whatever was generated default by the framework and not edited at all, that's a huge groan and turn off and you lose tons of strength (credibility) as a candidate. * I want to see your code looking pretty. Consistent ind…
I really don’t see why these things are relevant at all. It’s a personal Github profile. Why would anyone add thoughtful readme’s or a clean coding style if they’re the only contributor? I mean, those things are great of course, but not sure if I’d expect it on Github.
But on the other hand I'm no employee and don't know the "virtues" employers look for, haha.
Earlier quoted context omitted.
"error: n/a is not a valid URL"
how about www.idonthaveaninterestinggithub.com
As a hiring manager, I glance at it and take a brief look at anything interesting. It’s good for talking points at the interview, perhaps to ask the candidate to expand upon and explain the work. If the profile is empty, I close the tab and find something else to talk about. I will never, ever penalise a candidate for an empty GitHub profile. So many people just do not have time for open source and that’s totally fin…
While you don't actively penalize folks, it's worth pointing out that candidates with an active GitHub profile often _do_ have an advantage in the scenario you describe.