3 ms·
There are some static analyzer metrics as well as metrics you can obtain yourself. These metrics relate to the cost of maintaining code: - cyclomatic complexit
by partycoder 11y ago
There are some static analyzer metrics as well as metrics you can obtain yourself. These metrics relate to the cost of maintaining code:
- cyclomatic complexity
- statement length, function length
- number of singletons / global instances
- dead code
- duplicated code (intelliJ has a good duplicate detector that anonymizes variables and ignores whitespace and comments).
- number of known functions/types per file (coupling)
- number of commits per file (git-effort from git-extras)
Some of them are tricky to obtain. Making a simple script that parses import statements and outputs a DOT file with a digraph is useful to map dependencies, which is good to explain coupling.