An architect’s job is to manage complexity, not increase it. Yet the developer life is filled with jargon, acronyms, and seemingly infinite choices. So how do we know when complexity makes sense? Viewers will learn when abstractions are justified and walk away with an understanding of the merits of various approaches for structuring the business, service, presentation and data access layers with a pragmatic, real-world mind set.
Feedback on “Architecting Apps for the Real World in .NET” from Twitter
— Kevin O'Shaughnessy (@ZombieCodeKill) January 12, 2014
— Eric Olsson (@edolsson) August 19, 2015