> Chances are you were sent here by someone within Slack, IRC or another chat after you’ve started the conversation just saying “Hello” or “Good Morning!” waiting for a response and now you’re curios what they tried to tell you with this link…
I understand what this is going for and I can see how it's likely useful, but surely there must be a less passive-aggressive way to convey this sentiment...
This site reminds me of people who respond to a question by posting a Let Me Google That For You (LMGTFY) link. Do they have a point? Yes. Are they also going about it in a passive-aggressive way that makes them seem like an ass? Also yes.
Writing "Hello" and nothing else has been one of my large pet peeves (similar to pinging the whole room for anything that's not prod urgent). I really dislike seeing the wasted time.
That said, I have not yet found a way to bring it up with the people that do it. I'm not sure if I sent this page to a person, that they'd read it.
I imagine the exchange going:
A 13:30> Hey
Me 13:45> Hey. Maybe it's better to ask right away, see no-hello.com for more info.
A 14:30> Ok?
A 14:31> So did you get ...
Cue next week when A has forgotten all about some silly no-hello page. I might try it and see though.
this seems to be the intended use case for the page, but imo a better way would be:
A > Hey
B > Hey, what do you need?
A > [blahblahblah]
B > Alright, sounds good.
A > Thanks
B > By the way, next time could you just ask me what you want up front? When you just say "hey," [continued explanation based on rhetoric from the page, without actually necessarily linking to the page itself]
there's all sorts of issues with online work communication, and this is most certainly one of them, but a seemingly-flippant, passive-aggressive response linking to an external site surely can't really help much, and might in fact be perceived as rude in itself? the page doesn't seem to address any of these greater communication issues, which seems like a missed opportunity.
I encountered a great many issues like this while working for an international remote web dev shop, and they definitely deserve more attention than we give them. for example, the newest hire after me was a Mexican guy who was really nice and great to work with, but when our team was tasked with working with another team to complete some tasks, the responses he got about the stuff he was working on from the other team were terse and highly critical, and, as he perceived it, very rude. I had to explain to him that the other team was extremely tight-knit and used to very terse, effective communication (involving direct, to-the-point criticism of each others' work) to get things done, and that nobody hated him or thought he was a bad programmer or anything. eventually he came around but for awhile there I could tell it was really tearing him up and making him feel unwelcome.
a bit of empathy in resolving these remote communication issues goes a long way.
9 comments
[ 2.8 ms ] story [ 33.4 ms ] threadI understand what this is going for and I can see how it's likely useful, but surely there must be a less passive-aggressive way to convey this sentiment...
That said, I have not yet found a way to bring it up with the people that do it. I'm not sure if I sent this page to a person, that they'd read it.
I imagine the exchange going:
A 13:30> Hey
Me 13:45> Hey. Maybe it's better to ask right away, see no-hello.com for more info.
A 14:30> Ok?
A 14:31> So did you get ...
Cue next week when A has forgotten all about some silly no-hello page. I might try it and see though.
A > Hey
B > Hey, what do you need?
A > [blahblahblah]
B > Alright, sounds good.
A > Thanks
B > By the way, next time could you just ask me what you want up front? When you just say "hey," [continued explanation based on rhetoric from the page, without actually necessarily linking to the page itself]
there's all sorts of issues with online work communication, and this is most certainly one of them, but a seemingly-flippant, passive-aggressive response linking to an external site surely can't really help much, and might in fact be perceived as rude in itself? the page doesn't seem to address any of these greater communication issues, which seems like a missed opportunity.
I encountered a great many issues like this while working for an international remote web dev shop, and they definitely deserve more attention than we give them. for example, the newest hire after me was a Mexican guy who was really nice and great to work with, but when our team was tasked with working with another team to complete some tasks, the responses he got about the stuff he was working on from the other team were terse and highly critical, and, as he perceived it, very rude. I had to explain to him that the other team was extremely tight-knit and used to very terse, effective communication (involving direct, to-the-point criticism of each others' work) to get things done, and that nobody hated him or thought he was a bad programmer or anything. eventually he came around but for awhile there I could tell it was really tearing him up and making him feel unwelcome.
a bit of empathy in resolving these remote communication issues goes a long way.
What's next? no-how-was-the-weekend.net?