Dig Below the Surface with Developer Patterns
The main developer analysis is a good starting point, which in turn can drive more detailed investigations. A module with many contributors might still have one main developer who maintains overall consistency while other programmers contribute minor fixes to the code. Or, it could be a shared effort where many different programmers develop significant chunks of the total code.
To get those insights, you’ll use an algorithm that summarizes the number of commits for each developer and presents them together with the total number of revisions for each module. First, look at the raw data, and then you’ll take a step back to see where it comes from:
| | prompt> maat -l react_git_log.txt |
Get Your Code as a Crime Scene, Second Edition, 2nd Edition now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
