3 ms·
The first counterargument that comes to my mind is timezones. I was on a team distributed across San Francisco, New York, London, Munich, Australia, Tokyo. Not
by kaycebasques 5y ago
The first counterargument that comes to my mind is timezones. I was on a team distributed across San Francisco, New York, London, Munich, Australia, Tokyo. Not being able to schedule a meeting time that works for everyone was a neverending source of friction and frustration. In other words while I don't disagree that there is a lot more work that can be outsourced, perhaps we will reach the limit earlier than you expect.
- AlgorithmicTime 5y agoTimezones arguably benefit some places that require a 24/7 coverage schedule.
- bluedino 5y agoDoesn't matter. I'm not sure what time it is in India, the Philippines, or the Czech Republic, but the support teams answer the phone between 8am and 5pm our time.
- beckingz 5y agoOne growing trend in the US is outsourcing to South America. Lots of great value developers down there in the same timezone. The second issue that still comes up is communication and culture. Successful cross cultural communication requires more clarity in messaging and tasks. It can work and can work well and deliver good quality at great prices, but the obvious savings are partially offset by the higher communication and management costs. Sometimes more than fully offset.
- deleted 5y ago[deleted]
- TexanFeller 5y agoThere are tons of competent developers in Central and South America in time zones close to the US. The language/accent barriers as well as cultural differences are much less than say India IMHO. On average the folks I’ve worked with haven’t been as good as US staff, but I bet the gap could close quickly.