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.
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.
Jim Duey surveys several abstraction techniques that can help in writing reusable code in Clojure.
Greg Young discusses eight lines of very common code finding in them massive numbers of dependencies and difficulties, looking for ways to get rid of them.
Giovanni Asproni expands upon the idea that usable APIs help writing clean code.
Robert Reppel discusses applying DDD and SOLID techniques in order to improve legacy code, exemplifying with real code.
Rob Shilston discusses the need for coding responsively, not just designing responsively, along with the development process in place at Financial Times.
Cory Maksymchuk introduces 3 patterns for writing cleaner code: Predicates, Classifiers, and Transformer.
Jim McCarthy makes a passionate call for developers to rise up to their call and make their software great, sharing their light with the entire world.
Poul-Henning Kamp considers that if developers are not getting better, we are going to repeat many of the major IT project failures. He exemplifies with major Denmark project failures.