Writing software remotely works out great with things like version control, ticket managing systems, chat and screen sharing/video conferencing. I wonder what industries struggle to be efficient remote. I know the designers at my current company have said they have a hard time collaborating remote compared to in person. I wonder if it’s a culture issue or a lack of tooling. There might be some money making ideas there.
I work remotely, as does pretty much my entire company. Some of the biggest issues we have due to remote work is communication tools. I haven't found a tool that can replace the ease of communicating with a large number of people in the same room when having a collaborative discussion. I think the issue is largely due to latency. It's take a lot of practice to understand how to communicate effectively using video conferencing software.
Another issue is team building / comradery. I don't know my current coworkers nearly as well as I've been able to know coworkers from previous companies I've worked with. When remote you don't get to go to lunch, grab coffee or a beer with your coworkers. We do travel a lot to meet up, but I still only see people I work with closely when doing so. As the company grows it's much more difficult to even begin to meet everyone in the company which is much easier when in and office because everyday you can bump into someone different.
We've tried to solve this to some extent through randomly pairing two people every two weeks to schedule a short 15 minute meeting. However the scheduling itself is not automated and it's not always easy to schedule time due to lack of proper calendaring software and distributed share calendars. This is definitely something that could be solved but it's just another challenge of working remotely.
I have a dream that rural work will become more popular. I live in a city where all the local kids go to the oil fields or get out of Dodge, but I've heard a lot of comments from families that they'd do just about anything not to work out of town. With remote work, you could have more families and offset the retiree population, making this a more vibrant community. Does anybody have experience with starting a coders group in a low-density area like this?
Anecdotal, but I'd take lower pay to go remote and move back to my hometown (not a small town, but a small city with a weaker tech market than where I currently live). Being able to live near your friends and family that you grew up with is a massive benefit.
Second this. I'm particularly interested in whether or not the rise of remote work will affect the demographics of smaller cities that have some appeal from a tourism perspective. I can think of so many cities with low costs of living and vibrant cultures that are fun to visit, but where I could never live because of the lack of work. I wonder how that all changes when the majority of jobs are remote-friendly.
Is there a difference? A lot of people would only want to visit in NY or SF but plenty others would happily live their whole lives there. The existence of a vibrant culture should tell you that some people do like living there (otherwise the culture wouldn't exist).
That's fair. I agree. I didn't think about it that way at all. I've lived in NYC for all but 6 years of my life so I'm definitely in the could live in large metropolis my whole life category
I've been working remotely in various forms for nearly a decade, while also living in a rural area.
Organizing coder groups is hard, but one of the most interesting things I've discovered is that you don't get to be as picky about the specifics of technology. A hacker group (which is in a bit of down period right now), had a bunch of hardware guys, an active member of the clang community, a few Haskell/FP curious guys and someone who mostly worked in network device manufacturing. Really, really neat group of people, with even a few women. What you don't get are your hyper-focused Python groups or groups dedicated to frameworks like Rails, which I always thought was probably a net-gain.
I think this is already happening. Mid-size city demographics are shifting significantly, especially those within an hour band of a reasonable larger city (700k+).
I’ve seen some contracting firms do domestic “ruralshoring,” but IMO recruitment costs become controlling due to the lower density of talent and general difficulty with remote management as a practice. The common approach is to concentrate on small university towns that have a young CS talent pool — similar to Epic’s hiring approach — but eventually your talent moves to urban areas for culture/amenity/economy reasons, so you end up with a predominantly young remote workforce, which brings its own managerial issues.
I've worked with a significant number of remote workers (some part time and some full) and these remote management policies people keep talking about not being there or "standard" makes me think they're making a mountain out of a molehill.
Giving people deadlines and incremental check-ins ala milestones for projects or other work that they eventually have to show or "turn in" is all it is. Easier said than done, certainly, but if you can quantify the person's work on prem, remote isn't that difficult to manage.
It’s easier to fake it when you’re working onsite. How do you tell if someone is really working? Just by seeing them at their desk? It’s is absurd to think that someone is working hard because they sit long hours at their desk. Get some tools.
So true. My impression of one guy at my current organization is that he had some skills and productivity years in the past, but now he’s just given up and fiddles around on his phone while doing occasional low-effort tasks and trying to bully newcomers into doing things he can take credit for. Why he’s still there is beyond me. Very unlikely (in my opinion) that he could get away with this remotely.
If a role doesn't add value by remote, what is the real value of the role?
Remote work is not difficult to implement, remote management on the other hand, is disruptive. It is so new we haven't aggregated the best practices into some basic theory to train managers with, so it's going to be patchy. Arguably, most managers are not educated to manage in the first place, and an increasing majority seem to just sense the wind direction and muddle through.
A significant percentage of remote employees might be a signal that they are creating so much value that it offsets the managerial risks associated with it. A butts-in-seats grind culture could suggest the marginal value employees create is so small it needs to be ground out of them.
I don't think current companies will switch to remote, but I do think new ones will start with the question of whether a role justifies the overheads of an on-prem requirement.
Conversely, if the only value you add can be codified and delivered as work packages without physical contact with your peers, what makes you think that you have more value than someone offshore / a robot?
If you're doing real, creative, problem solving work, then daily physical contact with your colleagues is essential. The bandwidth of knowledge transfer is vastly in excess of anything that can be done remotely, and quickly bouncing ideas off other people will get you through problems and blockers far more effectively than anything else. We still don't have any collaboration software which can replicate this experience.
"If you're doing real, creative, problem solving work, then daily physical contact with your colleagues is essential. The bandwidth of knowledge transfer is vastly in excess of anything that can be done remotely, and quickly bouncing ideas off other people will get you through problems and blockers far more effectively than anything else. We still don't have any collaboration software which can replicate this experience."
This looks alot like the argument that was initially used to push open offices, which turned out to be not so right.
I'm not so sure about this. Remote is great for task-based work. But certain companies like Amazon seem to have a "cult"-like culture that keeps everyone focused and on the same page. And Google provides on-site services to increase productivity and time spent on campus. Being a remote worker, I feel more detached from the company "vision" and more like a mercenary who likes to get things done and then go about my life.
Well this is news to me, because I am looking fora remote software developer , I know nodejs, golang.....
and every company I applied to says. must be onsite,
or they advertise a "remote developer" and then they tell you in the interview it's remote 2 days a week, the other days, you have to come in to their office, in santa monica california, trouble is you live in new york. go figure.
If anyone is hiring for a 5 day a week remote role, be sure to hell to let me know, callagg3@gmail.com :)
25 comments
[ 6.0 ms ] story [ 78.8 ms ] threadCall-centers are another industry that can be entirely remote.
Another issue is team building / comradery. I don't know my current coworkers nearly as well as I've been able to know coworkers from previous companies I've worked with. When remote you don't get to go to lunch, grab coffee or a beer with your coworkers. We do travel a lot to meet up, but I still only see people I work with closely when doing so. As the company grows it's much more difficult to even begin to meet everyone in the company which is much easier when in and office because everyday you can bump into someone different.
We've tried to solve this to some extent through randomly pairing two people every two weeks to schedule a short 15 minute meeting. However the scheduling itself is not automated and it's not always easy to schedule time due to lack of proper calendaring software and distributed share calendars. This is definitely something that could be solved but it's just another challenge of working remotely.
On the other hand, some of us are trying to get as far away from those as possible.
Organizing coder groups is hard, but one of the most interesting things I've discovered is that you don't get to be as picky about the specifics of technology. A hacker group (which is in a bit of down period right now), had a bunch of hardware guys, an active member of the clang community, a few Haskell/FP curious guys and someone who mostly worked in network device manufacturing. Really, really neat group of people, with even a few women. What you don't get are your hyper-focused Python groups or groups dedicated to frameworks like Rails, which I always thought was probably a net-gain.
Texas Monthly did a good piece on this recently. https://www.texasmonthly.com/the-culture/high-rents-rural-re...
Giving people deadlines and incremental check-ins ala milestones for projects or other work that they eventually have to show or "turn in" is all it is. Easier said than done, certainly, but if you can quantify the person's work on prem, remote isn't that difficult to manage.
Remote work is not difficult to implement, remote management on the other hand, is disruptive. It is so new we haven't aggregated the best practices into some basic theory to train managers with, so it's going to be patchy. Arguably, most managers are not educated to manage in the first place, and an increasing majority seem to just sense the wind direction and muddle through.
A significant percentage of remote employees might be a signal that they are creating so much value that it offsets the managerial risks associated with it. A butts-in-seats grind culture could suggest the marginal value employees create is so small it needs to be ground out of them.
I don't think current companies will switch to remote, but I do think new ones will start with the question of whether a role justifies the overheads of an on-prem requirement.
If you're doing real, creative, problem solving work, then daily physical contact with your colleagues is essential. The bandwidth of knowledge transfer is vastly in excess of anything that can be done remotely, and quickly bouncing ideas off other people will get you through problems and blockers far more effectively than anything else. We still don't have any collaboration software which can replicate this experience.
This looks alot like the argument that was initially used to push open offices, which turned out to be not so right.
If anyone is hiring for a 5 day a week remote role, be sure to hell to let me know, callagg3@gmail.com :)