5 ms·

It is pretty annoying when people pause like that. I don't see why they can't buffer their writes until they get a complete thought (Saying "hey", then typing t

It is pretty annoying when people pause like that. I don't see why they can't buffer their writes until they get a complete thought (Saying "hey", then typing the next message is the worst). It isn't fully asynchronous if notifications are enabled. With notifications, you are more like a single cpu server that has to handle hardware interrupts for disk/network io. It stops you from working and forces context switching, only people aren't as good at context switching.

jerf 5y ago
"Saying "hey", then typing the next message is the worst" Pro-tip if you're one of those: If you look at the slack interface, there's not a lot of visual difference between two messages in a row, and a single message separated by two newlines (SHIFT-Enter if you don't know how to enter those). It looks exactly the same to type "Hey.\n\nJust wanted to check up on the status of the de-fooification project. How's that going?" as it is to send those as two separate messages, it looks just as polite on the screen, and it's way less annoying.
- bostonpete 5y ago
  Not relevant for your "Hey" example but I often do submit successive thoughts as separate messages rather than one less disruptive message because it allows readers to add reactions/responses to the individual thoughts.
Emanation 5y ago
Ha. I do this. It's emotional energy. Lacking seriousness or im too preoccupied with how my reply will be understood or not. Granted, I dont think I ever stopped at 'hey-'
- cto_of_antifa 5y ago
  Yup. And tolerating coworkers who do it is just part of being an empathetic human who puts team communication as a priority without being needlessly hostile. I've worked with many developers like that, and no matter how great the code, dealing with them was always tedious as hell.
jacobsenscott 5y ago
Even worse is people who type "hey", and then don't type anything else until you "hey" back. Even worse is "Hey, I want to talk about something. I'll call you in 30 minutes."
- Cthulhu_ 5y ago
  I think it's perfectly acceptable to leave them 'on hold' until they actually write something. If they don't, then it wasn't anything important.
wruza 5y ago
Saying "hey", then typing the next message is the worst You don’t have colleagues who type “hey” and then wait for your reply, do you?
the_gipsy 5y ago
Someone should write a bot like the gp that autoreplies “hey, how is your day going so far?” to a single “hey” line.
vidarh 5y ago
> Saying "hey", then typing the next message is the worst "hey" [waits for a response; then a long pause and agonisingly slow typing after you've said hey back] "Can I ask you a question?" [waits for a response] [agonisingly slow typing coupled with intermittent pauses]. Always makes me want to yell at people to just ask their damn question.

jerf 5y ago

"Saying "hey", then typing the next message is the worst" Pro-tip if you're one of those: If you look at the slack interface, there's not a lot of visual difference between two messages in a row, and a single message separated by two newlines (SHIFT-Enter if you don't know how to enter those). It looks exactly the same to type "Hey.\n\nJust wanted to check up on the status of the de-fooification project. How's that going?" as it is to send those as two separate messages, it looks just as polite on the screen, and it's way less annoying.

bostonpete 5y ago
Not relevant for your "Hey" example but I often do submit successive thoughts as separate messages rather than one less disruptive message because it allows readers to add reactions/responses to the individual thoughts.

Emanation 5y ago

Ha. I do this. It's emotional energy. Lacking seriousness or im too preoccupied with how my reply will be understood or not. Granted, I dont think I ever stopped at 'hey-'

cto_of_antifa 5y ago
Yup. And tolerating coworkers who do it is just part of being an empathetic human who puts team communication as a priority without being needlessly hostile. I've worked with many developers like that, and no matter how great the code, dealing with them was always tedious as hell.

jacobsenscott 5y ago

Even worse is people who type "hey", and then don't type anything else until you "hey" back. Even worse is "Hey, I want to talk about something. I'll call you in 30 minutes."

Cthulhu_ 5y ago
I think it's perfectly acceptable to leave them 'on hold' until they actually write something. If they don't, then it wasn't anything important.

wruza 5y ago

Saying "hey", then typing the next message is the worst You don’t have colleagues who type “hey” and then wait for your reply, do you?

the_gipsy 5y ago

Someone should write a bot like the gp that autoreplies “hey, how is your day going so far?” to a single “hey” line.

vidarh 5y ago

> Saying "hey", then typing the next message is the worst "hey" [waits for a response; then a long pause and agonisingly slow typing after you've said hey back] "Can I ask you a question?" [waits for a response] [agonisingly slow typing coupled with intermittent pauses]. Always makes me want to yell at people to just ask their damn question.