Jack Singleton discusses how to improve code readability and maintainability in Scala, and how to be productive with Options, Immutability, and the Collections library.
Adrian Smith covers symptoms, root problems and guidance on recommended solutions for avoiding automated testing mistakes.
Mike Falanga shows several C# and F# solutions to common programming problems, comparing how well each language enhances the ability to draw accurate conclusions about the code.
The panelists discuss if code generation techniques help or hinder long-term software maintenance, and how such techniques can be integrated in the maintenance process.
Paul Fremantle introduces Stratos/Stratos Live, explaining some of the design decision made for it, the tenancy model used, and some of its capabilities.
Ralph Johnson discusses principles, practices and tools relating to software development starting not from scratch but from already existing code which needs refactoring, maintenance, and sometimes architectural change.
Simon Stewart presents the activity of Google’s Engineering Productivity team and the role Software Engineers in Test (SETs) play in helping software developers to make their code more maintainable, recommending some of their tools: Gold linker, Eclipse, distcc, JDepend, graphviz.
Robert C. Martin, during his keynote at QCon London 2010, tried to figure out why there is so much bad code written. He offers advice on writing good code talking about a bad code example, Boy Scout rule, functions, arguments, craftsmanship, TDD, continuous integration, pairing, small cycles, patterns, engineering, certification, and other elements contributing to qualitative code.