InfoQ Homepage Code Quality Content on InfoQ
-
Evident Code, at Scale
Stuart Halloway shares advice on creating evident code that scales. Evident code is software that clearly expresses its meaning and purpose.
/presentations/Evident-Code-at-Scale/en/smallimage/Stuart.JPG)
-
Effective Use of FindBugs in Large Software Development Efforts
William Pugh explains how to use FindBugs, a Java static code analysis tool, to discover bugs. The talk covers general issues regarding code bugs with advice on how to make sure you get rid of them.
/presentations/Effective-Use-of-FindBugs/en/smallimage/Bill.JPG)
-
Software Quality - You Know It When You See It
Erik Dörnenburg shares techniques for estimating code quality by collecting and analyzing data using the toxicity chart, metrics tree maps, size&complexity pyramid, complexity view, code city, etc.
/presentations/Software-Quality-You-Know-It-When-You-See-It/en/smallimage/Erik.JPG)
-
Who Ever Said Programs Were Supposed to be Pretty?
Brian Foote wonders in this session if the quest for clean or beautiful code makes sense in a bottom-line obsessed business world.
/presentations/Who-Ever-Said-Programs-Were-Supposed-to-be-Pretty/en/smallimage/Brian.JPG)
-
Sufficient Design: Quality In Sync With Business Context
Joshua Kerievsky invites developers to start thinking as entrepreneurs, writing code that is “good enough” for the purpose it is supposed to serve rather than write elaborate code that is beautiful.
/presentations/Sufficient-Design/en/smallimage/Josh.JPG)
-
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)