This sounds great for experienced engineers, but in my experience junior workers often require bite-sized guidance in order to avoid going down rabbit holes. A 10 second conversation could easily save hours of head-banging-into-wall type work for a junior SWE (not even exaggerating). Accordingly, during the pandemic I think it was mostly the less experienced engineers suffering from low productivity and lack of confi…
Remote work requires communicating more, but less frequently
151–160 of 326 posts
Re: Remote work requires communicating more, but less frequently
#152This sounds great for experienced engineers, but in my experience junior workers often require bite-sized guidance in order to avoid going down rabbit holes. A 10 second conversation could easily save hours of head-banging-into-wall type work for a junior SWE (not even exaggerating). Accordingly, during the pandemic I think it was mostly the less experienced engineers suffering from low productivity and lack of confi…
People still ping me frequently for a "quick chat" which is rarely quick, tho.
Re: Remote work requires communicating more, but less frequently
#153Earlier quoted context omitted.
Async communication is not even remotely close to socializing, and hardly feels like genuine human interaction.
Work != socializing. Quality work requires deep concentration over long stretches of time, not tapping on a shoulder at random intervals. Both IRL and virtually.
"Just socialize outside of work!" seems to be everyone's go-to response, totally missing how much time is taken up by the 8+ hours of the workday, and how much ambient socialization has been lost with that time now spent remote.
Sure, remote is more convenient for "deep work", but I honestly never had issues with that in-office: If I had my headphones on, people didn't bother me. If I had questions, I'd take them off and look around to see if anyone else was "surfaced" to talk to, or ping someone on slack. In the meantime I could kill time chatting with my team or going for a walk around the building--when I would inevitably find someone else from another team who was taking a break, and I could either ask them or just chat.
Now it's just me, in my apartment, all day, except for maybe standup. The only reliable face-to-face human interaction I have is my partner when they come home from work--and they're usually exhausted and ready to go to bed in an hour.
Work absolutely used to be a significant portion of socialization--just like going to classes used to be, in college or secondary school. We've absolutely lost that.
Re: Remote work requires communicating more, but less frequently
#154Earlier quoted context omitted.
Oh.. The poor juniors. Instead of properly adapting the onboarding and mentoring to the remote setting let's romanticize the good old ways that imho sucked. Let's cherrypick and pretend everything is fine. We went from offices to cubicles to open space and nobody stopped to think if it was a good idea. Wr transformed the office from a place where work actually is done to a placr where we "socialize". Work? Do that on…
> Instead of properly adapting the onboarding and mentoring But... how? Remote check-ins with juniors every 30-60 minutes? That's crazy. But that's basically the only way to replicate the in person experience. The best mentoring results for me as the mentee and for me as a mentor have been when we're sitting next to each other. The mentor can visually tell when the mentee is stuck, and mentee can tell when the mentor…
We've used day long zoom windows or slack huddles. Keep muted until you want to say something. Slack is the same thing, just send a message.
Re: Remote work requires communicating more, but less frequently
#155> Remote work requires communicating more, less frequently, because asynchronous communication involves less frequent, but richer communication, meaning there is less time talking about the work and more time doing it, allowing the system to optimize for throughput and flow. This whole thing seems to be what people struggle with about remote work. Communication is way, way more important, and being an effective commu…
Re: Remote work requires communicating more, but less frequently
#156Another (unrelated) problem with Remote work is how harder is to lose weight when you stop moving throughout the day. Before the pandemic, I usually got up to make coffee, to ask for help or to make consensus with my fellow coworkers (other devs or even UX people, a few stairs away). I usually walked from work from time to time to clear up my mind. Now I barely move. I live in a small apartment. The fridge is 3 meter…
This is just a description of your lack of discipline. Since the pandemic, I lost a significant amount of weight and increased my fitness across all other parameters as well. This is because remote work facilitated that. If you need to work in an office in order to get up to make a coffee or to ask for help or to "make consensus" then that's a you problem.
I can cook but I appreciated not having to think about it, and the food was great.
Re: Remote work requires communicating more, but less frequently
#157Earlier quoted context omitted.
> Instead of properly adapting the onboarding and mentoring But... how? Remote check-ins with juniors every 30-60 minutes? That's crazy. But that's basically the only way to replicate the in person experience. The best mentoring results for me as the mentee and for me as a mentor have been when we're sitting next to each other. The mentor can visually tell when the mentee is stuck, and mentee can tell when the mentor…
I like to do virtual desk with Slack, where I will have a channel where I'm always in a huddle and they can drop by when they have questions, just like they would in-office. I have to say as a counter point though that I've had a lot more trouble with coworkers coming to my physical desk for questions that they could have Googled than with Junior getting stuck for extended period of time remotely. It's all a matter o…
Re: Remote work requires communicating more, but less frequently
#158Earlier quoted context omitted.
I think the experience of banging your head against the wall (for a bit) can be valuable. As long as the culture of the team encourages this and offers an escape hatch after a few hours (or whatever timeframe is appropriate for the problem).
exactly, the most frustrating type of behavior for any colleague (esp jrs) is those who just default to consistently ask for help instead of diving deep. That behavior is costly in slowing down others. People need to learn how to learn, otherwise they will just be handicapping team if they cannot function independently. At the same time, navigating large proprietary or new knowledge sources can be tedious and sometim…
Re: Remote work requires communicating more, but less frequently
#159Earlier quoted context omitted.
I think the experience of banging your head against the wall (for a bit) can be valuable. As long as the culture of the team encourages this and offers an escape hatch after a few hours (or whatever timeframe is appropriate for the problem).
It a useless exercise to have people do so for solved problems. Sure, reinventing the wheel every time is a valuable experience, but it's not efficient to relearn how to do things every time. This is like letting toddlers struggle to learn how to tie shoes themselves, sure they will eventually figure it out, but it's better to just teach people have to do the basics, and let people bang their heads against hard probl…
Junior engineers aren't toddlers. Hopefully they're a lot more competent. Nobody hires toddlers to do work.
Re: Remote work requires communicating more, but less frequently
#160This sounds great for experienced engineers, but in my experience junior workers often require bite-sized guidance in order to avoid going down rabbit holes. A 10 second conversation could easily save hours of head-banging-into-wall type work for a junior SWE (not even exaggerating). Accordingly, during the pandemic I think it was mostly the less experienced engineers suffering from low productivity and lack of confi…
> A 10 second conversation could easily save hours of head-banging-into-wall type work for a junior SWE Agree, though sometimes the hours of head banging will benefit greatly to the skills of said junior. That aside, everyone should be encouraged to ask to company's developer forum (slack channel). That way, if the senior that's responsible to train the junior is busy, other less busy senior can help.