I worked remotely for four years and liked it a lot. The only problem was as the company grew more people came onboard who didn't really understand how to work well in a remote environment, which eventually ruined it. If you're on a remote team with people who don't like video conferencing, asynchronous text chat, etc then it's very hard to work effectively.
This is going to be a bigger problem as remote work gets more common - at the moment companies that work remotely attract developers who want to work remotely, so it works. As time goes on more developers who don' want to work remotely are going to be pushed in to remote environments as a cost saving measure, and that's going to make it much harder for everyone. How to deal with that problem is going to be a challenge.
I worked 4 years remote. It was fine.. but I started to feel isolated. I didn't have a lot of remote interaction to explore ideas. I compensated by going to meetups. Eventually, I quit to join a small on-site team. I've like being on site.
Keeps me on a schedule
More places to put books
Less interruptions by the family.
Travelling to and from provides a moment of context switching between being a parent and being a colleague.
in the remote job, we never did video chat. Maybe that would have helped my feeling of isolation, and create a better sense of community.
In the city that I live in, the library downtown (which is unfortunately a bit out of my way) has a free coworking location for remote workers. I hope they extend this out further to the other library branches.
I would love to walk a couple of blocks to a free coworking location, and more cities are going to be trying to accomplish this, I think, in order to attract remote workers, reduce traffic congestion, among other benefits I'm certain.
It doesn't solve the 'everyone in the same room' problem but it does get you out of the house.
You hear about remote jobs all the time, with more and more people wanting them because of the leisure and convenience. Along with that, you hear about people with on site jobs that want to go remote. You never really hear about people who prefer on site over remote. I'd be interested to hear some stories about on site workers who were forced(or pushed towards) remote work and denied it.
I hate remote work. I want to go to an office and do work there and then when I leave I'm living the rest of my life.
I even rented myself an office when I was working solo for almost a year before hiring someone, just so I could have a desk, a file cabinet, a printer, and a real office environment to get work done. I lived alone. I still got up in the morning and went to the office, it was good for my productivity and mental health.
I feel that it's important to set up boundaries, or tasks and work will contaminate your personal spaces. I also think that it's just 100x better for communication to have everyone in the same room working together. Nothing beats verbal interpersonal communication.
With that said, I recognize that my opinion on this is 1) entirely subjective and 2) maybe because I'm old.
I'm 25 and it's the same for me completely. Working from home doesn't work for me, I need to get out in the morning or I never leave home state of mind. Same goes for leaving.
Don't sell yourself short. Everyone works differently and not everyone keeps the same interest in how they work forever. I personally don't mind an office or the clear delineation between work and life if the office and company are set up in such a way as to not crush my spirit and allow flexibility. Otherwise I like being to work however I want. Usually this ends up being coffee shops. Right now this is coffee shops while I'm road tripping and living out of my car. It works for me kind of, certainly wouldn't for everyone. But, I can't work at home. Even if I have a home, I go to a coffee shop or park, partly for the reasons you mention.
I have had the same mentality. Being married for the past few years and with a step-daughter, I've been thinking of having better boundaries like that.
If it were just me, I think I like remote work, living alone, just fine.
It's also much more supportive of different levels of productivity throughout a day. I have incredibly poor consistency when it comes to focus. So sometimes I'll sit down and not be abke to get anything done, so maybe I'll go exercise and pick it up at a time where I'll be abke to concentrate.
I worked remote for two months and hated it. Why? Because it was lonely and chat rooms feel like talking into an abyss. Half the reason I choose to go to an office is to have a social life during the day. It also made my home feel like a prison, because I spent almost all my time there.
I'm as introverted as the average programmer, but I'll take interrupting coworkers over permanent solitude any day.
I wonder, what's the introversion level of the average programmer. Because solitude during the work hours is a blessing for me. I had a chance to work remotely for a couple of years and I will take that over having "social life" in open space office.
I greatly prefer on-site work over remote work. Being able to walk over and have a conversation, or draw something up on a whiteboard, is a much, much higher bandwidth form of communication than any remote communication that I've seen. I've seen conflicts come up in code reviews and over chat that never would have happened in person, and I always move a conversation to in-person whenever there's any worry of conflict or confusion. I'm also much happier if I spend my day interacting with other people, even if it's about work things.
I worked remote for two years for a large bank. There was an office right downtown, but I never used it. There were other people, though, who came into the office, even though they could do their jobs remotely. They liked the ritual of it, and the psychology of being able to say "Not at work now".
It's one of the major reasons the workspace industry exists. Had a flatmate who had a beautiful big room in a usually empty house to run his one-man agency from and contracted all his developers remotely, but he bought himself a desk space with 30 minute commute as soon as he had the cashflow to do so. I guess it helped create an illusion of separation even when he was still emailing clients after getting home, and offered social interaction during the day as well as the evenings
As for workers being forced to work remote by bigger companies, a colleague of mine who mostly worked from home because they closed her local office always insisted she much preferred the days she came into the London office, even though she seldom participated in office chat outside formal social events (even in the original office) and was very productive when working mostly at home.
Had another friend who didn't mind the remote work one day a week because we don't have the space for all of you rota at all, but found it a bit weird since he was a quant at a major bank...
I would refuse it. I could never work from home regularly. I spend enough time there, I want an excuse to get out into the world. It would be so boring for me not to be surrounded by people, activity, and energy. Even if I'm not interacting with people I prefer to be around them in general rather than sit alone all day.
I think you don't hear about this because it's the norm and very neutral and fundamental. I don't think most people struggle with commuting, being around people, etc. Of course those things can be annoying. But I put up with the annoyances of participating in the world because it's overall better than the alternative. Which I think describes most people.
> You never really hear about people who prefer on site over remote.
Surely you used this phrasing because you wanted to be corrected :)
I've worked both remotely and onsite and I prefer onsite. I enjoyed working remotely for the first two years. Grocery shopping mid-day on a Monday! Going for a run at 11 am! No commute! Cooking whatever I want for lunch! Awesome!
Then it got old and wore down on me. I don't like working remotely anymore. I have worked on a team which was exceptionally well-suited for it: almost all communication happened on Slack, video conferencing was a strong part of the culture, managers didn't try to micromanage, etc. But after a while I felt pretty de-socialized and disengaged from the atmosphere of the company. My work output and productivity were fine, but I found myself really missing human interaction. I staved this off somewhat with meetups and by working in a public place, but it never really replaced what I enjoyed about being onsite at HQ.
I have two (very obviously anecdotal) observations about working remotely. First, most of the people I knew who worked remotely did not adjust their lifestyle to take advantage of that time. They did not exercise any more than their onsite counterparts. They didn't really run any errands in the middle day. I generally observed that their work and play time wasn't really divorced; in some cases they didn't seem to have a work life balance, irrespective of the corporate culture. The time they saved by not having a commute was usually spent doing more work.
Second, most of the time when I voice my concerns about long-term remote work and point out the problems I personally have with it - or the problems I've personally observed - I am told that this is not an issue intrinsic to working remotely. I think that's probably true but not really relevant, and frequently used as a dismissal of people who try to voice legitimate reasons for not working remotely.
With sufficient social supplementation, investment in corporate culture and communication and self-discipline, I think just about anyone can do well as a remote employee. But it's also legitimate to say that you don't really want to make that investment (as a company) or want to do what's needed to avoid working too much and not seeing other people enough (as an individual). Remote work can work very well, but I do not think most people should work remotely.
> A service to connect with other remote workers in the same city as you would be really helpful.
But only part of it. Surrounding yourself with strangers you have no connection to, except that you all work "remotely" somewhere, is not the same as being surrounded by colleges you work with face to face.
In my experience it comes close actually. I do remote work with 1 day a week from a coworking space, 1 video call every morning, and some pairing every week. The coworking space with mostly "random" people (but a mostly consistent group) really helps me fill that some kind of communication need.
I can confirm your first sentence with my own case. As the team grew, more non-remote people were hired, management changed to not-so-remote-friendly bosses and with them process that were remote-first started becoming local-first with (crappy) ways to allow remote people, and that has been killing the effectiveness of being remote on that team... And it's hard to grow past a certain point being remote.
I've been working remotely for four and a half years and not once have we used video conferencing. Voice and chat sure, but video is useless, doesn't add anything, and makes a lot of people uncomfortable. I personally despise it. It's clearly unnecessary as we have been doing quite well without it for a long time.
"who didn't really understand how to work well in a remote environment, '
I think on average remote workers need to be more mature and self-sufficient while at the same time very open to communication. It's definitely harder to hire for.
Purely distributed teams are great if all processes are designed for that. But most companies don't do it right. In my company we augment the US team with Indian devs and it really sucks royally. Most decisions are still made in meetings so the Indians don't know what's going on. The 12 hour time difference requires either that the Indians stay up late or come in early or the US workers have to do it which sucks if you have a life outside of work. Resolving even little issues takes too long because round trip time between question and answer is often several days. We also never travel to India so we don't know the people personally and don't know how they are set up.
The way a lot of companies go about with distributed teams is the same they do with agile. Management picks a few artifacts (daily standups, detailed backlog) but most other structures stay in place so the result is highly dysfunctional.
I've worked full time remote for two companies now, and one was more like you described, where most of the team was in one place with "augmented" remote employees, and the other bit the bullet and treated everyone remotely, even though there are large physical offices where some people like to work. And the main issue is communication.
"Augmenting" your team with remote workers leads to horrible communication. First, meeting rooms require very good audio setup, and very few people will spend the time, hire a sound engineer, and operate the meeting such that everyone in the room is clearly audible. As a end result, the remote workers often sit there with the sound up trying to figure out what's being said most of the time. Thus, people can never really act normally - everything has to be this composed, staged, response.
Additionally, the mostly local team will frequently have offhand conversations the remote workers are never a part of. Thus, you get siloing. Add time zone shifts, and the amount of siloing increases.
The place I work for now has teams that rarely meet in a physical room together - even though several members sit near each other, everyone's got a headset. It is amazing how decent audio changes communication. We also frequently have chats online.
Additionally, all major meetings at my current company are held as if people are remote. And events or other informal affairs are kept organized and isolated. I don' t have to sit through notifications about the coffee machine on the 3rd floor of a building 1300 miles away being broken.
I believe this has led to senior management feeling comfortable working remotely as well, so some VPs work from cities where there is no significant office or company presence.
Now, I _do_ wish this company relied on writing, but not everyone is a good writer. It takes a lot of time to build up that kind of confidence. If I could make one change, it would be to improve writing.
I agree that to make remote teams work the company (leads, actually) have to work differently. It can pay off or not, but assuming one can manage remote team just as you do a local one is a almost always a recipe for failure.
> Resolving even little issues takes too long because round trip time between question and answer is often several days.
This is the crux of the issue. You can expect question and answer round trip to be up to 24 hours, but the work flow must not depend on this being being minutes or hours. This means structuring work flow in larger chunks, writing tasks for remote teams clearly and having robust success criteria that remote team can check against, locally, before claiming they are done. And remote team must be able to understand what the request is before signing off on it -- at the very least they should have crystal clear understanding on those written success criteria.
Done this way, little issues that require a 24-hour turnaround are few and far between. It never works perfectly, so the company should also bring key tech leads together a few times per year. It is a different setup, requiring more careful planning at headquarters and competent leads, but it can be done.
But companies that manage remote teams as if they sit in the same building will get some serious disappointment. My 2c.
Ive never seen it work in practice. It just leads to endless meetings in attempt to synchronize what each team's are doing, and it's often very difficult to understand eachother over video only.
When I was working like that for a short while, I was trying hard to not collaborate with anyone and just do things myself in order to continue to make progress and get something done. Other team members who were trying to collaborate had extremely low output and their days were filled with troubleshooting stuff together with the remote team since basic things didn't work or got blocked by knowledge not existing on one side etc.
Definitely agree with that. Issue trackers in particular I've found to be a very powerful tool for navigating an environment that has bad actors within it - when everything is down in black and white it greatly reduces attempts at weasally behaviour from the more Machiavellian. Sad to say, I've come across this type more than once.
Most ambiguous thing I have found about remote work is how a decision gets made in a group, and then who directs the action on it.
It's too easy to talk past one another on conferences. Add flat organizations where you are supposed to be able to read the dynamic between the lines, then local culture differences, and you can end up in passive aggression hell.
Without physical presence, you need clear, logical rules in place.
The article splits the main challenges of "loneliness," and "collaboration," almost evenly. I don't get loneliness, but collaboration and distance are almost definitely conflicting needs.
I would be surprised if the rules for managing distance being a constraint on the dynamic aspect of collaboration was not a hard zero sum trade off.
Is it just me, or did the article completely fail to answer it's premise? I really wanted to hear about how office politics works in a full time remote workplace. The closest thing to an answer for this is "we write stuff down so it's permanent."
It is important to differentiate between distributed and remote, as well. I work for a very large company that has offices scattered all over the country. We are distributed, and remote exists but is not the norm.
It is unusual to have a meeting that doesn't make use of videoconferencing, even when everyone involved works primarily from an office.
For employees who are remote, this setup is wonderful. It means that there's little difference between being remote and working from a different office.
I'm remote but part of a team where some people are office based, and it can be nightmarish at times - I'm cut out of the loop time and time again, and the excuse that 'oh we just had a quick conversation about it and you didn't happen to be there' has now worn thin to the point of transparency. It's definitely the case with remote working that failure to prepare (on a company's part) is preparing for failure.
Suspect it's more than that, unfortunately. Thankfully though my circumstances are changing soon and I'll hopefully be out the door to somewhere better. Life's too short etc.
Sarah Cooper’s “10 Tricks to Appear Smart in Meetings,” which includes…
I took the bait and read the 10 tricks. These are all natural tendencies for me. This must explain why clients think I'm smart because I'm really not as smart as everyone treats me.
I would very much like to have a small discussion on this if you don’t mind sharing your thoughts on the following:
What would be the ground truth for some notion of smartness level? It could certainly be subjective, sure, but could you please tell me what you think being smart means? Do you think people around you have different scale/notion of smartness than you? Would it be possible that you’re being hard on yourself? If not, how would you rate/think about your coworkers smartness?
I am really interested in knowing your thought process because a part of me certainly identifies with your statement. And I am very much interested in discussing “appearing to be smart” vs “being smart”. Something tells me there’s not much difference between the two or perhaps only the former exists and latter is too abstract to be useful for any comparison.
I do a lot of consulting so that might have something to do with it. Basically I get paid to appear to be the smartest person in the room (which I personally think is utter and total horse shit but that's another rant). I've been told my whole life that I'm "smart" but the problem is there are lots and lots of people out there who seem (I've tried to read their papers on ML) like they're an order of magnitude smarter. I write like a 13 year old, but maybe I speak better? IDK.
For most people I think it's totally subjective. If you surprise someone with a bit of knowledge they don't have (either memorized or figured out for yourself) people think you're "smart". People who share what they know or help others come to a novel solution appear "smart".
I do believe in a general concept of intelligence (q). I'm willing to bet mine is only slightly above average if even that, only because I keep meeting programmers who cannot think as clearly as I can so I have to assume I'm smarter than some of them.
I'm sorry I don't have a better answer. It's a total mystery to me. I feel like a total dumb fuck most of the time.
You said you identify with my first comment. How so?
Thank you very much for your answer. It gave me a lot to think about.
To answer your question - I have been told by my peers and teachers that I have “potential”, some pointed out that I am exceptionally good at grasping new concepts. From my point of view I “sort of” accept whatever new information is presented to me as truth and my mind goes into a kind of overdrive. It constrcts all the possible realities and finds inconsistencies or irregularities. It just doesn’t know when to stop. Over time, I believe I have improved the way I communicate these imaginations of my mind which I suspect makes people think I am smart. However, this doesn’t say anything about whether I actually understand the concept or if I have deep knowledge of the presented subject. This, in my opinion, is an appearance of being smart rather than actually being smart.
All no-brainers as usual. I've been working remotely full time for three years now. There is no downside for me. Offices (and open floorplans) exist out of inertia only, and, because of the politics they encourage, are havens for the incompetent.
1. Remote is not "from your house". Rent an office near home, walk there.
2. Use video conferencing every day without fail. Something very monkey brain makes a human face you are talking to real, and prevents you flipping the doofus bit on people (and they you)
3. Everyone and everything must be remote-first - business and IT. There is real advantage to walking over and saying hello, shaking peoples hands.
4. Meet up in person and work together (pairing, meetings, clarifications) at least once a week. This basically limits the distance you can all be from each other (roughly two major metro areas apart - London and Paris, NY and Washington)
Ultimately this all costs money. it's cheaper to hire crap people and expensive office space.
This is going to be a bigger problem as remote work gets more common - at the moment companies that work remotely attract developers who want to work remotely, so it works. As time goes on more developers who don' want to work remotely are going to be pushed in to remote environments as a cost saving measure, and that's going to make it much harder for everyone. How to deal with that problem is going to be a challenge.