YOLO

[Belikeoscar]

I feel having the yolo badge does not pass the right message especially to recruiters. Reasons for having one could vary, like having to work on friendly projects that wouldn't require reviews.

[danielepiccone]

I don't understand why this is even an achievement, it has a negative connotation, and specially irrelevant for private projects.

[DevCleverton]

[fritzmg]

Besides that you have also the option to hide badges

But that would hide all the badges. This discussion is about the YOLO badge and its negative connotation.

[strom2357]

This response -- "recruiters won't care" -- felt really dismissive. Why not acknowledge OP's valid and shared concern about sending the right message on a professional profile?

[7iliama1]

👍🏼

[sampi]

sometimes you merge something but you still want the "paper trail" or perhaps it will be reviewed asynchronously the next morning.

[Belikeoscar]

that too, I just hope it doesn't become a basis of judgement by people.

[Pavel8913]

Alright

[floer32]

This badge especially shouldn't show up when it's about a private repository, or your own repository with no other contributors. But especially private repositories; it doesn't even make sense in that case.

[MichaelWheldon]

Oh hey, another completely stupid, bloated and distracting social feature on github. Just because badges and the gamification of the internet didn’t pan out a decade ago, why not try again?!

[ThomasThelen]

Did you forget that GitHub has been a social coding platform from the beginning?

[stratigos]

We havent forgotten that GitHub used to be logical and reasonable.

[sthagen]

The criteria of that badge seem useless, as peer reviews not executed by peers in an agreed time window often are a valid process implementation. So, this badge takes all other badges down with it (as I understand I can only decide for all to show or not, right)?

(Always wanted to end the text of an "answer" on a social media site with a question mark ...)

❔

[Belikeoscar]

We can honestly do without the Yolo, don't you think so?
(😏 ? )

[fritzmg]

I agree that this badge should be removed, as it conveys a negative connotation about something that can be completely valid and normal.

[VictorHugoAguilar]

It depends on the recruiter, but the difficult thing is to get it

[sthagen]

No. That wun is easy to get on GitHub.

[Kyle772]

I agree that it's not a very good badge. Why would I want other developers to think I merge without reviews?

[ThomasThelen]

GitHub is a social programming platform - you don't have to use it specifically for work or serious projects where there are strict standards in place. At the end of the day, judging a developer by gamification badges is probably not the best way to assess skill or quality.

[7iliama1]

agree 👍🏼

[sthagen]

Also, many pull requests I participate in are not at all about software development but instead say represent drafts of meeting minutes, or examples for specifications, ...

[nragland37]

If you're having doubts and don't want to hide all your badges. Simply, click on the specific badge in your profile that you'd like to hide.

nragland37.Nicholas.Ragland.-.Google.Chrome.2022-10-10.13-56-18.mp4

[stratigos]

Thank you for showing this - this comment was buried for me when I first viewed the page, I had to expand comments to see it.

[jdevfullstack]

latest update, you can now pick what you want to hide, unlike in the past, it was all or nothing

go to Achievements Tab, click the Achievements word, it is a link

or this URL, it's same thing

https://github.com/[username]?tab=achievements

you should be seeing like this

then, click any badge, hover left then you should be seeing like this

then boom ... you now have the option to hide those badges that you want to hide

[julienheinen]

ohhhhhh it's beautiful

[KeplerDE]

Super

[julienheinen]

I've been trying to get it for about 1 hour. It's much more annoying than trying to fix an unsolvable error in a program.

[stratigos]

I agree that the YOLO badge is not at all something positive. It represents an antipattern. I in no way shape or form want to be associated with the YOLO badge or what it means. Sometimes I have repositories for which I am the only maintainer, and therefore, I am the only one who can merge a PR. This is not a "YOLO" event, its intentional in that case, and in no way shape or form represents my values or how I would work on a team. I strongly advocate for peer review, and take peer review process very seriously.

I like my other badges, I want YOLO removed from my profile. Essentially, I want to be able to pick and choose which badges display, given that this and potentially others are antipatterns and not bragworthy at all.

If anything, remove YOLO, its a badge for the sake of having a badge, and does not represent any sort of positive action.

The recruiter remark is irrelevant. I do not interact with recruiters. I am not at all interested in what a recruiter thinks of my GitHub profile. I would instead prefer to reflect my values as an engineer to other engineers with my GitHub profile.

[stratigos]

After expanding the comments - which wasnt immediately clear to me when I first arrived on the page - I have learned how to hide a single, specific badge.

I still think its an illogical choice, and this is a platform for engineers. Remove the YOLO badge entirely, its in no way shape or form a positive value!

[lahirusamishka]

The YOLO badge is an important indicator of a developer's behavior. While it may suggest practices like merging code without a proper review, it also offers insights into their habits. Allowing the badge to change dynamically could be beneficial.

For example, developers who engage in negative practices could receive "bad badges" as feedback. This would encourage them to prioritize best practices to improve their badges over time. As they address these areas, they could work toward earning "good badges" that reflect positive development behaviors.