3 ms·
> ... if an employer insists every programmer has to hang around in that area something is off in their thinking. Yeah, I think that one of the only potential
by yladiz 10y ago
> ... if an employer insists every programmer has to hang around in that area something is off in their thinking.
Yeah, I think that one of the only potential issues with working remotely is that timezones may cause issues, but as long as meetings are planned well ahead of time and there's some kind of overlap with time so coworkers and bosses can communicate, working remotely makes more sense than working in an expensive place like the Bay Area. However, even with respect to timezones, companies such as Zapier have no issue with working remotely as far as Thailand (iirc) even though they're based in the Bay Area, so even that issue may be moot.
- 49531 10y agoTypically a good remote team should have "core hours". Usually 4 - 6 set hours each day where team members are expected to be online. Some team members end their day with the core hours, while some begin their day with it. It makes _most_ locations doable, but I've had some far flung teammates with odd sleeping schedules to account for it.
- jaggederest 10y agoMy experience as a full time remote worker since 2011 is that it can be tough in those ways, but at least for me, office work has its own challenges that nobody seems to give much credence. If you compare them without defaulting to office work, it's pretty balanced. I find it more difficult to get work done in an office environment, so whatever downsides there are re: meetings, (and I'm not certain that most meetings deliver a lot of value) there are upsides in terms of personal productivity that outweigh them.