| I find a lot of this to be surprising. The author seems sharp, but is missing so many obvious issues with what they are saying. > It’s harder to get a hold of each other, as we’re not online at the same time. “I’ll talk about it when I see him tomorrow” — these delays compound in a huge way. What? What does working remotely have to do with people working different times during the day? Core hours should be a thing - regardless of it being remote of in the same building. > So most interactions are async, leading to lower bandwidth, more context switching, and more things falling through the cracks. I can't wrap my head around why async communication results in more context switching. You literally decide when you engage with async information. > Even sync chats aren’t as good. People can’t interrupt each other or have sidebars, and there are bugs with video, audio, screenshare, etc… These frictions compound too. Ah here we go. Bro culture coming into play. If you have to interrupt each other in order to have discussions something is off. > This causes us to be less aligned. We’re only a few engineers right now, and yet people feel out of the loop on who’s building what. Now we're on it. The problem isn't remote work. It's how you are handling work and the process. If you think the only way to solve this is to put people in the same room then you are destined to fail on how to build stuff. You are limited in your thinking on how to work as a team and are going to greatly reduce your ability to deal with variations unless it "totally aligns with how you know how to work." This pretty much explains it all right here. |