Remix.run Logo
▲ shagie 2 hours ago

> Not sure whether it was out of malice or done for some other reason. Maybe they were mistakenly thinking it is helpful?

I believe a fair bit of this is an attempt to gain numbers where quantifiable numbers are advertised on otherwise indistinguishable resumes (with the corresponding belief that those numbers make differences in filtering or hiring decisions).

I base that on having seen people in the days of old put their Stack Overflow reputation on resumes thinking that having a rep of 4321 will be more likely hired than someone with a rep of 1234.

Having "210 accepted PRs on GitHub" (they believe) would appear to make them a more productive / less risky hire than someone who hasn't done any.

---

This is really a case of indistinguishable resumes where nearly everyone in the pool went to the same college, same internships, same capstone project, and maybe the same first year or two of professional experience.

▲JDups an hour ago | parent [-]

There are job applications that list having a certain amount of contributions to github projects as a requirement. Encourages useless spam. Also funny the implication that only projects on github have any worth.

▲shagie an hour ago | parent [-]

That wouldn't surprise me in the slightest. I see it with applicants for a position that doesn't have GitHub contributions listed as either a requirement or a nice to have.

I could see it as a "proof of familiarity with CI and expectations for a PR", though for applicants that are spamming the process with poor PRs (and people posting poor Q&A on Stack Overflow back in the day), this often hurts them more than it helps as its a demonstration of what they are going to be doing if they are hired (I've already got too many poor quality PRs to review, your PRs would not reduce the amount of time that the reviewer would need to spend).