Rich Smith discusses the progressive approaches taken by the Etsy security team to provide security while not destroying the freedoms of the Etsy engineering culture that are loved so much.
Alison Lloyd examines some less-than-stellar occurrences in non-software fields, drawing out some ideas that she hopes will make software development a little less painful.
How Did We End up Here? 50:22
Trisha Gee and Todd Montgomery attack the technology industry’s sacred cows by exposing the motivations that hide behind them.
Pete Goodliffe keynotes on what it takes to become a better programmer, discussing tools for reviewing the personal skillset and techniques to help one “become a better programmer”.
Randy Shoup discusses several important aspects of engineering cultures: hiring and retention, ownership and collaboration, quality and discipline, and learning and experimentation.
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.