Similarly, https://dontasktoask.com/
No Hello
191–200 of 256 posts
Re: No Hello
#192Hello was invented for phone conversations. It doesn't make sense if the conversation isn't verbal.
[deleted]
Re: No Hello
#193Earlier quoted context omitted.
Your wife is possibly wondering why you send everything cleartext in one single frame and don't do challenge-response or any sort of state machine resynchronization between client and server. (-:
My wife is probably wondering why I'm using her politeness as a joke on the internet
She can welcome the coming of our future robot overlords, as between you two they'll most likely spare her. :)
Re: No Hello
#194i get the initial frustration of not receiving additional context with a request for attention, but a few years ago, i realized that that was my problem to overcome, not everybody else who exhibits this very-common-and-not-at-all-intentionally-rude behavior.
Re: No Hello
#195It's funny to see this here. I manage a large team and just the other day had to deal with irate employees who are arguing over whether they should be saying "Good morning" to each other when they come into the office. One employee thinks it should almost be "mandatory" to greet each other, where the other employee says she isn't in the headspace to be greeting people early in the morning and would rather get settled…
i would hope my manager wouldnt see this as irate employeeS but rather one employee trying to be controlling by forcing another one to bark a response like a trained dog when they've made it clear what their boundaries are for early morning communications. allowing communication boundaries between employees is a pretty basic tenet of treating them with the respect humans deserve
I try to explain to the one employee that is fine to have the expectation that others say Good Morning, but it's also fine that the other employee doesn't want to engage that way. Both things can be true and right at the same time. She doesn't adjust her position and still thinks it's a requirement.
Re: No Hello
#196It's funny to see this here. I manage a large team and just the other day had to deal with irate employees who are arguing over whether they should be saying "Good morning" to each other when they come into the office. One employee thinks it should almost be "mandatory" to greet each other, where the other employee says she isn't in the headspace to be greeting people early in the morning and would rather get settled…
Quite frankly this sounds like something from The Office.
There are many things that basically could be a game of "True Situation vs Scene from The Office"
Re: No Hello
#197Arthur Clarke made this point in a story about high latency communication half a century or more ago. He made the point that one should simply keep talking rather than wait for questions and answers to ping pong back and forth. While one is providing an answer you can be asking the next question. I can't remember the name of the story though. The solution was expressed in slightly sexist terms: speak like to women having a telephone conversation exchanging news.
Re: No Hello
#198Yknow what? This doesn't bother me. I've had coworkers who do this. You just respond "hello!" and maybe they just ask their question, or maybe they ask about your day, or whatever else. God forbid I spend an extra 4 seconds per day thinking about a person I work with. Do "hello" messages waste time? Yes. Am I happy to field them anyway? Yes!
It's not about the time it takes to say "hello" back. It's about synchronization steps. What if I don't see the first message right away (i might not see the notification, or I was busy with something else, or I was AFK, etc etc)? Then I reply 20 minutes after with just a "hello" because I don't know what they wanted at all, so I can't reply with any information. Then they might take 20 minutes to respond because they aren't going to sit for an answer, etc etc.
It's a waste of interruptions. And for some types of work, like programming (we're in HN after all), interruptions can be more costly than just the "4 seconds" it takes to reply. Them saying "hello" and then without waiting for a reply explaining what they want in a short way, is more efficient and respectful of your time (and theirs, to be honest).
Re: No Hello
#199This is not the first time I see this here and to be honest, I was in total agreement a few years ago. In principle, I still am. Then I became a manager, I had to start dealing with more people, to navigate the enterprise environment and I understood that one of my strengths is to be understand people and to accommodate their ways of working. In this context, being hard with people that just say hello just doesn't ma…
> Then I became a manager So it bothered you when you had actual work to do, but once you moved to a position where everyone else was doing the actual work and you just sat around benefiting from their labor, you didn't mind minor interruptions and time wasters anymore? Shocking.
Being a manager is not benefiting from other people's work, is to try my best to eliminate barriers so they can do their best work. That includes making them comfortable in the work environment. When you reach a point where you work with many people from different backgrounds, you really have to learn to adapt to people and accommodate to their ways of working.
If that means that I don't get triggered when they leave me a "hi" and never come back, that's fine by me.
Re: No Hello
#200Earlier quoted context omitted.
That's only rude sometimes. We don't typically talk to other people in real life without confirming their attention (e.g. via eye contact) first.
That's because we're communicating synchronously in person. If you say something when I'm not listening to you, I will probably start listening midway through your statement, and miss potentially vital info. In a slack message, I can just read it again.
IDK about you but I get chats from 30+ different people and I usually miss at least one person's message a day as it falls off the "front page" so to speak