BIRT 3.7
Written by: Michael Williams
Featured Refcardz: Top Refcardz:
  1. Scrum
  2. Apache Maven 2
  3. Essential MySQL
  4. Node.js
  5. Groovy
  1. jQuery Selectors
  2. Ajax
  3. Java
  4. Spring Config.
  5. Java Concurrency

Link Details

Link 748209 thumbnail
User 355617 avatar

By piccoloprincipe
via dotnet.dzone.com
Published: Feb 20 2012 / 14:32

In previous articles, Ayende Rahien argued against excessive use of abstractions in .NET applications (or anywhere, really). The reason, in a nutshell: abstraction reduces transparency. Too much infrastructure means that you can't tell what a piece of code is, simply by knowing what it is doing. In this follow-up, he walks through an actual refactoring, explaining in detail how to flatten the architecture of an overly-abstracted app.
  • 8
  • 1
  • 685
  • 794

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.

Voters For This Link (8)



Voters Against This Link (1)