Abstract
Developers focus on functional requirements, but once you step into the architect role, your world is increasingly inhabited by the ‘-ilities’—the nonfunctional or quality attributes of a software system. But which ‘-ilities’ matter and which don’t? Nathaniel Schutta explores approaches to architectural problems and explains how to best document the inevitable decisions we arrive at.
)
Nathaniel T Schutta
Software Architect
Nathaniel T. Schutta is a software architect and Java Champion focused on cloud computing, developer happiness and building usable applications. A proponent of polyglot programming, Nate has written multiple books, appeared in countless videos and podcasts. He’s also a seasoned speaker who regularly presents at worldwide conferences, No Fluff Just Stuff symposia, meetups, universities, and user groups. In addition to his day job, Nate is an adjunct professor at the University of Minnesota, where he teaches students to embrace (and evaluate) technical change. Driven to rid the world of bad presentations, he coauthored the book Presentation Patterns with Neal Ford and Matthew McCullough, and he also published Thinking Architecturally and Responsible Microservices available from O’Reilly. His latest book, Fundamentals of Software Engineering, is currently available in early release.