You should essentially never do syn/ack IRL. If you don't know precisely what the recipient is doing, you do not know what they are doing, it could be important. Always lead with info to help them prioritize things. Ideally in the first ~5 words, because that's all they may see in the notification.
(this is also IMO why phone calls are terrible. they're the equivalent of "hello" over a channel that has no other message, so everything must be assumed to be maximum urgency or you might miss something truly critical)
(I'm picking up kids)
Me, Mon 5pm: hey
(He's gone for the day)
Bob, Tue 9am: can you check the logs for xyz...
The number of times that this has happened, with certain colleagues of mine, over Slack. Ugh.
Dude, if you had just skipped the really-actually-not-required-on-slack pleasantries, I could have already given you the information you needed, 16 hours ago.
If someone just wants to send me an information, email is great for that.
My personal order of contacts is snail mail → email → IM → phone → in person. Each of the steps is one order of magnitude of urgency greater than the previous one.
There is probably also a cultural component.
“Hello, could we set a time to chat about xyz” lets the reader give a meaningful response when available (and maybe thats immediate)
I simply ignore hellos but happily respond to questions.
It's possible to be polite while being mindful of how many interrupts you are causing another person.
Good! If you went up to someone in person who is in flow state and say HELLO! you'll probably get a rude response too.
If I’m at work, I’m always going to be available to talk, and anyway, nothing is lost by them sending me what they want to say and me responding when I become available.
I’m of the opinion that you shouldn’t ever send messages that are unsafe for 200 of your colleagues to see.
Every other time when you don't need to know that, you can still not get all the problems of the empty "hello" message.
I almost always have time to fight fires — unless busy with a larger conflagration. I may or may not have the time to debate the finer points of table naming conventions however.
Without context I might say yes and then have to take it back once I discover the topic.
Hello without a context is ignored.
Hello with a context empowers me to make a decision about how my day will go.
A "hello" means it is "IM urgent" so it can wait for the moment I am OK to exchange.
Like I said, this is also cultural - some cultures allow people to interrupt others, some not.
Re: your messages in this thread
Dear BrandoElFollito:
You're rebuilding TCP over UDP. Chat apps are connectionless (or RESTful, if you will). What makes them productive, especially in the workplace, is the fact that they can work without all the handshaking that accompanies more structured communication like in-person, spoken human conversations.
Nothing is stopping you from adding back all your binds, listens, SYNs, and ACKs to a protocol that doesn't need them. But it's a conversational code smell if you do.
Sincerely yours,
sowbug
That is why hello is annoying. People are capable to talk immediately, but take forever to finish writing.
Sending Hello this way seems like calling somebody and if they answer it's ok to interrupt.
Being responsive doesn't mean you're idle.
If this is to say something minor I will block that person, or never pick up their call again.
“Hey I’m blocked on xyz, thanks anyways how was your weekend?”
Is far more pleasant than
“Hey how’s the weekend? anyway I’m blocked on xyz”
In async communication it's unnecessary though, people might do it by inertia.
TCP RST
It was such a dead end for getting things done (he was productive on his things, but blocker for everybody else.
It was a weird hill to die on.
If that wasn’t desired, the greeting would be more like “Good day” or “Hello”.
How difficult would it be to design a mechanism that facilitates humans being nice to each other, rather than making humans emulate emotionless robots?
That way you'd only be pulled into the conversation once there's actionable information.
12.00 - Hello
12.01 - Hello, what's up?
12.02 - (long text explanation with some urgent changes)
(you just returned from another urgent 3-hours meeting)
14.40 - sorry, just read your message?
Something that happened recently or something that you heard about or something you remembered or something you are looking forward to, just... anything.
I'm playing with LEGO®.
I'm eating sushi. You?
I'm in spaaaaaaceeeee but I'm separated from my module!!! Halp!
Huh. I’m glad this is not a thing in my circles. Being direct and exposing some vulnerability seems to work great for us.
I known its just a custom that can’t be analyzed too deeply, but what you describe sounds so timid and shy from the outside.
Rightly or wrongly (probably wrongly), if I picked up that someone was doing this, I’d assume they need a lot of special handling and ceremony to feel comfortable. It would take a lot for me to want to bother.
Maybe in the United States, but I would hardly call it universal.
Like he's swinging a club at you. The only reply is to raise your shield.
Or you could do something clever. But either way your attention has been lassoed.
Gotta be cleverer.
Yes. And I find myself using this pattern when I want to talk (heck, I started the conversation, so I have something in my mind), but I’m not sure if it’s a convenient time.
If my asking “What’s up” unlocks a conversation, then maybe it’s not a good time to talk about what I was thinking.
Honestly, I've had a hard time turning these into interesting discussions. It amounts to, "no time to really reflect. Here are my mundane joys and traumas. Okay, back to the pressing issues at hand..."
> “What’s up?” is one of the most dreadful texts to get; it’s short for “Hello, I’d like you to entertain me now.”
The typical response to "What's up?" from myself and, uh, nearly everyone I know, is some variation on
"Not much! What's up with you?" or
"[trivial recent happening, quickly related] So, what's been going on with you?"
...and that's because "What's up?" is nearly universally a way to prompt someone to ask you that question back, so you can tell them about the thing you really want to say without it seeming sudden or forced.