Tom Gilb keynotes on 10 key Agile principles: Control projects by quantified critical-few results, Give developers freedom, Estimate the impacts of your designs, Involve the stakeholders, etc.
Roy Rapoport shares some of the lessons Netflix learned building a monitoring system, the challenges, pitfalls and opportunities encountered along the way.
John Wilkes shares lessons learned managing clusters at the scale of Google.
Enyo Kumahor shares software development stories from the African continent.
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.
Christophe Grand tells Clojure stories full of immutability, data over behavior, relational programming, declarativity, incrementalism, parallelism, collapsing abstractions, local state and more.
Russ Olsen tells the moon landing story and how it has affected the software development.
Chad Fowler attempts to convince people that keeping things "tiny" –small iterations, small methods, small teams - is the best thing one can do for himself and his team.
Peter Norvig keynotes on using machine learning techniques to solve more general software problems, helping both the advanced programmer and the novice one.
Jack Strong introduces the Deming Cycle - Plan, Do, Check, Action (PDCA)-, along with techniques for team building, brainstorming and prioritization.
Greg Young advises understanding the pros and cons of a system’s concepts and environments in order to avoid oscillating between options or choosing the wrong ones.
Mike Atherton keynotes on aligning work with values to get most benefits from it, to be proud of the results and to make a difference.