Sometimes it's good to default to a comprehensive write-up if it will be useful for a long time to multiple people, but it can be a bit wasteful if you write up a thorough description of a relational schema and it turns out they just wanted to know why there was a particular index on a particular table.
Please don't say just hello in chat (2013)
201–210 of 362 posts
Re: Please don't say just hello in chat (2013)
#202Earlier quoted context omitted.
> If you can't play nicely on a team then maybe a different job is for you? This is a bullshit copout. It's a cultural issue if people cannot be respectful of their co-workers time. It is very common that if something is important to use important modes of communication such as phone calls. My team for example is very asynchronous because that is our culture. Our team is located all over the country and some people i…
No, the bullshit copout is showing that you are available when you are not, to give the illusion that you are working I have nothing but respect for my coworkers personal time. I couldn't care less, personally, if you need to take hours, days, weeks, or even months off of work for whatever reason. Do what you need to do. However, if you are on Slack and suggesting to people you are available when you are not, that is…
Re: Please don't say just hello in chat (2013)
#203Earlier quoted context omitted.
Could you please name at least one that would warrant a "naked greeting" like that though? "Production issue" comes to mind, but that would just as likely warrant a quick summary of the situation, since waiting for a response to "hi" wastes even more time.
Your boss has 10 reports and he needs to talk to all of them within an hour to tell some bad news face to face before it’s announced impersonally via email. I probably would be slightly more verbose saying “hey, got a sec?” but honestly it’s a style question and if I’m on the receiving end it’s not going to bother me. I find much of the discourse around slack etiquette to be slightly self-absorbed. The fact is, thing…
Re: Please don't say just hello in chat (2013)
#204* Other people looking at my screen. Common when working out designs, in person or remote
* I'm presenting my screen publicly and might have forgotten to turn off notifications
* I might be busy and want you to email me instead so that I'll get to your request on my own time
* I don't want you to think that I got your message if I haven't especially if it's set to be deleted on some timer
That said I recognize that some people who don't have these problems have a "nohello" preference. I generally advise people to make their preferences explicitly known without sounding like there's only "one true way" of doing business when it comes to communication modes (and to respect others' preferences).
Re: Please don't say just hello in chat (2013)
#205Re: Please don't say just hello in chat (2013)
#206>People who do this are generally trying to be polite by not jumping right into the request, like one would in person or on the phone - and that's great! Different people have different reasons but I notice that many people that do a naked "hi" / "hey" are trying to see if the receiver is present for an immediate reply. In other words, the sender deliberately wants a synchronous instead of asynchronous convo. They do…
I do that. And my main reason is not to have a synched conversation, but first to see it the recipient is responsive before I ask the question, usually, a tough question that the recipient might want to dodge or procrastinate. So if I ask everything at the same time, he might never answer, dodge it and say "sorry I didn't see your message". Basically, I use hello as a trap.
Re: Please don't say just hello in chat (2013)
#207>People who do this are generally trying to be polite by not jumping right into the request, like one would in person or on the phone - and that's great! Different people have different reasons but I notice that many people that do a naked "hi" / "hey" are trying to see if the receiver is present for an immediate reply. In other words, the sender deliberately wants a synchronous instead of asynchronous convo. They do…
Alternatively, if you're not busy, respond but steer the conversation to topics like the weather.
Re: Please don't say just hello in chat (2013)
#208People asking to ask really pisses geeks off (me included). This was one of the first things that made me realise that I'm very similar to a very small number of other fellow geeks, and very different from most people. Most people think they're being polite by asking to ask. We think they're being rude by wasting our time on such pointless pleasantries.
I like that this page uses The Office for its examples. I don't think it will do any good, though. People either get why you don't ask to ask, or they don't. And some people don't value their time (let alone your time) as highly as you value yours.
Re: Please don't say just hello in chat (2013)
#209>People who do this are generally trying to be polite by not jumping right into the request, like one would in person or on the phone - and that's great! Different people have different reasons but I notice that many people that do a naked "hi" / "hey" are trying to see if the receiver is present for an immediate reply. In other words, the sender deliberately wants a synchronous instead of asynchronous convo. They do…
Re: Please don't say just hello in chat (2013)
#210Earlier quoted context omitted.
For immediate replies I’d usually use “you there?” or “free for a quick chat?”. The naked greeting is just begging to get ignored.
The linked page advocates against these on the same premise, which is my primary challenge with it. It ignores urgency.