3 ms·
I think some of it is a "senior vs junior and a maturity divide" as you said, but some of WFH effectiveness has to do with experience in the current role/projec
by lastofthemojito 6y ago
I think some of it is a "senior vs junior and a maturity divide" as you said, but some of WFH effectiveness has to do with experience in the current role/project. I've got something like 18 years of software experience, have often been the senior guy who doesn't require handholding, etc. But I got a new job during the pandemic, and joining a team with a complex system and various environments and deployment methods, etc, takes some time to come up to speed on. I definitely felt that I picked that stuff up more slowly from Confluence pages and Slack conversations than from previous transitions where you can sit next to a co-worker and effortlessly watch what they're doing, talk about what they're doing, shout over to the person in the next cube with a question, etc. Not saying WFH doesn't or can't work, but I do think that people who are already up to speed do well WFH and people who are still coming up to speed are at a bit of a disadvantage.
- macintux 6y agoBootstrapping is definitely a process that's much easier when you have instant, low-friction access to the people with the knowledge. Often you don't even know what questions you need to ask, and the give-and-take of a 1:1 face to face meeting provokes all sorts of useful tangents.