4 ms·
Nice! I'm working on internal tooling for us that does a lot of the same things - gonna buy the book, thanks for that, weird I've never heard about it. For now
by thecupisblue 8y ago
Nice! I'm working on internal tooling for us that does a lot of the same things - gonna buy the book, thanks for that, weird I've never heard about it.
For now I'm measuring: churn, complexity, linting, test coverage, test quality and am going to add a dependency graph.
It seems to me that churn, complexity and dependencies are the biggest indicators of a hotspot.
Got any tips for possible problems I'll encounter along the way?
- nephrenka 8y agoCool - thanks! While the measures a simple in theory, there are some practical challenges; git repositories tend to be messy. So part of the practical challenge is to clean the input data (e.g. filter out auto-generated content, checked in third party libraries). Another challenge is that version-control data is quite file centric, while many actionable insights are on a higher architectural level. In CodeScene we solve this by aggregating files into logical components that can then be presented and scored.
- thecupisblue 8y agoI'm already onto data cleanup, tbh I'm focusing on Android repos for now. But great idea, now that I think of it as an architect I'd mostly like the option to group a few classes/packages or let's call them "modules" together and then visually see which pieces are too dependent on outside sources and which are the hotspots/connections/dependencies inside that group. There goes my weekend...