Slack Etiquettes

Slack Etiquettes:
	- know when to DM and when to use channel messages. 
		- No need to put a DM message in a channel unless others require visibility.
	- tag required folks. e.g. @here/ @channel / @xyzLoginId to get their attention.
		- e.g. `@here @x @y what's with this domain specific thing. FYI/cc: @a, @b, @c`
	- use threads for replies. Don't pollute the channel conversations with inline replies.
        - Sometimes the messages get lost in pile of replies, that's where threads :thread: help to organize attention span.
		- One catch though: unless you tag a person in the main message or thread, they won't receive notification replies for thread messages. use @here / @xyzLoginId to notify them of new replies in the thread.
	- Since slack doesn't have read receipts, maximize use of emojis. Sometimes it's human equivalent of a smile. e.g. Looking-👀, done-✅, :yes:, :no:, :joy: 
	- create different channels for different domains/areas. e.g. backend-<team>, ui-<team>, <big-feature-x>-<team>, product-<team>. 
        - This helps get the right attention from right folks. This also helps folks to prioritize their reading. i.e. just because I sent a message doesn't mean all receipients will read right away. 
	- STOP USING "Hi" messages. - https://nohello.net/
		- imagine below scenario
		- [10AM Doe]- Hi John,
		- [10.30AM - John opens slack as he was focused on another task]
		- [10.30 AM - John] - Hi Doe! how can I help?
		- [Congrats you just established a secure channel :( by spending/wasting 30 mins]
	- If you are a fan of joining multiple channels, group them in sections to organize your attention span.
	- Use workflows to automate manual work:
		- examples:
			- Use reminder for recurring activities like asking folks to send their standup updates, update metrics for next leadership sync, etc.
			- Asking cross team folks to update the agenda of a recurring meeting.
			- add welcome message with all the links for new-joinees. Yes you can do that too!
	- Allow your readers the time to respond. Use message when you can wait X duration for the reply. Use meetings when you can't wait. x=user defined.
	- Use async when you have small trivial stuff. Use ad-hoc-syncs / quick huddles (if possible) to quickly close brainstorming aspects. Don't spend 15 mins typing and explaining what can be done in a 5 mins of call.
	- Praise when possible. 🙌, 👍 We all need human touch in remote world.