It's an interesting metric, the "churn" or "hot spots" in code. Why do certain areas and not others exhibit high churn? I had a quick look through the codebase

It's an interesting metric, the "churn" or "hot spots" in code. Why do certain areas and not others exhibit high churn? I had a quick look through the codebases showcased on the CodeScene site, and across them, the files with most churn tend to have quite generic names (like core, daemon, helper, internalEngine, etc). It sort of supports my intuitive take on the answer: the "churniest" areas of the code are the ones that were initially difficult to think of in specific terms, ie, the ones that don't tend to implement one thing, but boundaries between things. They're the catch-alls, the areas where our conceptual abstractions don't fold together as neatly as we'd like.