@[email protected] to Experienced [email protected] • edit-26 months agoWhat's your approach for understanding a big codebase?message-square14fedilinkarrow-up122arrow-down13file-text
arrow-up119arrow-down1message-squareWhat's your approach for understanding a big codebase?@[email protected] to Experienced [email protected] • edit-26 months agomessage-square14fedilinkfile-text
minus-square@[email protected]linkfedilink3•6 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
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