3 ms·
I mean, maybe? We had an offshore subsidiary in India. The problems with it were LEGION. 1. The key issue was overall quality. I'm sure it's possible to get g
by ubermonkey 5y ago
I mean, maybe?
We had an offshore subsidiary in India. The problems with it were LEGION.
1. The key issue was overall quality. I'm sure it's possible to get good code out of an offshore team, but we couldn't. Their contributions to our code base comprise the lion's share of the technical debt we're carrying.
2. Time. Working asynchronously is really, really hard, even without any other issues floating around. I wouldn't want to work async with the best devs I've ever known, let alone a "regular" dev.
3. Culture. Local cultural differences can KILL developmental communication. If the local customs discourage saying "no, I don't understand" or "no, we can't do it that way" or whatever, then you end up with bad code and a worse product even if you get anything at all out of it. (I have my biases here, but I'm trying to frame this as a mismatch of expectations and not, as some might, an example one way being Good and the other Bad.)
I might be willing to work with proven, reliable, highly communicative resources at a 6 hour offset, but a new hire on the other side of the planet working local hours? No way.
- sumedh 5y ago> I'm sure it's possible to get good code out of an offshore team, but we couldn't. That depends on the salary, how much were you offering?
- ubermonkey 5y agoEXTREMELY competitive salaries. The company owner believes in paying for talent.
- sumedh 5y agoEXTREMELY competitive salaries does not say anything. You have companies like Google and Microsoft in India paying very well and you have the IT consulting giants like Infosys, TCS etc who pay peanuts yet they still find employees but they have a bad reputation. Was your company paying Google level salaries or the TCS level salaries?
- ubermonkey 5y agoGod, I hate HN discourse sometimes. I guess you'll just have to take my word for it. Or not, Internet Stranger.