@alexdeathway@programming.dev to Experienced Devs@programming.dev • edit-21 year agoWhat's your approach for understanding a big codebase?message-square16arrow-up125file-text
arrow-up125message-squareWhat's your approach for understanding a big codebase?@alexdeathway@programming.dev to Experienced Devs@programming.dev • edit-21 year agomessage-square16file-text
minus-square@tomas@lm.eke.lilinkfedilink3•1 year 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