News for hackers. Stuff that matters.
Re:How to embrace asynchronous communication for remote work by digging on Friday March 15, 2024 @06:05PM (#39721191)
I've had almost the exact situation at my work. I eventually even put nohello.net in my status message and forced it to show up whenever someone messages me (which felt rude! but important). Wrote up a pros/cons document of async standup which referenced many of the benefits of properly practiced async communication, with the implication that we could adopt those principles in our regular communications.

I still get a "Hi" at least once a week. I've completely stopped responding to those. The cycle of grueling standups growing longer week by week until some form of reorganization cuts them back down continues.

If leadership says they're remote-first but doesn't understand the practice of async communication, I don't believe a job at that org can be good.

Re:How to embrace asynchronous communication for remote work by laserlight on Saturday March 16, 2024 @02:11AM (#39723740)
> I still get a "Hi" at least once a week. I've completely stopped responding to those.

A funny behavior I observed from those only-“Hi” people is that they will write their request after they don't get a response for a long-enough time.

Re:How to embrace asynchronous communication for remote work by pizzafeelsright on Saturday March 16, 2024 @12:03PM (#39727051)
"If I am available or not, please include your request in future messages so that I may fully respond in the event you're also not available"

Hi, bye, and thank you are implied. No need to say them in the course of business.