Link Details

What happens to code over time, and what should happen to it? What does a healthy, long-lived code base look like? What architectural decisions have the most lasting impact, and what decisions made early will make the most difference over the life of a system?

Posted by jim.bird  |   Oct 12 2012 / 04:17

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.

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