Earl Barr, Mark Marron discuss building time-travel debuggers for managed languages, implemented with Tardis, and enabling developers to investigate what happened prior hitting a bug.
Bjorn Freeman-Benson suggests “listening” to the code, refactoring it based on various factors such as the defect rate or underperforming services, providing strategies and tools.
Patrick Smacchia shares code analysis-related practices - structuring code, measuring code quality, automated tests, code contracts, reporting progress, trending- based on his experience with NDepend.
Bodil Stokke keynotes on the FP languages for writing bug free, fault tolerant code that help building simple, concurrent and reusable software.
Crista Lopes discusses if scale affects the internal structure of projects and whether the popularity of libraries is correlated with internal software metrics such as bug density.
Panos Astithas presents some of the debugging, profiling and tracing tools available to web developers today.
Zach Tellman discusses instrumenting and analyzing running systems using real world examples from Factual's production systems.
Daniel Spiewak and Aaron Bedra take a look at code verifying starting with Tony Hoare’s paper on testing(1969), type theory, and language-integrated proof systems.
Joe Walker covers present and future Firefox development tools for editing, inspection, history and control.
Chris Houser discusses stack traces in Clojure and introduces a library for investigating activity across multiple threads and servers, plus a technique for reproducing race conditions.
Bryan Cantrill discusses debugging production systems using post-mortem debugging and dynamic instrumentation, with a bit of history and an introduction to useful debugging tools.
William Pugh explains how to use FindBugs, a Java static code analysis tool, to discover bugs. The talk covers general issues regarding code bugs with advice on how to make sure you get rid of them.