alexdeathway to Experienced Devs · edit-21 year agoWhat's your approach for understanding a big codebase?message-squaremessage-square16linkfedilinkarrow-up125arrow-down13file-text
arrow-up122arrow-down1message-squareWhat's your approach for understanding a big codebase?alexdeathway to Experienced Devs · edit-21 year agomessage-square16linkfedilinkfile-text
minus-squaretomas@lm.eke.lilinkfedilinkarrow-up3·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