Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

I get the point. You want a quick answer, then ask the question directly.

I dont think the rule can be applied universally.

1) Cultural norms - This may not work in all environments

2) You have an issue which requires cross function help. Hard to frame a precise question when you dont know which features are the most significant.



> 1) Cultural norms - This may not work in all environments

If you have the luxury to pick and choose, going to a company where that works is a huge improvement at large.

In my personal experience at least, I've seen no place where the "let me quick call you" is a norm and engineering is also decently respected and paid appropriately.

> 2) You have an issue which requires cross function help. Hard to frame a precise question when you don't know which features are the most significant.

You'll need more investigation either way, I'm not even sure you'll be able to properly decide who should be part of the meeting. The whole "who should I talk to" can be potentially be done better by chat, where you ask a whole group at once who's concerned by your problem and further narrow down as you get pointers.

Messaging a whole channel at once will probably be better accepted than inviting random people at a meeting to realize none of them were concerned.


It would be strange if you used a nail to hit a hammer. There is a degree of picking and choosing the right tool for the right job.

> I've seen no place where the "let me quick call you"

You haven't seen places where people say "Hi?", especially in the context of remote work?

>...decide who should be part of the meeting

This would be where "could we have a call?" matters,

As said first, words used with purpose provide a specific utility.

Nor did I mention messaging a whole channel? Whatever the situation you are envisioning, it is of your own experience that looks to be bleeding in.


> You haven't seen places where people say "Hi?", especially in the context of remote work?

The whole bit from the article:

> > You started a conversation by writing "Hi", or "Hello", or even maybe "Good morning Sebastian, I have a question". And then you waited. And waited. And waited for minutes (or hours if I was busy and you were patient) without a single word explaining what problem you were facing.

Yes, I've seen this in places, many places. Most times the person doing it immediately got guidance to stop doing it.

The only place where it persisted was a small shop where the founder and managers would also be doing it, and the technical team was leaking away at a speed I couldn't check for very long, as I was out pretty fast too. That could be one of the most clear sign they don't give a damn about online communication and won't care to adapt.

>...decide who should be part of the meeting

TBH I'm not sure to understand your answer. Of course I'm talking from my own experience, how could I speak for you ? Also, calls are costly, using them to understand who you're actually supposed to call feels wasteful. That can be done completely asynchronously in most cases.


> Of course I'm talking from my own experience,

1) that experience, is already captured in the article.

2) I am presenting specific, different scenarios where the derived advice does not hold.

You are reiterating point 1.

I do not see any new information being added. Perhaps you can specify what is the new insight, or refinement, in your information.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: