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.
Jen Myers discusses the need to make software development attractive and accessible to a larger audience, improving the overall development and learning process in order to have better programmers.
Jeff Lawson shares some of the lessons learned in his career and discusses the current trends in software and challenges developers have to face.
Michael Feathers keynotes on the history of programming, what brings joy to this activity and why developers like it.
Neal Ford keynotes on the impact the real world has on software development and the other way around.
David Mortenson details how Facebook maintained efficiency while increasing the number of engineers by reducing the n00b time sink, keeping development fast and avoiding unintended consequences.
Glenn Vanderburg sustains the need for redefining software engineering as the science and art of designing and making systems that can readily adapt to the situations to which they may be subjected.
Jim McCarthy makes a passionate call for developers to rise up to their call and make their software great, sharing their light with the entire world.