Sid Anand discusses the architectural and development practices adopted by LinkedIn as a continuous growing company.
Josh Knowles shares thoughts on the strong engineering culture which has made the Pivotal Labs team successful, taking a look at how things have evolved over the past 20 years.
Douglas Crockford discusses how to use programming languages more effectively; reviews the good parts in EcmaScript 6 and JSON.
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
Dan North describes some of the many facets of craftsmanship using examples of mastery from various fields and tries to figure out exactly what is programmers’ craft.
Corinna Brock discusses the place of women in software development, how to be a minority, how to increase their number and how to keep the current ones.
Didier Verna keynotes on the bonds between biology and computer science, how these bonds developed over the years, and how software could behave like living organisms.
Christopher Simons suggests using SBSE to iterated through multiple possible solutions and select the one that performs the best, offering insight into some available tools and techniques.
Tom Stuart uses code to tell a maths-free story about the source of a computer's power, the inevitable drawbacks of that power, and the impossible programs which lie at the heart of uncomputability.
Kent Beck addresses several questions: Why are programmers so often ill at ease with themselves? What can we do to become comfortable in our own skins? What might happen as a consequence?
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.
Chad Fowler keynotes on practicing joy as a software developer, starting from his life experiences and concluding that joy is intrinsic while happiness requires discipline.