-
Notifications
You must be signed in to change notification settings - Fork 23
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
A nice feature would be some analysis of the available git information #377
Comments
Thanks, @jackson-dean. Great idea. We'll add it to our list for exploration. |
I could imagine us doing something like
|
👍 there is a cli tool that does a lot of this analysis. Note that I have not vetted it for how well it works or anything else https://github.com/adamtornhill/code-maat but it was created to accompany the exercises in the aforementioned book. I imagine it has some nice tricks that could be used for inspiration though. |
None of these are my ideas, they all come directly from the book Software Design X Rays: Fix Technical Debt with Behavioral Code Analysis by Adam Tornhill :)
But it would be super cool to have analysis of what are the “hot” files, or where do we have lots of different people touching the same files which can be broken down to more granular modules, where do we have related changes always happening in tandem indicating tight coupling, among other things.
The text was updated successfully, but these errors were encountered: