Archives / 2016 / February
  • DTO Organization in vNext API's

    So lets face it, projects are getting more complicated, with more and more objects to keep track of.  If you follow any type of agile process you're often creating an object per operation with the hopes that your technical debt will allow you to reactor the dupes later.  If you're following a DRY principle or a seperation of concerns it can open add layers of abstraction that confuse your object graph even more.