Stuart Williams shares from experience how his company implemented Kanban, what worked for them in handling maintenance, support and a number of small projects.
Jeff Morgan shares lessons learned helping organization adopt test automation, along with techniques for keeping the automation code simple, clean and maintainable.
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 from already existing code which needs refactoring, maintenance, and sometimes architectural change.
Simon Stewart presents how Google’s Engineering Productivity team and Software Engineers in Test (SETs) help developers to make their code more maintainable, recommending some of their tools.
Robert C. Martin on writing good code starting with a bad code example, then addressing many topics like: Boy Scout rule, functions, arguments, craftsmanship, TDD, engineering, certification, etc.