The Center for Technology Innovation sponsors a series of day-long workshops on cutting-edge technology issues with nationally-known speakers.
Software developers often long to upgrade their careers by becoming software architects. But many don't realize that although the job title suggests a work day focused on technical decision making, the reality is quite different. Over two days, Nathaniel Schutta details the skills you need for success in the real world, where communication trumps coding, as he walks you through what it means to be a successful architect.
Cover the full scope of software architecture
In this episode of the O’Reilly Programming Podcast, I talk with Nathaniel Schutta, a solutions architect at Pivotal, and presenter of the video I’m a Software Architect, Now What?. He will be giving a presentation titled Thinking Architecturally at …
Architects are essentially the Rosetta Stone of an organization, providing translation services (or, as some would call it, the elevator between the executive suite and the development floors).
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? …
Being a software architect is more than just possessing technical knowledge. It’s about thinking like an architect, being a leader, and understanding the architectural elements, patterns, and styles necessary to create effective software …
Ford and Schutta offer concrete instruction in how to plan your presentation, handle a wide variety of presentation types, manage your audiences, and deal with constraints and surprises.