News for hackers. Stuff that matters.
Re:Resumes are dangerous? by laurent123456 on Monday April 25, 2022 @04:47AM (#31151961)
If you don't have much to show on your GitHub profile, simply do not provide the URL. It's just one data points among others, but it's true that it's useful to see the candidate's coding skills in advance and the easiest for that is open source code (since anything else probably can't be shared).
Re:Resumes are dangerous? by tsukikage on Monday April 25, 2022 @05:44AM (#31152327)
+1. Additionally, in general, I personally prefer to keep work and leisure separate. Things that I bring to the awareness of potential / future employers are selected and curated, and distinct from places where I keep the half-baked stuff I do for fun for my own consumption.

It's certainly possible to get from my real name to my leisure activities and vice versa with a concerted effort, but the first page or two of a casual Google search won't do it.

Re:Resumes are dangerous? by Aeolun on Monday April 25, 2022 @07:10AM (#31152919)
> it's useful to see the candidate's coding skills in advance

Yes, but only if it’s representative of their work. Good luck finding the one kind of sensible library I’ve written in the 100 forks and experiments.

Re:Resumes are dangerous? by lolinder on Monday April 25, 2022 @08:58AM (#31153805)
That's what pinned repositories are for. It's your opportunity to highlight the projects you're actually proud of. Any half-reasonable prospective employer will look at those first, and probably only those.

And again, if you have nothing worth pinning, there's always the option to leave it off your resume.

Re:Resumes are dangerous? by Cthulhu_ on Monday April 25, 2022 @05:37AM (#31152270)
I've googled people's names + github if their GH wasn't provided, just out of curiosity.