Experienced Devs

3850 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:

Logo base by Delapouite under CC BY 3.0 with modifications to add a gradient

founded 1 year ago

MODERATORS

[email protected]

What's your approach for understanding a big codebase? (programming.dev)

submitted 3 weeks ago* (last edited 3 weeks ago) by [email protected] to c/[email protected]

14 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

[–] [email protected] 3 points 3 weeks 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