Quote:
Originally Posted by Handro
Yep, when I worked for an Indian company there was a lot of double work going on. Teams in India and teams in SF/Chicago/NY not knowing who's role was what, lots of super early mornings/super late nights (mostly for the Indian employees), etc. A lot of it probably could have been managed better if the company wasn't so young and some of the management more invested, but the reality of 100% remote work across several time zones was apparent.
|
Even when it's managed well, it sucks. I've worked and managed teams in India and Europe before, and I hate it. The teams in India are willing to be on for a few more hours than those in most of Europe but it sucks. Try making software with people on one team located in the US, Europe, Asia, etc at once and they all have to collaborate. I called it out in my circles back when some companies announced it. It's one thing to have teams split across the continental US, which is doable, but I'd never approve actual non manager engineers working in Asia, Europe, North America, etc on the same team. It's very unrealistic. The only way it works is if you have enough mass in one location or timezone (or mostly adjacent timezones) and can form teams based on that.
I think a lot of companies who require highly collaborative teams will learn the hard way or have already realized it's way easier said than done.
We'll see some companies do hybrid and some do the "old" arrangement pre covid. Each one will require people to still mostly be colocated which is good for various cities and areas.
I imagine in that case we'll continue at a minimum to see demand for new residential anyway, especially as the amenities that attract people to live in a city (who can afford it) continue to open more and more.
Prev
Linear Mode
