InfoQ Homepage Code Quality Content on InfoQ
-
Software Naturalism - Embracing the Real Behind the Ideal
Michael Feathers analyzes real code bases concluding that code is not nearly as beautiful as designers aspire to, discussing the everyday decisions that alter the code bit by bit.
/presentations/Software-Naturalism-Embracing-the-Real-Behind-the-Ideal/en/smallimage/Michael.JPG)
-
Beauty Is in the Eye of the Beholder
Alex Papadimoulis discusses ugly code, where it comes from, how to avoid it, and how to get rid of it.
/presentations/Beauty-Is-in-the-Eye-of-the-Beholder/en/smallimage/Alex.JPG)
-
How to Stop Writing Next Year's Unsustainable Piece of Code
Guilherme Silveira mentions some of the turning points in project development that may affect the quality of the code offering advice on avoiding writing crappy code.
/presentations/How-to-Stop-Writing-Next-Years-Unsustainable-Piece-of-Code/en/smallimage/Gui.JPG)
-
Stop the Software Architecture Erosion
Bernhard Merkle advices on preventing architectural degradation of a project by using tools for constant monitoring of the code, exemplifying with an analysis of Ant, Findbugs and Eclipse.
/presentations/Stop-the-Software-Architecture-Erosion/en/smallimage/Bern.JPG)
-
Infinitely Extensible
Alex Papadimoulis discusses avoiding over-engineering a program, presenting extensibility types used, extensibility design patterns, when to use them, and what happens when they are incorrectly used.
/presentations/Infinitely-Extensible/en/smallimage/Alex.JPG)
-
Compile-time Verification, It's Not Just for Type Safety Any More
Greg Young talks about .NET’s Contracts library, showing how to use it, what it is good for, and how it improves code quality.
/presentations/Contracts-Library/en/smallimage/Greg.JPG)
-
Where Did My Architecture Go?
Eoin Woods advices on writing code that preserves the initial architectural design using conventions, dependency analysis, module systems, augmenting the code & checking rules, and language extensions
/presentations/Where-Did-My-Architecture-Go/en/smallimage/woods.JPG)
-
Five Static Code Audits Every Developer Should Know and Use
Mike Rozlog discusses the need for software audits, proposing five code reviews that every developer should use: Numerical Literal, String Literal, god Method, Shotgun Surgery and Duplicate Code.
/presentations/Five-Static-Code-Audits/en/smallimage/305.JPG)
-
Living and Working with Aging Software
Ralph Johnson discusses principles, practices and tools relating to software development starting from already existing code which needs refactoring, maintenance, and sometimes architectural change.
/presentations/Working-with-Aging-Software/en/smallimage/johnson.JPG)
-
The DCI Architecture: Lean and Agile at the Code Level
James Coplien explains the DCI paradigm used to better represent the user’s mental model through code, proposing a way of reintroducing architecture back to Lean and Agile projects.
/presentations/The-DCI-Architecture/en/smallimage/dci.JPG)
-
Scrub & Spin: Stealth Use of Formal Methods in Software Development
Gerard Holzmann discusses Spin, a design analyzer tool, and Scrub, a code review tool, used by Jet Propulsion Laboratory to analyze and fix the software used for solar system exploration missions.
/presentations/Scrub-Spin/en/smallimage/holzmann.JPG)
-
Sustainable Test-Driven Development
Steve Freeman offers advice on writing good tests that make development easier avoiding dead weight code that is hard to maintain. Topics: readability, complex data, diagnostics, and flexibility.
/presentations/Sustainable-Test-Driven-Development/en/smallimage/SteveFreeman.png)