Donald Belcham explains how to improve a system’s reliability by using appropriate code patterns.
Ian Barber discusses the importance of behavior, domains and clarity of the names used when writing software or building systems.
Donald Belcham presents design patterns and development concepts that protects one’s code from external systems that may change in uncontrollable ways.
Baruch Sadogursky and Fred Simon discuss the Groovy version of the epic Java Puzzlers.
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.
Chad Fowler attempts to convince people that keeping things "tiny" –small iterations, small methods, small teams - is the best thing one can do for himself and his team.
Martin Fowler keynotes on the need for refactoring and different ways to approach it. You can view here part 2 of this presentation: http://www.infoq.com/presentations/healthy-social-environment.
Jessica Kerr shows the charm of autogenerated test data, the beauty of expressing only what matters, and the challenge of stating what you need without repeating the code under test using ScalaCheck.
In this solutions track talk, sponsored by Caplin Systems, Phil Leggetter discusses concepts for writing structured and maintainable code for single-page web applications with HTML5 and BladeRunnerJS.
Ann Robson discusses how to develop standards, approach refactoring in a safe and practical way, and track the evolution of a code with tools and metrics.
Jack Singleton discusses how to improve code readability and maintainability in Scala, and how to be productive with Options, Immutability, and the Collections library.
Viktor Klang discusses approaches to writing software without building a complex, full of bugs and hard to maintain basecode.