Ingo Rammer shares 15 tips regarding people, complexity and technology that he learned doing software architecture for 15 years.
Graham Lee discusses some of the vulnerabilities that may affect Objective-C programming, offering solutions to avoid them.
Jesper Boeg shares his experience, lessons learned, failures, and common problems met when introducing Kanban to various teams having no previous Agile or Lean experience
Phil Trelford suggests domains, such as modeling, DSLs, concurrency, for which functional programming is well-suited, and areas for which an OO or a mixed approach has better results.
Eoin Woods shares some of his architectural experience along with principles and techniques useful when working with legacy systems.
George Fairbanks stresses the importance of having a good grasp of various conceptual models in order to be a master-builder, translated into development as “learn your software architecture”.
Talk #1: Stefan Edlich suggests choosing a NoSQL DB after answering about 70 questions in 6 categories, and building a prototype. Talk #2: Edlich presents NewSQL solutions counteracting NoSQL.
Rich Hickey compares value-oriented programming with place-oriented programming concluding that the time of imperative languages has passed and it is the time of functional programming.
Don Reinertsen outlines the need for using an economic model for development, explaining what that is emphasizing the cost of delay, how an economic model looks like, how to build and use one.
Benjamin Mitchell advices on carrying team conversations about information presented on Kanban boards helping members to change their thinking and acts in order to achieve evolutionary change.
Adrian Howard addresses misconceptions that may affect the designer-developer relationship, detailing 6 principles helping UX designers better integrate into Agile teams.
Yves Reynhout discusses event sourcing and storage, demoing implementing a conceptual event storage model on top of AWS Storage and Azure Storage Services.