Recent & Upcoming Events

2018

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.

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.

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.

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 inner webs?

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 inner webs?