20
What's your approach for understanding a big codebase? (programming.dev)
submitted 5 months ago* (last edited 5 months ago) by alexdeathway@programming.dev to c/experienced_devs@programming.dev
16 comments fedilink hide all child comments

understanding a big codebase you have never worked.

you are viewing a single comment's thread
view the rest of the comments
[-] tomas@lm.eke.li 3 points 5 months ago

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

this post was submitted on 07 Jun 2024
20 points (88.5% liked)

Experienced Devs

3950 readers
1 users here now

A community for discussion amongst professional software developers.

Posts should be relevant to those well into their careers.

For those looking to break into the industry, are hustling for their first job, or have just started their career and are looking for advice, check out:

founded 1 year ago
MODERATORS
snowe@programming.dev
jmk1ng@programming.dev
drewsiferr@programming.dev