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.
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.
Andy Hume shares details of the processes and approach used by The Guardian in developing and implementing quality in their front-end software.
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.