Code Evolution
What keeps changing in your codebase? Let's look at the Git history and find out.
I think commit history is one of the most useful sources of architectural evidence we already have.
These ten analyses help me to see the possible unhealthy patterns in the codebase. It show which files change most, which parts move together, who owns key areas, how changes reach production, and where complexity is building up.
They can act as architectural fitness functions. It's a feedback loop for understanding where the design is holding up under pressure.
These metrics help diagnose what is happening in the codebase. However, be aware of Goodhart's Law:
"When a measure becomes a target, it ceases to be a good measure."
Use the results to start a conversation. A hotspot may be important work or a knowledge silo may reflect healthy ownership.
If you want the background behind these techniques, see my a bit nerdy page about Code Behavior Analysis