4 ms·

Thanks! We considered looking at Git history - churn is an metric that I've seen in other tools, but I don't have a great intuition for whether it's actually va

by timfsu 4y ago

Thanks! We considered looking at Git history - churn is an metric that I've seen in other tools, but I don't have a great intuition for whether it's actually valuable. I just ran code-maat on the codebase I've been working on, and I'm not sure if it's that useful. Our most touched files are our typedefs, package.json, backend routes, feature flags file, and the sidebar navigation component. These are large files that could be refactored, but I imagine I could've found those just by looking at lines of code. I'm curious if you have any stories of this being helpful?

cratermoon 4y ago
Metrics like churn really need further processing to be most useful. One reason I linked code-forensics tool is that it produces deeper analytics and visualizations. For example, a diagram that shows both how large/complex a file is and how much it's changed is more useful. Another useful report from code-forensics is the knowledge map, which helps gauge ownership by analyzing the number of changes to each file by developer. None these metrics and analysis will give answers, they are raw data to be used as input to thinking about organizational and design issues.