Main Content

Pragmatic Architecture in .NET : Curing the Architecture Astronaut

A talk by Cory House at Codemash 2014

About the Talk

January 9, 2014 10:00 AM

Sandusky, OH

Sandusky, OH

An architect’s job is to reduce 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? We’ll learn when abstractions are justified and discuss how to structure applications so they’re maintainable, scalable, and testable.

We’ll make sure everyone is comfy with the core jargon like N-Teir, separation of concerns, and loose coupling. Then we’ll dive into various patterns for implementing the three common layers: data access, business logic, and presentation. You’ll learn when table module, active record, DDD, and ORMs make sense and walk away with the tools to better evaluate and justify complexity. We’ll focus on the value of keeping things simple whenever we can. Examples are presented in C# in Visual Studio but developers in Java, PHP, and other C-like languages should be able to follow right along.

Ratings and Recommendations

Avg. Rating

Average based
on 1 rating

comments powered by Disqus