Cory Maksymchuk introduces 3 patterns for writing cleaner code: Predicates, Classifiers, and Transformer.
Darius Silingas emphasized the need for quality models in MDD, presenting a number of anti-patterns along with best practices for creating them.
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.
Mike Williams outlines some of the main characteristics that make developers and teams perform better than the average.
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.
Alex Papadimoulis attempts to define ugly code, how one can recognize it, providing advice on avoiding writing such code and refactoring old code to get rid of it.
Colin Jones discusses applying the SOLID OOP principles to Clojure programming in order to create systems that are easy to change.
Nat Pryce considers that we cannot write the perfect code because it is never fully prepared for the coming change, so he suggests embracing impermanence & continual imperfection.
Stuart Halloway shares advice on creating evident code that scales. Evident code is software that clearly expresses its meaning and purpose.
Michael Stal discusses system architecture quality, how to avoid architectural erosion, how to deal with refactoring, and design principles for architecture evolution.