Link Details

Link 1031685 thumbnail
User 722527 avatar

By jim.bird
Published: Sep 14 2013 / 16:53

There are two widely opposed (and often misunderstood) positions on how expensive it can be to change or fix software once it has been designed, coded, tested and implemented. One holds that it is extremely expensive to leave changes until late, that the cost of change rises exponentially. The other position is that changes should be left as late as possible, because the cost of changing software is – or at least can be – essentially flat (that’s why we call it “soft”ware). Which position is right? Why should we care? And what can we do about it?
  • 14
  • 0
  • 1013
  • 1275


Add your comment
User 1180739 avatar

xxx1000 replied ago:

0 votes Vote down Vote up Reply

batch drools

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