Nathaniel Schutta | Devoxx

Nathaniel Schutta
Nathaniel Schutta Twitter

From Pivotal

Nathaniel T. Schutta is a software architect focussed on cloud and making usable applications. A proponent of polyglot programming, Nate has written two books on Ajax and speaks regularly at various worldwide conferences, No Fluff Just Stuff symposia, universities, and Java user groups. In addition to his day job, Nate is an adjunct professor at the University of Minnesota where he teaches students to embrace dynamic languages. In an effort to rid the world of bad presentations, Nate coauthored the book Presentation Patterns with Neal Ford and Matthew McCullough.


web Modern Web

Building a Front end Pipeline


Back in the day, it used to be so simple. Our projects had a main.js file that contained a few hundred lines and every so often the corporate communication department would ship out some new CSS files. But now things are not quite so easy. With more and more single page apps containing thousands or hundreds of thousands of lines of JavaScript, we're going to need a bigger boat. In this talk I will explore various options you can deploy on your projects to tame the mass of code that lives on the front end of our applications. From NPM to Gulp to Webpack, this talk will help you establish a front end pipeline.

architecture Architecture

From Developer to Architect

Hands-on Labs

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.