Slashdot Mirror
Can China Pull An India?
ricst writes: "The New York Times has a story about how China is trying to leap ahead of India as the world's second-largest producer of software. Apparently the Chinese are trying to learn everything they can from the Indian software developers. It's not clear that if China becomes a strong competitor to India that 'jobs will be lost or simply not created' in the U.S. My guess is that the most creative software opportunities will remain in the US for some time, and the more routine development efforts will continue to be transfered overseas."
People may wonder how this type of outsourced programming works, and I'll run down a few examples here.
One is the fixed API method. A function or functions are needed that perform X on data Y. This requirement is simply farmed out, and code is produced that does this. This code is then integrated into the larger code by the contracting company. In essence, this is the grunt work of programming, and it's where India started, and where China will likely start too.
Another is code upgrade. Legacy code in one language is handed to a programming team, and the requirement that it be ported to new language X on system Y is given. India does a lot of this now, and their technology parks have a plethora of older hardware to mimic these legacy systems for developers to work with. The advantage here is that Indian's speak english fluently and reading native code with it's comments and documentation presents no problem at all for them. A legacy of British Colonialism that the Indians have turned to their advantage. I don't see the Chinese doing well here very quickly, as periodic reviews will be done in english, and communication could be a total headache.
The third is the requirement style. Software must perform X,Y,Z and run on systems A,B,C. This is becoming more common. In this case, the entire software suite, from the core to the interface is handled by the Indian company. This is where India finds itself today, and it's pretty good at it. I've reviewed some results from projects like these, and the coding style is uniform, properly commented and compact. It's also a unique kind of style, and takes some getting used to, but any given company will produce the same style each time, so it's certainly very acceptable. On average I'd say it's less buggy, BUT!, I only see the end result, it may have been hell just weeks before, and I never saw it. This is somewhere the Chinese could do well, as a final pass to translate comments isn't terribly hard, but
The last style is market need. This is where a perceived need is seen, and software is made to meet this need unsolicited. This I haven't seen very much, but as they become more aware of our market, India will certainly begin to try it's hand at this. China may never bother, as their own market is probably going to be big enough to consume any supply for a long time, and the very different cultures make the risk greater than a lot of companies may want to take.
It's debatable wether China will ever catch India, the difference in style of education and culture may be to great. China may end up with the widget API market, and may end up serving the Indian markets need for this, oddly enough, but wether they can break the language barrier enough to work directly with english commented and documented code is something I can't predict. It's one of thoise moments where paradigm shift actually means something.