Leslie Lamport makes the case for separating the design details of what a program should do and how it should work from the business of writing code, and discusses how the design process should work.
Pawel Brodzinski focuses on the importance of having a correct mindset and understanding the context rather than blindly following some methods.
Jessica Kerr explains through Java and C# code samples six principles of the functional programming style.
Josh Wexler takes participants through the Idea Stack exercises and use case studies, illustrating how to build a vision for a product before developing it.
Eric Evans shares approaches that have helped him with issues in architecture, with a focus on establishing boundaries between software with different conceptual approaches and discipline levels.
Phil Nash presents how NEAT (Non-Exercise Activity Thermogenesis), its relationship with to sitting, standing and walking, and the chemistry behind it helps being fit for long schedules.
A lively panel discussion with Eric Evans, Duncan DeVore, and Leo Gorodinski, hosted by Mike Feathers, on software architecture improvement, DDD, the ins and outs of microservices and much more.
David Nolen introduces Om, a ClojureScript library that adds a functional layer on top of Facebook React, providing OO abstractions in a MVC environment.
Gerard Meszaros advises on using the right abstraction level and automation tools when creating unit or system-level tests.
Glen Ford discusses how Zeebox applies and refines Lean: methods, experiments, discovery and feature teams, cultural challenges, innovation, etc.
Michael Dowden introduces JMeter and explains how to develop a data-driven methodology to determine some of the limits of a web application: max number of concurrent users, bottlenecks, etc.
Damian Conway discusses what regexes really are, how they actually work, and how programmers can make use of their existing software development skills to construct correct and efficient regexes.