Link Details

Link 957113 thumbnail
User 219636 avatar

By martinig
Published: Apr 20 2013 / 02:03

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.
  • 6
  • 3
  • 761
  • 1197
User 265881 avatar

Topnotch replied ago:

0 votes Vote down Vote up Reply

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.

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.

Apache Hadoop
Written by: Piotr Krewski
Featured Refcardz: Top Refcardz:
  1. Play
  2. Akka
  3. Design Patterns
  4. OO JS
  5. Cont. Delivery
  1. Play
  2. Java Performance
  3. Akka
  4. REST
  5. Java