To vote on the idea, please sign in with your personal or social account (Facebook or Google).
To watch the idea, please sign in with your personal or social account (Facebook or Google).
As an architect I constantly look for painpoints on the code base.
It would be extreamly convinient to find the Top XX (40?) files that has changed in a given repository and displayed it grapchically.
Now that information will give me some insight, but even better would be to take that top 40 and have a graph for each file and see if a file (or package for that sake) have changed frequently over a longer period of time.
Lets say I have a file that is constantly changing over a longer period of time this is an indication that this file
- Either containts a lot of bugs
- is Subject for frequent change and could/Should be refactored so new functionality can be put in different classes (Single responibility)
Same graph would be great if we could have a grapt of top files that are part of checkings related to bugs/issues
Again a file that is "part" of several bugs is worth looking at.
Last but not at least it would be great to have a graph over files that has not! changed for a long time.
This code is either verry stable (well worth investing the time to document) or not in use (can be deleted)