Colin Garlick presents a foundation of value for the practice of architecture, starting with the values that architecture is established on, showing what's important for an architecture.
Paul Butcher advises on using concurrency the right way in order to avoid its pitfalls.
Kevlin Henney examines seven coding habits that are not as effective as many programmers — whether working with Java, .NET, native or scripting languages — might believe, and suggests alternatives.
How Can We Use Our Creative Power and Technological Opportunity to Address the Challenges of the 21st Century?
Gyorgyi Galik discusses our urban future and explores new possibilities to create projects and materials that change the environmental effects of art and design practices.
Ian Cooper takes a look at two architectural patterns: pipelines for dealing with streams of data effectively, and events which provide significant advantages for loose coupling.
Aino Corry discusses anti-patterns appearing in retrospectives, providing advice on how to deal with them.
Deepak Nadig discusses how PayPal’s API Platform evolved both internally and externally, the principles and patterns used, and how it is enabling the future of Money.
Garrett Wampole describes an experimental methodology of applying Enterprise Integration Patterns to the near real-time processing of surveillance radar data, developed by MITRE.
This session describes architectural patterns for developing microservices: Service Decomposition, API Gateways, Stateless/Shared-Nothing Apps, Configuration and Backing Service Consumption, etc.
Jutta Eckstein discusses how pedagogical patterns and corresponding tools can help individuals improve themselves, making them better mentors and therefore help their teams improve continuously.
Gareth Rushgrove explores patterns and practices useful to implement continuous integration in an infrastructure-as-code environment.