Skip to content


Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP


Add description of what graph means #15

merged 1 commit into from

3 participants


I didn't like having to go look at the article from Michael to figure out how to use the graph I was looking at.

Hopefully he won't mind the "plagiarism". :-)



@chad chad merged commit 1832050 into from
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Commits on Nov 16, 2011
  1. Add description of what graph means

    Mike Gehard authored
This page is out of date. Refresh to see the latest.
Showing with 19 additions and 0 deletions.
  1. +19 −0
@@ -3,6 +3,25 @@ Hopefully-meaningful Metrics
Based on Michael Feathers' [recent work]( in project churn and complexity.
+Here is how to read the graph (extracted from the above article):
+* The upper right quadrant is particularly important.
+These files have a high degree of complexity, and they change quite frequently.
+There are a number of reasons why this can happen.
+The one to look out for, though, is something I call runaway conditionals.
+Sometimes a class becomes so complex that refactoring seems too difficult.
+Developers hack if-then-elses into if-then-elses, and the rat’s nest grows. These classes are particularly ripe for a refactoring investment.
+* The lower left quadrant. is the healthy closure region.
+Abstractions here have low complexity and don't change much.
+* The upper left is what I call the cowboy region. This is complex code that sprang from someone's head and didn't seem to grow incrementally.
+* The bottom right is very interesting. I call it the fertile ground.
+It can consist of files that are somewhat configurational, but often there are also files that act as incubators for new abstractions.
+People add code, it grows, and then they factor outward, extracting new classes. The files churn frequently, but their complexity remains low.
Something went wrong with that request. Please try again.