this post was submitted on 18 Nov 2024
6 points (100.0% liked)

Ask Experienced Devs

1232 readers
4 users here now

Icon base by Delapouite under CC BY 3.0 with modifications to add a gradient

founded 1 year ago
MODERATORS
 

For context, "no hello website" is a term I'm using to describe websites like https://nohello.com. The gist is that it's trying to get people to no only say "hello" but also ask whatever it is they're trying to ask you about. (In my opinion, this can even extend to generic conversations, like "hey, how are you?" versus just "hey!")

The problem is, many of these websites seem pretty rude. At the end of the day, I don't think it's possible to make one not seem at least a little rude because telling someone not to say hello just sounds rude lol. That said, even my favorite one (https://nohello.club/) has phrases like

  1. Unnecessary pleasantries
  2. useless phrase like "Hello"

But I like it because it doesn't say things like this that the original http://nohello.com says

please be prepared to be ignored if you only say "Hello!".

Some context, I'm not necessarily looking to include this on any corporate messaging app bio (unless it was 100% polite, which as I said I don't find possible). But the closer to something that polite, the more useful I think it is.

you are viewing a single comment's thread
view the rest of the comments
[–] BatmanAoD 2 points 12 hours ago

I think it does make sense to make sure there's something substantive in the very first message, even if it's not a complete description of the problem or a concrete request for help.

And the message with my problem tends to be longer and take me more time to type, so there is a delay between "Hi" and the actual issue.

That makes perfect sense, and I see why the habit became so commonplace; but that's exactly why this is annoying to anyone who is highly responsive on a messaging app, especially if responding to requests for help is part of their professional work. They pay attention to their notifications, so the notifications are probably configured to be noisy. Checking a notification before it's actionable is a waste of their time, albeit a small one.

Plus, if you force yourself to start typing out the problem before hitting "send", you'll often understand the problem better by the time you finish typing. This doesn't generally mean that you will have solved the problem yourself (though of course that sometimes happens), but it does mean you'll have more context you can provide as part of the request. And sometimes, you'll think of something you want to check or investigate before sending the request for help, in which case you'll be glad you haven't sent a ping yet.

Finally, you can still split up your messages after typing them all out. Just "cut" all but what you want to send in the first message, send, paste, and repeat.