InfoQ Homepage Code Quality Content on InfoQ
-
Surviving Big JavaScript Projects
Anton Kovalyov provides an inside look into a large JavaScript project, presenting techniques for maintaining code quality while allowing the team to push lots of changes every day.
-
Robust Software - Dotting the I's and Crossing the T's
Chris Oldwood discusses what it takes to create robust software: correct error detection and recovery, testing systemic effects, app monitoring and configuration.
-
Similarity in Software Artifacts and Its Relation to Code Generation
Rainer Koschke discusses software cloning – reusing code through copy and paste.
-
Engines of Abstraction
Jim Duey surveys several abstraction techniques that can help in writing reusable code in Clojure.
-
Keynote: 8 Lines of Code
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.
-
Writing Usable APIs in Practice
Giovanni Asproni expands upon the idea that usable APIs help writing clean code.
-
Legacy Code: Using Domain-Driven Design to Carve Out Areas of Sanity
Robert Reppel discusses applying DDD and SOLID techniques in order to improve legacy code, exemplifying with real code.
-
The FT Web App: Coding Responsively
Rob Shilston discusses the need for coding responsively, not just designing responsively, along with the development process in place at Financial Times.
-
3 Patterns for Cleaner Code
Cory Maksymchuk introduces 3 patterns for writing cleaner code: Predicates, Classifiers, and Transformer.
-
Software for Your Head
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.
-
Entirely Predictable Failures
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.
-
Beauty is in The Eye of the Beholder
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.