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.
Tomer Sharon discusses the psychology of attitude & behavior and shares tips for conducting a high-quality, impactful, and fast UX research.
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.
Michael Feathers advices on creating an organizational process and culture that can enhance software development in a way that reduces technical debt.
Christof Ebert discusses technical debt including a Netscape vs. IE case study and provides a framework with practices for managing technical debt.
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.