Garrett Smith introduces Drunken Stumble, a development method in two stages: a lean, which represents the goal of the programmer or team, and a stumble, which is a series of automatic "next steps".
Mike Pearce tells the story of how MOO manages to keep a fresh, startup-like culture that fosters innovation and values collaboration, while still delivering products and looking after its staff.
Jon Skeet keynotes on developers’ passion for their craft, how to find, nurture and enjoy it, how to balance work and life activities, when to step back, and if too much passion can be a problem.
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.
Russ Olsen tells the moon landing story and how it has affected the software development.
Em Campbell-Pretty overviews how to create an Impact Map, sharing real world examples of how impact mapping has helped support the delivery of software products.
Melissa Pierce discusses the history and present of CS culture, gender relations, and tensions between hardware and software engineering.
Sri Viswanath shares the ideas and program driving Groupon’s engineering culture.
Alvin Sng discusses the important engineering aspects of the Resolution Center’s development.
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.
Sid Anand discusses the architectural and development practices adopted by LinkedIn as a continuous growing company.