4 ms·
"Remote is about getting things done asynchronously." Not necessarily. Consider a call center or help desk, or any form of customer service done remotely. Asyn
by Animats 5y ago
"Remote is about getting things done asynchronously."
Not necessarily. Consider a call center or help desk, or any form of customer service done remotely. Asynchronous and remote are different.
- jedberg 5y agoI think OPs point is that that is not remote work -- it is officeless work. They are trying to make a distinction between the two.
- lostcolony 5y agoRight, but development this is correct; if you're remote and require sync, you're not actually getting things done. Meetings are not the desired outcome; deployed, working code is. Communication is necessary, but not the output, and so to be effective you have to find ways to make that communication asynchronous wherever possible. It's fine to still have the -output- be synchronous (i.e., pairing), but don't confuse the default synchronous tasks (meetings) without output. Anyway, all of that is a red herring; don't just tell me you're remote, tell me if you're prioritizing asynchronous work or not. The places trying to recreate the office, just now remote, are not places I want to work at.
- site-packages1 5y agoI have worked at software companies where meetings were indeed the desired outcome, even if no one said that part out loud.
- lostcolony 5y agoYeah, I have too. Oftentimes for business stakeholders and leadership, that is the case, as it helps justify their existence ("I was so busy!"). Which presents, unfortunately, opportunities for useless devs to glom on; sit in meetings, do no work, collect a paycheck.
- JoeQuery 5y ago> Meetings are not the desired outcome; deployed, working code is Maybe if all you want to do is code. I get the sentiment. If you're working on a product, getting input from team members and stopping bad ideas from making their way to the hands of the "don't bother me with meetings, I only want to code" person is important.
- lostcolony 5y agoYou seem to have completely ignored my "Communication is necessary, but not the output". Put another way, meetings are the 'how', not the 'what'. The how is not a deliverable, and so can be changed so long as the 'what' stays the same. You can get input, collaborate, etc, in other ways that are not synchronous. We've all had that "this meeting could have been an email" experience. Make it an email. Start re-evaluating every meeting; any sort of unidirectional informational meeting can be offloaded onto a doc or recorded presentation just as efficiently. Bidirectional decisional meetings can often be done more effectively by writing up a problem statement, the various options, and a 'due' date for input. Allow people to read over it, comment, propose new suggestions, etc, then at that due date, hold a vote (can be done sync or async). Voila, a decision is reached that allowed for greater amounts of discussion, and was arrived at as democratically or 'loudest voice in the room' (if only a select few people's votes count) as you care to have it, rather than whatever organically happens in your meetings. Etc. In my experience what I'm left with are the meetings where it's the 'personal connection' that matters; these are things like the occasional AMA/Town Hall style meetings, and 1-on-1s. 90% of my pre-COVID meetings turned out not to need to be meetings.
- JoeQuery 5y agoI didn't ignore anything. The product is the output. Code is not the output. Your code is as much the output as communication is. Users don't care if you spent your time coding or in a meeting. They care if the product fulfills their needs. A meeting that stops a terrible redesign contributes as much the output as the heads down programmer who would have implemented it. Now I would hate to be in meetings all day, don't get me wrong. But I disagree that code is the output specifically for a product.
- Draiken 5y agoTrue. Someone else pointed out that some call it async work instead. I've never heard companies say they're async though, only remote. The two seem to be conflated most of the time.
- madeofpalk 5y agoMost companies are just not async. That’s really hard to do I think!
- jacquesm 5y agoIt's the difference between using mostly meetings (real or virtual), IM and phone calls versus using mostly email. If you use mostly email for your comms it is perfectly possible to be both remote and async.
- ghaff 5y agoMost large companies are some combination of async and sync. If you have offices in the US and offices in Europe--much less Asia--you may have some hopefully not too inconvenient real-time calls. But you'll probably do a lot of things asynchronously. (And even within an office or within a country, a lot of people travel, have customer meetings, etc. so they're often just not immediately available.
- mgerdts 5y agoOr software engineers. I've been working remotely for about 12 years with teams spread around the globe. In the decade or so before that I worked in various offices with coworkers scattered around the globe. Async issues related to timezones or personal preferences are in no way unique to remote working. Remote working is about location, not about time. Over this past couple of decades, the only times that I have felt the need to announce my absence from the keyboard are when it is something out of the ordinary and unexpected. I never announce to the world that I am eating lunch, nor do I feel obligated to respond to IMs or other interruptions during any time that shows busy or out-of-office on my calendar. Just like when I was in the office, if I need to step away from an active conversation for a few minutes for whatever reason, I'll let people know I need to step away and the estimated time of my return.