alexdeathway@programming.dev to Experienced Devs@programming.dev · edit-25 months agoWhat's your approach for understanding a big codebase?message-squaremessage-square14fedilinkarrow-up123arrow-down13file-text
arrow-up120arrow-down1message-squareWhat's your approach for understanding a big codebase?alexdeathway@programming.dev to Experienced Devs@programming.dev · edit-25 months agomessage-square14fedilinkfile-text
minus-squaretomas@lm.eke.lilinkfedilinkarrow-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
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