InfoQ Homepage Quality Content on InfoQ
-
The Ideal Programmer - Why They Don't Exist and How to Manage Without Them?
Mike Williams outlines some of the main characteristics that make developers and teams perform better than the average.
/presentations/Ideal-Programmer/en/smallimage/Mike.JPG)
-
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)
-
SOLID Clojure
Colin Jones discusses applying the SOLID OOP principles to Clojure programming in order to create systems that are easy to change.
/presentations/SOLID-Clojure/en/smallimage/Colin.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)
-
Nothing Is Permanent Except Change - How Software Architects Can Embrace Change
Michael Stal discusses system architecture quality, how to avoid architectural erosion, how to deal with refactoring, and design principles for architecture evolution.
/presentations/Nothing-Is-Permanent-Except-Change/en/smallimage/Michael.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)
/presentations/From-Crap-to-App/en/smallimage/Lee.JPG)