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.
Adam Rocska discusses how to approach an enterprise web front-end architecture, including quality assurance, code documentation, deployment, architectural planning and task delegation.
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.
Jon Skeet provides practical advice on designing APIs using immutability, separation of concerns and other principles, resulting in elegant and reusable code.
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.
Emma Langman explores the usefulness of some of the Quality tools that have been around since the 50s for gathering requirements, tackling repeat problems, or innovating more efficiently as a team.
Barb Spurway, Tracy Bowman discuss Voice of the Customer (VoC), a Total Quality Management/ Lean Manufacturing concept helping teams build quality products from the customers’ perspective.
Nat Pryce, Steve Freeman advise on design principles useful to create code structures with objects that fit together and communicate, and where the capabilities and the information flow are explicit.
Doug Hiebert questions conventional wisdom that is taken for granted when writing code, and presents alternatives by way of before-and-after examples.