InfoQ Homepage Code Quality Content on InfoQ
-
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.
/presentations/Predictable-Failures/en/smallimage/Poul.JPG)
-
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.
/presentations/Ugly-Code/en/smallimage/Alex.JPG)
-
Building Rich User Experiences without JavaScript Spaghetti
Jared Faris provides 3 principles –decouple everything, make it testable, push events not state – and some patterns which help avoiding creating JavaScript spaghetti code over time.
/presentations/UX-JavaScript-Spaghetti/en/smallimage/Jared.JPG)
-
Stop Refactoring!
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.
/presentations/Stop-Refactoring/en/smallimage/Nat.JPG)
-
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)