DEV Community


Posted on

Strategies to understand codebase ?

The ability to understand a codebase is really helpful when one is trying to make tweaks/develop the underlying code. Ideally, repos have good documentation to guide the interested developer but for the most part, this may not necessarily exist.

Therefore, given a GitHub repo, what's a good strategy to understand (in broad strokes) the structure of the code?

Top comments (1)

polterguy profile image
Thomas Hansen

Start with the folder structure. If it's bad it's probably not worth understanding ... :/