That rings true, I think for most seniors who've been around the block remote is fine, for juniors it might be a different story. A combo of local and remote (co-working spaces?) might be optimal in many cases.
Been using UNIX since the late 80s; Linux since the mid-90s; virtualization since the early 2000s and spent the past few years working in the cloud space.
Location
Alexandria, VA, USA
Education
B.S. Psychology from Pennsylvania State University
I'm 25+ years into an IT consulting career. I've only had brief stints as a "never remote" worker. In short, I don't think new-to-the-profession people are intrinsically disadvantaged by going to work for a 100% remote business.
For reference: I first started doing almost-wholly remote work in 1997. My employer paid to run an ISDN line and a PBX-extension to my apartment (cell phones weren't practical options, back then, just pagers). It was only my second IT-focused job — after having only been at my prior employer (my first permanent, full-time job after graduating from college) for 18 months. So, I'd say I was pretty junior at the time (even if my hobbies had made me "advanced for my age").
I have seen a lot of my batchmates struggle, while I didn't have any major issues while working from home. I am talking about interns here, who haven't yet graduated. Knowing my way around tech and being "advanced for my age" has actually made WFH easier for me. Doesn't mean it is the same for others. Junior devs do struggle with WFH!
Been using UNIX since the late 80s; Linux since the mid-90s; virtualization since the early 2000s and spent the past few years working in the cloud space.
Location
Alexandria, VA, USA
Education
B.S. Psychology from Pennsylvania State University
My point was more that whether you struggle or not (or need an office setting), is less a function of seniority than the individual worker. I've spent most of my career working on distributed and/or remote/wholly-offsite teams. Some people are suited for it, many aren't. It was never a problem for me. But, for others it often is. Worse, most people don't really know whether they're suited for it until they accept their first primarily-remote or remote-only jobs. Over the years, I've encountered many newly-hired senior engineers who simply couldn't cope with not working in an office and being able to have face-to-face conversations (not just work-related, but the random "what did you think of the latest GoT episode" or "man, the Cowboys really stunk it up, yesterday" conversations ...possibly finding the absence of the latter more problematic than absence of the former).
Overall, it's sorta like how a significant number of people have had problems with the COVID19-related lockdowns while some don't. I feel fortunate to be in the "don't" camp.
Ironically, one of the biggest problems I had with remote work didn't occur until after I got married. It took my wife nearly two years to understand that just because I was home didn't mean I was available. It took a number of months of me stating — eventually yelling — "that thing you walk by that looks like me? That's not me, that's just a really lifelike hologram" …and that my business-hours availability is just like when I used to travel for a living — if it ain't a legit emergency, I ain't available during those hours (and, no, the fact that your cable box isn't working doesn't constitute an emergency).
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
That rings true, I think for most seniors who've been around the block remote is fine, for juniors it might be a different story. A combo of local and remote (co-working spaces?) might be optimal in many cases.
I'm 25+ years into an IT consulting career. I've only had brief stints as a "never remote" worker. In short, I don't think new-to-the-profession people are intrinsically disadvantaged by going to work for a 100% remote business.
For reference: I first started doing almost-wholly remote work in 1997. My employer paid to run an ISDN line and a PBX-extension to my apartment (cell phones weren't practical options, back then, just pagers). It was only my second IT-focused job — after having only been at my prior employer (my first permanent, full-time job after graduating from college) for 18 months. So, I'd say I was pretty junior at the time (even if my hobbies had made me "advanced for my age").
I have seen a lot of my batchmates struggle, while I didn't have any major issues while working from home. I am talking about interns here, who haven't yet graduated. Knowing my way around tech and being "advanced for my age" has actually made WFH easier for me. Doesn't mean it is the same for others. Junior devs do struggle with WFH!
My point was more that whether you struggle or not (or need an office setting), is less a function of seniority than the individual worker. I've spent most of my career working on distributed and/or remote/wholly-offsite teams. Some people are suited for it, many aren't. It was never a problem for me. But, for others it often is. Worse, most people don't really know whether they're suited for it until they accept their first primarily-remote or remote-only jobs. Over the years, I've encountered many newly-hired senior engineers who simply couldn't cope with not working in an office and being able to have face-to-face conversations (not just work-related, but the random "what did you think of the latest GoT episode" or "man, the Cowboys really stunk it up, yesterday" conversations ...possibly finding the absence of the latter more problematic than absence of the former).
Overall, it's sorta like how a significant number of people have had problems with the COVID19-related lockdowns while some don't. I feel fortunate to be in the "don't" camp.
Ironically, one of the biggest problems I had with remote work didn't occur until after I got married. It took my wife nearly two years to understand that just because I was home didn't mean I was available. It took a number of months of me stating — eventually yelling — "that thing you walk by that looks like me? That's not me, that's just a really lifelike hologram" …and that my business-hours availability is just like when I used to travel for a living — if it ain't a legit emergency, I ain't available during those hours (and, no, the fact that your cable box isn't working doesn't constitute an emergency).