Bruce Eckel reviews some of the ideas and practices of the development community, outlining patterns of the problems related to communication, organization, process, etc. it has been trying to resolve
Dave Farley introduces the ideas of Continuous Delivery as a practical everyday, holistic process, using some of the techniques and technologies from a real world project as an example.
David Hussman combats the addiction to a specific process, discussing various topics such as product thinking, regression deficit, building teams and connecting programs to portfolios.
Dana Caulder discusses how to improve team communication and delivery, aligning processes and tooling for iterative improvement, processes to mitigate team member turnover and speed-up onboarding.
Greg Brockman shares Stripe's principles powering their software projects and the culture instilled to avoid the usual software engineering traps: failed rewrites, delayed timelines, etc.
The panelists discuss if code generation techniques help or hinder long-term software maintenance, and how such techniques can be integrated in the maintenance process.
Juan Manuel and Jesús López González share their experience gathered over five years designing and implementing Speech, a DSL for programming social processes.
Alan Griffiths shares the organizational process, the technological challenges and the solutions adopted by a team developing a C++ systems component.
Andy Hume shares details of the processes and approach used by The Guardian in developing and implementing quality in their front-end software.
Jeff Patton presents the process of co-creating products, where everyone is involved and responsible, taking examples from three companies he’s worked with.
Roy Clarkson and Gunnar Hillert present how GitHub, Gradle, and Artifactory are used to upgrade Spring’s infrastructure and processes.
Jez Humble addresses the most important factors in implementing continuous delivery: organizational, architectural and process.