News for hackers. Stuff that matters.
Re:Gitlab Handbook's HN Page by floatingatoll on Thursday January 20, 2022 @03:15AM (#30006193)
Hi, I think either I missed something or I see an insight that may not be in there yet, not sure if. In brief:

“Conveying without convincing.”

I think this guide is generally applicable to everyone interacting on HN, not just GitLab PRops, and while considering that I uncovered something I think would improve the value the guidelines.

Lots of online conversations get mired in back-and-forth persuasion, where each side is trying to convince the other of their viewpoint rather than just trying to convey it. This is essentially an impossible conversation to walk away from satisfied, because it’s rare that anyone can be convinced.

So, instead, focus on conveying. Ensure the facts are made clear and point out disagreements. Share your motivations and reasoning. Ask people to clarify when they say something you don’t understand, or could parse multiple ways. Leave disagreement alone, and don’t press it to change into agreement.

This is the toughest thing for anyone to do in conversation (“someone is wrong in the internet” xkcd here), but it’s absolutely the most essential skill and I don’t see it clearly called out. (Maybe I missed it though, it’s late!)

So, I would love to see that concept applied in guideline form. Teaching people to ensure comprehension rather than convincing, and to move on if it isn’t getting through, is the ultimate win in online chat, and I encourage adding it the the guide.

Re:Gitlab Handbook's HN Page by john_cogs on Thursday January 20, 2022 @09:28AM (#30009314)
While we regularly discuss this as a team, it was not documented. You are right that it should be so I opened an MR (which also links back to and quotes your comment): https://gitlab.com/gitlab-com/www-gitlab-com/-/merge_request...

Thanks for the great feedback.