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.
- Prairie Developer Conference 2015
- Prudential IT Talks – Des Moines 2014
- Heartland Developer Conference 2014
- DevLink 2014
- Kansas City Developers Conference 2014
- Codemash 2014 – Rate this talk
- AJi Software Geek Lunch 2.20.14
- Kansas City Developers Conference 2013 – Rate this talk
- St. Louis ALT.NET User Group
- CodeStock 2013 – Rate this talk
- Topeka .NET user group
- Iowa Code Camp Fall 2013 – Rate this talk
- Iowa .NET User Group
- Kansas City .NET User Group
- St. Louis Days of .NET 2014
What are people saying?
— Aaron Bauman (@AirN5475) January 10, 2014
— Mike Cole (@colemike) November 2, 2013
— Greg Hale (@bcowl03) July 13, 2013