131–140 of 256 posts
Earlier quoted context omitted.
This section should be required reading to get on the internet http://www.catb.org/~esr/faqs/smart-questions.html#not_losin...
The scenario described there would be considered harassment under modern Codes of Conduct. Describing the reaction as behaving like a "loser" is likely offensive itself.
I'm the original author of this content. I wrote it on the internal wiki at Google in 2007. Someone copied it and posted it at nohello.(something) after I left Google. It's made the front page of HN multiple times. 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 gro…
There's another reason for 'hello' ... it's a way to make sure you have the other person's attention before launching into a topic or question.
If you want my attention give me a reason to give it.
Earlier quoted context omitted.
The scenario described there would be considered harassment under modern Codes of Conduct. Describing the reaction as behaving like a "loser" is likely offensive itself.
While you're likely right in describing the status quo, it's unfortunate that it has come to that. The one thing that's really objectionable in that section is the last part about people who attack or flame without apparent reason. Such people should be called out by other community members in the same way ESR describes for newcomers in the first part of the section.
It's 2025, we should be able to use LLMs to adapt between communication styles. If someone I don't know "hello"s me, my LLM should detect that, suppress the notification, and reply automatically - and then resume notifications and defer to me once non-greeting conversation has started.
So, basically the classical annoying phone screen but for you coworkers? What's next - "press 1 for a question about FOO, press 2 for.." and level 1 AI support bots?
Earlier quoted context omitted.
There's another reason for 'hello' ... it's a way to make sure you have the other person's attention before launching into a topic or question.
That’s exactly what’s rude about it. Don’t make sure you have their attention. Just send the actual message. If it’s urgent enough that the actual message isn’t enough, “Hello” isn’t going to cut it either.
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 at her desk. Pretty obvious, but these two employees hate eachother and this is a sign of a bigger problem.
I'm the original author of this content. I wrote it on the internal wiki at Google in 2007. Someone copied it and posted it at nohello.(something) after I left Google. It's made the front page of HN multiple times. 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 gro…
There’s more than two groups. Some people are just being friendly, behavior which is hard to exhibit when you primarily (or only) interact with someone over chat. Yes, some people are just being nervous around potentially breaching etiquette in an ironic way that happens to be a different breach of etiquette (for some, at least) but I just respond with “hi” strictly because I am interested in getting on with the conv…
It'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 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.
They send their "Hi", and go do other stuff. You eventually respond with "hi", and they immediately reply with the request. At this point, they know you're around and saw their message - you just replied to their "hi". And you know they know, and also they know you know they know, which was the entire point.
They got to ask you the thing directly, so ignoring it now feel like walking away, which is rude.
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…
This is the problem I run into, I want to just reply to any "Hey" message with a link to this page, but then I'm the one being rude. We just need a better way to let other people know that this isn't a good way to do async chat. I've heard of other people making their status message this site, so then people see it when they go to message you and it doesn't have to be explicitly brought up
> If the worst they do to me is to say hello and never talk to me again, I'm ok with accommodating this in my daily workflow
This I can't really get behind, because if they just send a hello it's implied that I then need to follow-up and find out what they were asking about