@alexdeathway to Experienced Devs • edit-24 months agoWhat's your approach for understanding a big codebase?message-square16arrow-up124arrow-down13file-textstarcopymore-verticalflagCreate ReportslashBlock user
arrow-up121arrow-down1message-squareWhat's your approach for understanding a big codebase?@alexdeathway to Experienced Devs • edit-24 months agomessage-square16file-textstarcopymore-verticalflagCreate ReportslashBlock user
minus-square@[email protected]linkfedilink3•4 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 arrow-up13arrow-down10file-textreply1starmore-verticalmailMessageflagCreate ReportslashBlock user
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