Adam Tornhill teaches how to predict bugs, detect architectural decay and find the code that is most expensive to maintain, how to evaluate knowledge drain in a codebase, and much more.
The presenters introduce CheckCell, an Excel add-on used to identify cells that have an unusually high impact on the spreadsheet’s computations.
Tal Weiss discusses some essential tools and advanced techniques Java developers can use in their code to debug live servers and resolve errors quickly.
Luís Pina, Luís Veiga, Michael Hicks introduce Rubah, a method for dynamically updating applications running on the JVM.
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.