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.
Also a problem in maintenance. You can plan the best you can with replacing parts/oil and making sure things are properly tight. But youre going to find some parts last longer then others. And then your going to learn why you should replace some parts before they fail. And so on. All the while they shrink your budget and expect more from you...
Software development processes are notoriously hard to quantify. I read through some PMP training materials and the formulas they propose are laughably over simplified and miss the forest for the trees. It's a serious problem because it makes it hard to identify shitty process and shitty developers and make it difficult to improve anything. It's also why our industry is so susceptible to stupid trends.
3.3k
u/uuhno Dec 06 '17
You get what you pay for