Link Details

Offshore development is now commonplace for just about everything from legacy maintenance to enterprise application development. One area where the notion of offshore continues to encounter resistance is product development, as many product managers consider it too risky to develop the “crown jewels” of their organizations in locations that are far removed in terms of both distance and time zones.

Posted by martinig  |   Apr 20 2013 / 02:03

Add your comment


Html tags not supported. Reply is editable for 5 minutes. Use [code lang="java|ruby|sql|css|xml"][/code] to post code snippets.

Comments

User 265881 avatar

Topnotch replied ago:

Every example of offshore development I've seen has been an unmitigated disaster. Routine attributes of a offshore software project: Horrible code, poor english, bad communication, high maintenance, poor reliability, etc. It just costs more than it saves. You actually save money from high-quality local development as opposed to losing money from low quality offshore development. This is enticing only if you are a penny wise and pound foolish bean counter.

Reply 0 votes

Recommended Links

Scala
Written by: Ryan Knight
Featured Refcardz: Top Refcardz:
  1. Apache Hadoop
  2. Play
  3. Akka
  4. Debugging JavaScript
  5. Design Patterns
  1. Apache Hadoop
  2. REST
  3. Java
  4. Git
  5. Java Performance
Connect with DZone