211–220 of 257 posts
Earlier quoted context omitted.
Mandatory clap time sounds horrible haha. I guess it's nowhere as near as robotic as it sounds in reality
Nothing about it sounds mandatory to me. It sounds like their team/company culture values recognition and openly & sincerely engages it as part of their schedule.
I've thought about trying to start some movement, not sure how to spread the word, that each open source project on github should make a "thank you" issue and pin it as a place for people to say thank you. AFAIK It's frowned on to say thank you in issues but it also sucks to have projects with 100s or 1000s of stars/forks and not a single thank you what so ever. Medium has the "claps" but I think it would be even nic…
It always bothered me that Github uses “Issues” for the name of the discussion board, as if encountering problems is the only reason to engage in conversation with the author.
>Discussions is the space for your community to have conversations, ask questions and post answers without opening issues.
I’ve learned that when I have a positive thought about someone, it’s generally worth communicating it. If I think a coworker saved me on some project, I tell them. If my partner is making me feel warm and fuzzy, I tell her. If someone impresses me, I say so. I don’t think people express these things nearly as often as they feel them, and I expect that many of the positive things that do end up communicated have anoth…
Earlier quoted context omitted.
Absolutely. My current workplace is very good at the organic thankyou. I try my best to show gratitude where I can.
What could have caused you and the other one to not get any votes, at the previous workplace? I'm guessing it was not work performance or anything like that (The votes were publicly announced -- and also who had voted?)
I've thought about trying to start some movement, not sure how to spread the word, that each open source project on github should make a "thank you" issue and pin it as a place for people to say thank you. AFAIK It's frowned on to say thank you in issues but it also sucks to have projects with 100s or 1000s of stars/forks and not a single thank you what so ever. Medium has the "claps" but I think it would be even nic…
For projects that have gitter/slack/chat, I've jumped in and said thanks. I've also considered sending thanks through the email addresses provided in package control (although it seems a bit weird emailing strangers, especially when you're not explicitly seeking a response). Starring a repo is also an (admittedly small) way to show thanks. What are some other ways to reach out?
Some people are pointing out how rare it is for GitHubbers to express gratitude, but GitHub doesn't exactly encourage it. Doesn't it feel inappropriate to express gratitude as an "issue"? Maybe if there was a natural place for these messages they'd be sent more often. To the extent that there are affordances for it (stars, emojis) it is actually quite popular to praise good work on GitHub.
> Doesn't it feel inappropriate to express gratitude as an "issue"? Yes, because it is, but I'd dispute the claim that GitHub discourages it. If anything, the people who use GitHub are more willing/most likely to misuse bugtracker for not just support requests but also general discussion and comments like this. It seems like there's a (non) issue like this that gets linked at least once a month on HN. I click through…
Is there a better, more canonical way to leave positive feedback, other than opening a Github issue? For projects that have gitter/slack/chat, I've jumped in and said thanks. I've also considered sending thanks through the email addresses provided in package control (although it seems a bit weird emailing strangers, especially when you're not explicitly seeking a response). Starring a repo is also an (admittedly smal…
Earlier quoted context omitted.
On every retrospective session we do, every other week, there is an additional column called “stars” or “heros” and we add a note each there giving praises to someone else for something they did those two weeks. We then read them all out followed by a round of applause for each one of them. It brings great positivity to the team.
That sounds horrible to me. I’d much rather be in the background rather than getting effusive, mandatory public praise. Maybe I’m weird, but I’m not motivated by cupcakes, gold stars and clapping. If I do a good job, that’s just the minimum standard. If I do something worthy of clapping, then just remember that when it’s time to award annual RSUs and bonuses or when a special project comes up that needs leadership. T…
You think complimenting people is horrible, people should be publicly shamed, insulted and blamed for the failure of the team, and fancy yourself for a leadership role? Grief.
Instead, perhaps take the "if you're on time, you're late, being early is the minimum" self-satisfied chip off your shoulder and realise that blaming Bob for you being a doormat and working on the weekend is you being "a bit of a douche".
I’ve learned that when I have a positive thought about someone, it’s generally worth communicating it. If I think a coworker saved me on some project, I tell them. If my partner is making me feel warm and fuzzy, I tell her. If someone impresses me, I say so. I don’t think people express these things nearly as often as they feel them, and I expect that many of the positive things that do end up communicated have anoth…
I've started to do this on a regular, almost daily basis.
If I come across something that sparks joy or interest - usually something I find here, on HN - I reach out to the author and let them know with a personal email.
I also sometimes offer a free-forever-no-strings-attached rsync.net account on the off chance that they would find that useful.
In reality, the Venn diagram of "people who write things that spark joy to the founder of rsync.net" and "people who aren't already self-hosting their own solution " is small.
But once in a while it really makes someones day ...