Thinking

From Developer to Software Architect

Cloud Native Pittsburgh

QCon New York 2018

Devoxx Poland 2018

Thinking Architecturally Book

I’m very excited to announce my latest book project, Thinking Architecturally, is now available! My thoughts on being an architect, dealing w/ change, etc. If you’ve attended one of my talks in the last few years, you will recognize some of the material. The reception has been beyond my expectations and I am delighted by the responses I’ve received from people that have read the book. If you are interested in perusing the material, it is a free download from the Pivotal Resource center.

Thinking Architecturally Is Available

I’m very excited to announce my latest book project, Thinking Architecturally, is now available! My thoughts on being an architect, dealing w/ change, etc. If you’ve attended one of my talks in the last few years, you will recognize some of the material. The reception has been beyond my expectations and I am delighted by the responses I’ve received from people that have read the book. If you are interested in perusing the material, it is a free download from the Pivotal Resource center.

&& ! ||

Full Abstract Software developers are seemingly on a perpetual path to discover the one true technology to unite them all. And yet there are no golden hammers, there is no one size fits all solutions. Instead we have to carefully weigh the pros and cons of our options and in some instances take the least worst approach. Rather than continue down this trail of disappointment, we need to embrace the and not the or.

Architect as Storyteller

Full Abstract Nathaniel Schutta explains why an architect’s job is to be a storyteller. 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). The challenge lies in not only crafting a compelling message but doing so for wildly disparate audiences. (The pitch you give your developers will not go over well with the executives, for instance.

Developer To Architect

Full Abstract 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. In this workshop, software architect Nathaniel Schutta constructs a real world job description in which communication trumps coding. Discover the skill sets needed to juggle multiple priorities, meetings, and time demandsLearn why your best team leadership tool is not a hammer, but a shared cup of coffeeHear the best ways to give and take criticismUnderstand the necessity of writing effective email and formal architecture documentsGet tips for delivering confident career-building presentations to any audienceReview essential techniques for stakeholder management and relationship buildingExplore the critical needs for architecture reviews and an effective process for conducting themThrough lecture and small group exercises, Nathaniel will help you understand what it means to be a successful architect.

Architecting for the ilities

Full Abstract As a developer, your focus was squarely on the “functional requirements” aka the business capabilities your application must meet. But once you step in the architect role, you discover a world inhabited by “the ilities” otherwise known as the non functional or quality attributes of a software system. But how do we know which ilities matter and which ones don’t? And much as we may want to turn every knob up to 11, many ilities are inversely related - maximize one and you by definition minimize another.