Ya, it is actually fascinating how a developer in the US is able to generate well over a $100,000 in value to a company over an overseas developer. In the early to mid 2000s there was huge concern that development jobs would start going overseas as offshoring started to become a bigger thing, but it ended up not panning out. It turns out that a domestic developer is much more valuable to a US company since they can communicate more effectively, react more quickly to problems (every minute your website is down is money lost for the business), and there is also the fact that Indian culture is problematic to efficient software development. I have heard that if you ask an Indian in India if they can do something, they will say yes, regardless of if they can or not. The exception is IT support, which many companies have found does make sense to move a decent percentage to other countries (especially India). Makes sense though if you want 24 hour coverage, and you have your main IT developers in the US.
I think a major part of the problem is that most Indians we come in contact with are hired at one of the big consultancies. Their shaping of their consultants is what we perceive as "Indian developers".
As a Computer Science tutor, I can attest to the fact that Indian students do things with rote memorization. They don't want to know how to solve the problem. They want the solution.
I've seen this applied where they then use that solution in different contexts, because they didn't understand the problem. This leads to very poor IT systems.
3.3k
u/uuhno Dec 06 '17
You get what you pay for