Live data from Hacker News

Collaborate with kindness: Etiquette tips in Slack

slack.com

121–124 of 124 posts

Re: Collaborate with kindness: Etiquette tips in Slack

#121
post #34

Being polite and cooperative it's a good thing, self-censorship is not and the least one who can write an "etiquette" is a proprietary platform. Sorry that's just a pathetic bland and casual push toward Chinese social score homogenization. Usenet netiquette, mail netiquette etc are not wrote by someone up front but slowly formed by a community of users out of their experience. My own personal etiquette for Slack is:…

You must be fun to work with. Slack and similar are just tools. Caring about whether they are proprietary or not is lower down on the stack of priorities for most of us.

Re: Collaborate with kindness: Etiquette tips in Slack

#122
post #34

Being polite and cooperative it's a good thing, self-censorship is not and the least one who can write an "etiquette" is a proprietary platform. Sorry that's just a pathetic bland and casual push toward Chinese social score homogenization. Usenet netiquette, mail netiquette etc are not wrote by someone up front but slowly formed by a community of users out of their experience. My own personal etiquette for Slack is:…

You must be fun to work with. Slack and similar are just tools. Caring about whether they are proprietary or not is lower down on the stack of priorities for most of us.

Anything is just a tool, some are good tools, some (self/imposed)torture tools, some are just crappy tools pushed by ignorance that makes anything hard and inefficient, some are security threats etc.

Personally I consider a third-party propritary digital communication tool a security threat on it's own, since the third party might audit anything and I can't tell if that's happen or not, that's why I classify similarly Slack, Zoom, Meet, Teams, O365 etc.

I consider chat-based coms something useful in another era, when we can't just make VoIP calls, or still useful if you need to reach a remote ship or submarine via very expensive and limited sat/LF coms (classic telex), definitely wrong otherwise.

My coms are simple: you need to reach me quickly? Call me, classic SIP/RTP. It's not urgent? Send me a mail, a plain text one with a romance quoted multiple times or a signature longer then the message itself. Try to be "more connected" means trying to be distracted and less productive.

Need to send me files? I hope any company do have a decent DMS also for file sharing purposes.

Need to share the screen? Ok, call me and we do

etc.

Right tool for the right job. About working with me practically: for most who know me it's not an issue, and my productivity tend to be far above the average, for newcomers seems not hyper-nice to start, but it's a short time period.

Re: Collaborate with kindness: Etiquette tips in Slack

#123

Earlier quoted context omitted.

People have to prioritize their time. If they get messages from someone, they have to weigh responding to it against all of the other things they may be doing with their time (other messages, that ticket you’re working on, etc etc.) By just saying “Hey”, you’re leaving a message of unknown priority . You’re giving the other party zero information as to what you might want. If you say that to me, you’re saying “I need…

I dont think it is a problem with saying "hey" but when you say "hey" by itself. All the time I will say something like "hey" and then a followup message with a short question or asking how they are doing, etc etc. But for sure it is annoying when someone sends me a message that says "Hi" and then says nothing else until I respond

The person you're sending a message to doesn't need to sit there and watch you type out your actual message.

Just put "Hey" at the beginning your message. Don't split your message up into a separate message for "Hey" and a separate message for your real message.

Post reply on HN