from Hacker News

Evaluate your technical debt with Sonar

by farnulfo on 6/14/09, 7:27 PM with 7 comments

• by jimrandomh on 6/14/09, 9:17 PM

  Software does not have a sense of elegance, and short of a strong AI, it cannot ever have a sense of elegance. The kind of technical debt that matters is mismatches between program abstractions and target domain abstractions. What this does is more like using a spell checker to determine how close a book is to being ready to publish - fundamentally misguided at best.

• by DenisM on 6/14/09, 7:56 PM

  Nice. I would like to see inclusion of the following metrics:

  1. Class coupling - amount of time it takes to grok the code

  2. Build time (full, typical partial etc) - amount of time developer is twiddling his tumbs

  3. Time between checkin, integration tests and end-user tests - amount of time code spent being created but not used, aka "waste" per The Toyota Way

  4. Referential loops in layering diagram - amount of problems that need to be overcome to start refactoring