Live data from Hacker News

Please don't say just hello in chat (2013)

nohello.net

341–350 of 362 posts

Re: Please don't say just hello in chat (2013)

#341

Earlier quoted context omitted.

Yikes. Screw that noise, literally. Your messaging habit of sending each message fragment as a new notification is the most annoying. 5 messages to communicate one thought? You have no respect for other people or their attention and are so self centered that even at their explicit request you can’t use the shift key when hitting enter. You,re the type of communicator I’d have to look up Slack documentation to mute al…

Jeez, that's some vitriol and some ad hominem here. Calm down, would you ? > Your messaging habit of sending each message fragment as a new notification is the most annoying. 5 messages to communicate one thought? Not 5 messages to send one thought. 3 different messages (each message being one full sentence) to send three distinct points that led to a fourth message being a conclusion. > You have no respect for other…

[deleted]

Re: Please don't say just hello in chat (2013)

#342
post #293

Earlier quoted context omitted.

> it also exposes you to corporate risk if it in fact was a sensitive matter with urgency and it's deemed that the necessary communication attempts were made You're joking, right? I'll print your chat history of a single "hi" and that'll be all the evidence I need to clear my name. That print-out is going on my wall afterwards. You're funny.

> You're joking, right? I'll print your chat history of a single "hi" and that'll be all the evidence I need to clear my name. That print-out is going on my wall afterwards. You're funny. Counterpoint: > Director, HR. First interaction with this user. > 2:30: "Hey, this is a matter with urgency. Got a second?" > missed call at 2:33pm > 2:45: "Hey, I've reached out to your manager Taylor J. to resolve the matter."

Hey, you took my advice! You specified that the matter had urgency! Good job!

Re: Please don't say just hello in chat (2013)

#343
post #243

Earlier quoted context omitted.

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…

> No, the bullshit copout is showing that you are available when you are not, to give the illusion that you are working I think you're ascribing a bit too much intention to what most people just ignore as the default setting on an application. I've never once touched my slack status settings, and I leave a slack tab open in my browser while I work, so I assume it probably shows me as online all the time when I'm work…

I do pay attention to Slack status, but I always figure it as a negative indicator -> This guy is definitely offline. It is not a guarantee that the person on the other end is going to see my message instantly.

Re: Please don't say just hello in chat (2013)

#344

Different people have different communication styles. I have some co-workers who hate it when people do not say hello the first time I talk to them in a day. There are other who I can jump straight to the question even having not talked for months. And I have one coworker who will ignore your questions until you stop, say hello, and talk to them a bit about how things are going. Anyone who gets to know their coworker…

Just say "Hello, how do I do X?" and you are nice to both crowds.

Re: Please don't say just hello in chat (2013)

#345
post #313

Earlier quoted context omitted.

> Now, if Mike from Accounting wants to talk urgently, I may not be available because I have my own list of urgent things to tackle. I will try to carve out time and prioritize his request, but I am in no way committed to his personal sense of urgency. That's fine, and that's for you to decide. But Mike from Accounting may have a reason to withhold the details for a different channel or to mitigate against other pote…

I'm kind of surprised about how much pushback you're getting on this. If I was working in person, someone coming up to me and asking "do you have a sec?" would be a perfectly reasonable thing to do. Even if I worked in a private office, someone knocking on the door would deserve enough attention to explain their situation. I don't think I've ever worked at a place where I could get away with telling my colleagues "do…

People like to maintain control over their own time and attention; I totally get it. But you're right, I'm also surprised at the extremes to which people are taking it, going so far as to assume that ephemerality and confidentiality mean the conversation is somehow immoral or illegal.

That's the kind of argument law enforcement makes against the use of encryption. It's an interesting double standard on HN.

I work infosec. My frame of reference is different from many here. But there are many times where I:

• want to ensure a synchronous conversation about an urgent matter, and

• don't want someone forwarding a "quick blurb" ("Hey, eganist here. Got an urgent moment to talk about something unusual we're seeing with web service X?") and spreading workplace gossip about a security anomaly when the anomaly itself is still being investigated to determine whether it's an incident.

Re: Please don't say just hello in chat (2013)

#346
post #342

Earlier quoted context omitted.

> You're joking, right? I'll print your chat history of a single "hi" and that'll be all the evidence I need to clear my name. That print-out is going on my wall afterwards. You're funny. Counterpoint: > Director, HR. First interaction with this user. > 2:30: "Hey, this is a matter with urgency. Got a second?" > missed call at 2:33pm > 2:45: "Hey, I've reached out to your manager Taylor J. to resolve the matter."

Hey, you took my advice! You specified that the matter had urgency! Good job!

> Hey, you took my advice! You specified that the matter had urgency! Good job!

No, not at all. You requested a description of the topic. Urgency, whether explicit or implicit, is always there when someone requests a synchronous conversation.

Edit: as a reminder,

> If it's urgent then you should probably take a few seconds to explain why.

Sorry you misinterpreted. Urgency is not "Why," and my example mentioned urgency explicitly without "taking the time to explain why."

Gaslighting someone in a discussion makes me less inclined to communicate. Wish you the best.

Re: Please don't say just hello in chat (2013)

#347
post #342

Earlier quoted context omitted.

Hey, you took my advice! You specified that the matter had urgency! Good job!

> Hey, you took my advice! You specified that the matter had urgency! Good job! No, not at all. You requested a description of the topic. Urgency, whether explicit or implicit, is always there when someone requests a synchronous conversation. Edit: as a reminder, > If it's urgent then you should probably take a few seconds to explain why. Sorry you misinterpreted. Urgency is not "Why," and my example mentioned urgenc…

TFA is literally about people just saying "hi".

Re: Please don't say just hello in chat (2013)

#349

Earlier quoted context omitted.

you... never just say "hi" to people ?

Not on Slack, no.

for me it feels super rude, as in, "you're not a human I like to interact with, just a cog I need to turn to continue my job"

Re: Please don't say just hello in chat (2013)

#350

Earlier quoted context omitted.

A new one for me is that work email is filled with security audit emails. Slack so far is not. I’ll open up my email, see if any subject lines are important, I’ll then go directly to service and get info there. I basically never open actual work emails ever. So tired of gotcha security

Stuff like that should be dumped to a dedicated folder. Maybe with an autodelete for messages older than a week.

Email filters are an office superpower.
Post reply on HN