4 ms·
> I work from home most of the time, except for travel across the US one week a month. I've worked full time remote for over 10 years for different companies a
by eikenberry 7y ago
> I work from home most of the time, except for travel across the US one week a month.
I've worked full time remote for over 10 years for different companies and never had to fly that much. I've always flown once or maybe twice a year at most. I think this is more the norm, at least for software engineering and operations.
> The problem IMO is that too little work is truly remote.
You follow this with some specific examples, most of which would require travel even if you were in an office. I don't agree on those you list as requiring face-to-face meetings, they are all fully capable of being done remotely. IMO the only ones that require you on site are one where you physically interact with things/people.
- notacoward 7y ago> they are all fully capable of being done remotely. They certainly are, as long as others cooperate. Good for you if you've never been on a team where people resist and sabotage any such effort. I don't see any particular reason to believe your shorter experience is more representative than my longer one.
- eikenberry 7y ago> your shorter experience I had assumed I had the longer experience as most people I've discussed it with have only worked a few years remotely and you didn't specify. I've only worked one job that was part-time remote where people weren't cooperative with it. But that was mostly the results of one manager who was generally bad, so I didn't take it as remote specific. The other 3 companies where I worked full time remote were all good experiences w/ no one sabotaging things. Solving the issue with one place with the bad manager was pretty simple though... I just found a new job where it wasn't an issue. Anymore I only apply to places that are either fully remote or advertise themselves as remote friendly with a remote-first culture and it hasn't been an issue.