Rich Hickey once said programmers know the benefits of everything and the trade-offs of nothing…an approach that can lead a project down a path of frustrated developers and unhappy customers. As architects, though, we must consider the trade-offs of every new library, language, pattern, or approach and quickly make decisions often with incomplete information. How should we think about the inevitable technology choices we have to make on a project? How do we balance competing agendas? How do we keep our team happy and excited without chasing every new thing that someone finds on the internet?
As architects, it’s our responsibility to effectively guide our teams on the technology journey. Nathaniel Schutta outlines the importance of trade-offs, how to analyze new technologies, and how to effectively capture the inevitable architectural decisions. Nathaniel also explores the value of fitness functions as a way of ensuring the decisions are actually reflected in the code base.
Nathaniel T. Schutta is a software architect focused on cloud computing and building usable applications. In addition to his day job, he’s an adjunct professor at the University of Minnesota, where he teaches students to embrace dynamic languages. A proponent of polyglot programming, Nate has written multiple books, including Presentation Patterns, with Neal Ford and Matthew McCullough, written to rid the world of bad presentations. He’s also appeared in various videos and is a seasoned speaker, regularly presenting at conferences worldwide, No Fluff Just Stuff symposia, meetups, universities, and user groups.
Comments on this page are now closed.
©2019, O'Reilly Media, Inc. • (800) 889-8969 or (707) 827-7019 • Monday-Friday 7:30am-5pm PT • All trademarks and registered trademarks appearing on oreilly.com are the property of their respective owners. • firstname.lastname@example.org