“At one point or another, every developer has looked at a piece
of code and said aloud (or to themselves), ‘This is crap.’ Until
now, however, the definition of what actually constitutes bad code
has not been an exact science with a proper formula or
analytics.“Thanks to the efforts of Alberto Savoia, founder and CTO of
Agitar Software, there is now a statistical measure to monitor Java
code. Called crap4j, CRAP is an acronym for Change Risk Analyzer
and Predictor…”