Kevlin Henney addresses the motivation, implications, pros and cons of a craftsmanship view of software development, as well as touching on other metaphors and their implied practices.
John Hughes discusses automated testing techniques that can catch more code defects, with war stories from the likes of Ericsson, Volvo Cars, and Basho Technologies.
Terry Yin explains different programming exercises, outlining the difference in their effectiveness.
Jeff Beck shows how to use Codenarc, Cobertura, JSLint, and other tools to perform static analysis on Grails applications.
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.
Jen Myers discusses the need to make software development attractive and accessible to a larger audience, improving the overall development and learning process in order to have better programmers.
Chris Oldwood discusses what it takes to create robust software: correct error detection and recovery, testing systemic effects, app monitoring and configuration.
Rainer Koschke discusses software cloning – reusing code through copy and paste.
David Craelius tells the story of Klarna building an online payment system in Erlang and their approach to solving the nightmare of technical debt accumulated during a period of fast expansion.
Mike Long describes techniques for managing large legacy restoration projects, using a roadmap, prioritizing technical debt remediation tasks and motivating devs and stakeholders during the process.
Jim Duey surveys several abstraction techniques that can help in writing reusable code in Clojure.