Live data from Hacker News

Non-obvious remote work techniques

queue.acm.org

21–30 of 87 posts

Re: Non-obvious remote work techniques

#21
post #2

Does anyone have any suggestions on a platform to facilitate Tip #4: Idling in a Videoconference Room? Zoom is the obvious choice, but wonder if anyone has built something better for this use case?

My wife's ex colleagues built this - https://www.remotion.com/. It's more like always on room

Re: Non-obvious remote work techniques

#22
post #2

Does anyone have any suggestions on a platform to facilitate Tip #4: Idling in a Videoconference Room? Zoom is the obvious choice, but wonder if anyone has built something better for this use case?

There was this Show HN for watercooler.work a few months ago.

https://news.ycombinator.com/item?id=23434271

Re: Non-obvious remote work techniques

#24
post #9

#3 - Holy hell I hate it when someone sends me a message with just "Hi". Just tell me what you want!

It's easier to reply "sorry, busy right now" in response to "hi". Once they say what they want I feel more obliged to make time for them.

Can't really determine if I actually have time for something before I know what it is. And unfortunately, I don't have the luxury of just ignoring things I don't want to deal with.

Re: Non-obvious remote work techniques

#25
post #23

#5 - IMHO you just can’t emulate a physical social event, the biggest problem being that you cannot establish smaller groups which are natural in physical events.

Agree, but that’s better than nothing. I spent several months working with a remote team. I didn’t really know my teammates for six lonely months, they were just names in a screen, until we started scheduling social meetings. Of course it’s nothing like the real thing, but it helps.

Re: Non-obvious remote work techniques

#26
post #18

Earlier quoted context omitted.

So you want them to use the chat program like e-mail?

The article explains perfectly what the parent would want instead.

So an e-mail with the subject tomato incident and a link to a zoom?

Chat is for back and forth.

And to pretend that this "conversation preparation" somehow takes (and interrupts) a worthy chunk of your day is either laughable or pompous.

plus, didn't we agree that chat is async and thus this "conversation setup" never happens? I am forced to respond to "how are you" in real time?

async convo = UDP "convo setup" = TCP, and it doesn't happen

Re: Non-obvious remote work techniques

#27
post #9

#3 - Holy hell I hate it when someone sends me a message with just "Hi". Just tell me what you want!

So you want them to use the chat program like e-mail?

Um, yes?

Email WORKS JUST FINE. You know what else works fine? A PHONE.

I know that actually calling someone on the phone seems to be traumatic for anyone under 35, but hey.

If it's really important--call. If it's not that important--why am I being interrupted? Send me email.

Chat--all the expressiveness of text with the interruptiveness of a phone call.

Re: Non-obvious remote work techniques

#28
> Accurate Chat Status > In meatspace you don't walk up to someone's desk and just start talking.

This list seems to assume or suggest that chat should only be used for synchronous conversation... Are there reasons to avoid using chat asyncronously?

My assumption is that chat can be asynchronous, but I recognize many people don’t want to ask their question until I’m actively responding. I can imagine security concerns, like someone doesn’t want their question to be read by people near me or someone wandering by my desk while I’m away...

But, my status as to whether I can chat synchronously changes dozens of times per day, and I don’t particularly want to have to manually toggle my status when I’m on the phone or when I’m chatting with someone else, or when I’m in the middle of coding and prefer to answer your “quick question” later, since it will inevitably require a 10 minute conversation. Quick to ask is often not quick to answer.

Re: Non-obvious remote work techniques

#29
post #18

Earlier quoted context omitted.

The article explains perfectly what the parent would want instead.

So an e-mail with the subject tomato incident and a link to a zoom? Chat is for back and forth. And to pretend that this "conversation preparation" somehow takes (and interrupts) a worthy chunk of your day is either laughable or pompous. plus, didn't we agree that chat is async and thus this "conversation setup" never happens? I am forced to respond to "how are you" in real time? async convo = UDP "convo setup" = TCP…

> hi

...

...

...

>> hi what's up

...

...

...

...

> there's a bug, it does abc when you do xyz

...

...

...

> ok I fixed it

versus

> hi, there's a bug, it does abc when you do xyz

...

...

...

> ok I fixed it

pleasantries are fine, just include the point along with them

Re: Non-obvious remote work techniques

#30
post #27

Earlier quoted context omitted.

So you want them to use the chat program like e-mail?

Um, yes? Email WORKS JUST FINE . You know what else works fine? A PHONE . I know that actually calling someone on the phone seems to be traumatic for anyone under 35, but hey. If it's really important--call. If it's not that important--why am I being interrupted? Send me email. Chat--all the expressiveness of text with the interruptiveness of a phone call.

If something's broken or if someone needs some info/action to be unblocked, I want a notification. I'm less likely to check email for something time sensitive, but I sure as hell don't want 20 phone calls a day.
Post reply on HN