Experienced Devs

3961 readers

5 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

snowe@programming.dev

jmk1ng@programming.dev

drewsiferr@programming.dev

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

[–] MagicShel@programming.dev 9 points 5 months ago (1 children)

Look at the packages. Try to break it down into architectural layers. Understand in a broad sense what each layer adds to the one before. Rage that it wasn't so much architected as cobbled together from pieces never designed to fit together. Decry it as total garbage and recommend total rewrite.

[–] TheButtonJustSpins@infosec.pub 8 points 5 months ago (2 children)

As an advanced technique, you can usually skip the first half of this.

[–] ikidd@lemmy.world 7 points 5 months ago

Everything except last 3 words.

[–] Templa@beehaw.org 4 points 5 months ago

Yes, I'd start from "Rage".