Becoming a software architect is a longed-for career upgrade for many software developers. While the job title suggests a work day focused on technical decision making, the reality is quite different. Nathaniel Schutta leads a workshop exploring a real-world job description in which communication trumps coding, helping you understand what it means to be a successful architect.
Through lecture and small group exercises, Nathaniel helps you understand what it means to be a successful architect. Working through various problems, you’ll have the opportunity to think through architectural decisions and patterns and discuss the importance of nonfunctional requirements and why architects cannot afford to practice résumé-driven design.
9:00am–10:30am: Introduction—What does it mean to be an architect?
3:30pm–5:00pm: Modeling (cont.)
9:00am–10:30am: Architecting for the “-ilities”
11:00am-12:30pm: Architectural decisions
1:30pm–3:00pm: Leading technical change
3:30pm–4:15pm: Leading technical change (cont.)
4:15pm–5:00pm: Stakeholder management
Nathaniel T. Schutta is a software architect focused on cloud computing and building usable applications. In addition to his day job, he is 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.
©2016, 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