Bryan Helmkamp discusses insights from analyzing over 1T LoC daily, what makes a code metric valuable, when unmaintainable code may be preferable, and what prevents maintaining quality code over time.
The authors introduce Alembic, a new static analysis tool that frees programmers from having to manually move computation to exploit locality in PGAS programs.
Gary McGraw keynotes on the internal forces and relationships active inside companies that drive them to success by managing to take ideas and transform them into technologies.
Jeff Beck shows how to use Codenarc, Cobertura, JSLint, and other tools to perform static analysis on Grails applications.
Paul Grenyer discusses why and how to create a Walking Skeleton - an implementation of the thinnest possible slice of real functionality that we can automatically build, deploy and test end-to-end.
Doug Hiebert discusses the principles and objectives behind automated testing, TDD, Unit and Integration Testing, using asserting and mocking to write tests, and static analysis.
Magnus Robertsson shows how to control the code architecture to avoid an architectural drift leading to a big-ball-of-mud: peer review, code analysis, and zero tolerance to warnings and errors.
Creating secure code requires more than just good intentions. Static source code analysis can be used to uncover the kinds of errors that lead directly to vulnerabilities. Brian Chess shows you how.