81–90 of 256 posts
My wife does not find this guidance helpful. But, when her mother started doing it to her she went off the rails, so there is some small consolation to be had there.
This 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…
>they start conversations and are interrupted It's not about interruption really, it's about a style of using chat apps that wastes peoples' attention and is easily avoided. > they receive hundreds of notifications okay, so this nohello thing is good advice to help reduce the noise.
they need to work on their time management.
> you're actually just making the other person wait Where is the problem? Just do what you did until the question pops up? It’s not a phone call, remember ?
This site is saying "don't poke people in the head and then wait for them to ask you why you did that before continuing. It's detrimental for this mode of communication."
It's like a protocol handshake, of course. Why transmit information until you've established that the connection works? Consider it a text modem :)
If people saying hello on a chat pisses you off, take it as a sign that you need a vacation. I bet when you're back from 2 weeks in the Bahamas, when someone pings you with an empty "hello", you'll reply with a nice "oh hey buddy, what's up?", rather than spending one week building a fancy website to post to HN people who already agree with you.
The discussions always split between the people who just want to get on with the conversation and the people who can't bring themselves to do that because they consider it unforgivably rude. The second group never seem to take the hint that the first interruption is an imposition in itself.
Earlier quoted context omitted.
> It’s a boomer tendency. wat. No, it isn't. I see it almost 100% from young people who live in India. And that probably isn't the right criteria either - it is probably different people within each organization. This is a cultural thing, not generational.
I am in no way qualified on this, but my assumption was that this comes from cultures that consider getting straight to business rude. So while I do find it annoying, I also try to be polite back and I certainly won't be putting some "No Hello" link. If it is a cultural thing and coming from a place of politeness, then I'll engage in a quick round of pleasantries. Once people are familiar, I've noticed this stops.
Earlier quoted context omitted.
They probably need handholding to go through the issue and aren't good at putting into words explicitly what their issue is. Especially nontechnical and nonprogrammer people have problems around structuring and breaking down an issue into explicit parts, with a clearly formulated goal and required inputs and expected outputs etc. Most people's problem-solving relies on a collaborative thinking process where short sen…
> They probably need handholding to go through the issue and aren't good at putting into words explicitly what their issue is. I expect that from students and children, sure. But professionals? > Especially nontechnical and nonprogrammer people have problems around structuring and breaking down an issue into explicit parts, with a clearly formulated goal and required inputs and expected outputs etc. Ah, they were fai…
But anyway, my main point was, simply sending them a link like this will be perceived as baffling and rude, and I doubt that it can have a positive causal effect because it's not merely that they don't know about this rule of how to write messages, but that they require handholding. You can ask why they got hired then, but sometimes people can be confident and charming and that's often enough especially in non-programming interviews, or there might be also other reasons.
My wife, god bless her, is really good with people. I try very hard to mimic her, but this multi-round interaction has completely permeated how she interacts over tech, even with tech. I cannot manage it. Her: "Alexa, add to shopping list". "OK, what should I add for you". "Peanut butter". "OK, peanut butter added, what else?". . Me: "Alexa add peanut butter to shopping list". "Peanut butter added". Some people are T…
See, if you had Siri you'd be forced into the first anyway: "Alexa add peanut butter to shopping list" "OK, what should list should I add to?" "shopping list" "Ok, what should I add for you" "Peanut butter" "Ok, playing Peanut Butter by the Royal Guardsmen on a HomePod you forgot you had"
Siri occasionally misunderstands the name of the item, or needs to ask who's speaking (when on the HomePod), or has trouble because the phone of the person asking has briefly dropped off the Wifi, but in the ~5 years we've had it, I can count on one hand the number of times adding has just failed with any pattern remotely like what you describe.
I see this more often when someone desires synchronous, multi-turn interaction, not simply "when is that thing starting again?". Things where they aren't exactly sure how to ask the question so they want to rely on you asking questions back and then together zeroing in on the solution of some issue.
Hmm you're actually selling we on why this can be useful. They are gaining information in the exchange, like how available you are, how willing to help etc.