Main Content

Pragmatic Software Development: Curing the Architecture Astronaut

About the Talk

September 4, 2014 9:15 PM

Omaha, NE

Omaha, NE

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? Let's discuss when abstractions are justified and determine how to structure applications so they’re maintainable, scalable, and testable. In this session we’ll contrast the simplest thing that could possibly work with a more enterprise style architecture and consider the merits of each approach. By contrasting these extremes the benefits of both styles will become clear. We’ll discuss layering, the active record pattern, ORMs, the repository pattern, and service layers and you’ll walk away with the tools to better evaluate and justify complexity as an agile software craftsman. We’ll focus on the value of keeping things simple whenever we can.

Ratings and Recommendations

This Talk hasn't been rated yet. Sign In to rate Talks.

comments powered by Disqus