Timeline for Slack culture in fully remote workplace - send "Hello" before asking a question?
Current License: CC BY-SA 4.0
8 events
when toggle format | what | by | license | comment | |
---|---|---|---|---|---|
Feb 23, 2023 at 10:30 | comment | added | Greenonline | I may be wrong but I feel as if the crux of this answer is the cut and paste aspect, which avoids the "SrEngineer is typing..." message, which can incur an irritating (especially when you are busy) delay. Even though I agree with the "This could be sent as one message (with or without line breaks)" comments, maybe you could edit your answer to emphasise that the cut and paste avoids the recipient having to see the annoying "X is typing..." message. | |
Feb 21, 2023 at 18:37 | comment | added | David S | I would caution that sending multiple messages at once is frequently interpreted as an increase in priority by the receiver. | |
Feb 21, 2023 at 12:50 | comment | added | Volker Siegel | @PaŭloEbermann I think sending it in a separate message is a significant difference. | |
Feb 21, 2023 at 12:18 | comment | added | NotThatGuy | Don't send it in 2 (or more) separate messages, period (unless you cut-and-paste it, but this is unnecessary). It can be quite irritating to open the app after getting a notification, but then still have to wait for some actionable message to appear (or getting multiple notifications when busy with something). FYI: you can add line breaks within the same message in pretty much every IM app (Shift+Enter or Ctrl+Enter are common shortcuts for this), so separate messages doesn't even really have the advantage of looking pretty. | |
Feb 21, 2023 at 1:11 | comment | added | Paŭlo Ebermann | You can also just send both in the same message, no need to make it two. | |
Feb 20, 2023 at 21:33 | history | edited | A-B Problem | CC BY-SA 4.0 |
Clarified resoning.
|
S Feb 20, 2023 at 21:32 | review | First answers | |||
Feb 20, 2023 at 22:32 | |||||
S Feb 20, 2023 at 21:32 | history | answered | A-B Problem | CC BY-SA 4.0 |