minus-squaretomas@lm.eke.litoExperienced Devs@programming.dev•What's your approach for understanding a big codebase?linkfedilinkarrow-up3·5 months agoIf there is git history it’s often a good thing to use that to understand what tends to change together, which parts have lots of churn, etc. There are tools for this: https://github.com/smontanari/code-forensics linkfedilink
If there is git history it’s often a good thing to use that to understand what tends to change together, which parts have lots of churn, etc.
There are tools for this: https://github.com/smontanari/code-forensics