Live data from Hacker News

New GitHub Profile Badges Beta

github.blog

21–30 of 113 posts

Re: New GitHub Profile Badges Beta

#21
post #17

Can we please stop turning everything into a social media experience? Why the constant need for personal validation / ego gratification? It seems like almost every tool or platform these days needs a friends feature, bragging badges or other form of social validation.

To be fair, GitHub's original slogan was "Social Coding".

True, but why do people think they need validation to collaborate?

Re: New GitHub Profile Badges Beta

#22
I like this feature.

I understand that it's not for everyone, but I also feel like people here tend to forget that GitHub is a social coding/collaboration platform as well. If you didn't like these features, why are your projects on GitHub then? Plenty of other git solutions.

I see some comments worried about this feature being abused or misused in regards to "bad contributions" however those contributions would either just be rejected, as they should, or accepted by the maintainers which means the badges worked to begin with, promoting more open-source collaboration.

Re: New GitHub Profile Badges Beta

#24
post #21
post #17

Earlier quoted context omitted.

To be fair, GitHub's original slogan was "Social Coding".

True, but why do people think they need validation to collaborate?

Stackoverflow also has badges and it motivated me a lot to answer questions on the early days.

Re: New GitHub Profile Badges Beta

#26

One of the achievements is 'YOLO': 'merged without a review'. We really shouldn't be encouraging this.

It's not exactly as bad as it sounds, there's been a few times I have merged a PR from someone where I reviewed it, I just never went through the "Review this PR" -> "Approve PR" workflow that adds the meta data "joshmanders has approved this PR"

Re: New GitHub Profile Badges Beta

#28

One of the achievements is 'YOLO': 'merged without a review'. We really shouldn't be encouraging this.

More than likely, this is a red flag, not an achievement; or at least one would hope it is.

Only if you can't imagine working on a project by yourself...

Re: New GitHub Profile Badges Beta

#29

This is not stupid. It's not a waste of time. It doesn't matter if this leads to a proliferation of shit contributions. It doesn't matter if it encourages bad practices. It doesn't matter if you don't like it. It's smart. This is WHY Microsoft bought Github. Software is eating the world and Github is where most of the eating happens. There are many career paths that require you to live on Twitter or LinkedIn or whate…

Precisely. LinkedIn doesn't specialize in software, it's a glorified résumé database. We all know that résumés don't really tell you whether an engineer is going to do good work for you; if they did, the only purpose of engineering interviews would be for culture fit. At the same time, even if all of an engineer's contributions were fully in the open and linked to from their GitHub profile, it's all a bit too much for a hiring manager to parse per résumé that they receive.

Achievements is a way of distilling contributions down to the important questions that hiring managers have: just how senior is this person I'm interviewing anyway? If I hire this person to do cutting-edge work, are they the kind of person to interact with the community on pushing the state-of-the-art, or not?

Post reply on HN