It is kinda hard to have a bunch of juniors at home. I’m all for WFH, and have been doing it most of my life, but I’m also very productive, experienced, and don’t need hand holding. If I was starting out now, there’s no way I could get meaningful experience with just PR feedback from the person who keeps rejecting my PRs with asshole comments.
We jad a junior to train while we all WFH, but he was a very receptive and smart guy, so it was kind of easy.
The last stage of code review, we would go through all changes together in a meeting. I would explain the reasons something may be a bad idea (e.g. harder to maintain later on). Other things were also handled in meetings, so i didn’t feel it too different from what I’d do in the office, such as designs/whiteboarding.
This does require enough capacity from seniors, though.
In short, it can work, though some people may prefer face to face contact, and the organization/availability has to allow for some hand holding.
My first junior job was entirely WFH and it didn’t seem that hard. Messages and calls exist. It’s not like your only interaction with people is through async PR comments.
Yeah since then, and I’ve done pair programming both in the office and online. It didn’t feel that different. The biggest advantage of the office is you get to know people better. I guess it’s easier to chase seniors in an office as a junior if they don’t have time for you but I hate being that person either way.
I like to know people personally. 🤷♂️ I’d rather work with a cool person with average code than some aloof GitHub username. I’ve done both, and the first is better for mental health. That said, WFH is… very nice. It’s a toss up I guess.
It is kinda hard to have a bunch of juniors at home. I’m all for WFH, and have been doing it most of my life, but I’m also very productive, experienced, and don’t need hand holding. If I was starting out now, there’s no way I could get meaningful experience with just PR feedback from the person who keeps rejecting my PRs with asshole comments.
That doesn’t sound like a WFH problem
Haha. Possibly not. But it’s easier to learn when you’re able to talk in person. And I think the last 6 years proves that pretty well.
We jad a junior to train while we all WFH, but he was a very receptive and smart guy, so it was kind of easy. The last stage of code review, we would go through all changes together in a meeting. I would explain the reasons something may be a bad idea (e.g. harder to maintain later on). Other things were also handled in meetings, so i didn’t feel it too different from what I’d do in the office, such as designs/whiteboarding.
This does require enough capacity from seniors, though.
In short, it can work, though some people may prefer face to face contact, and the organization/availability has to allow for some hand holding.
My first junior job was entirely WFH and it didn’t seem that hard. Messages and calls exist. It’s not like your only interaction with people is through async PR comments.
It’s not about hard. It’s about getting one on one with people. Have you ever had a developer job in the office at least part time?
Yeah since then, and I’ve done pair programming both in the office and online. It didn’t feel that different. The biggest advantage of the office is you get to know people better. I guess it’s easier to chase seniors in an office as a junior if they don’t have time for you but I hate being that person either way.
I like to know people personally. 🤷♂️ I’d rather work with a cool person with average code than some aloof GitHub username. I’ve done both, and the first is better for mental health. That said, WFH is… very nice. It’s a toss up I guess.
I find WFH with voice calls the sweet spot but it’s a preference ¯\_(ツ)_/¯