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

[–] deegeese@sopuli.xyz 8 points 5 months ago (1 children)

Get it up and running in a dev environment and start inserting changes to see what breaks where.

Revert and retry until you’ve learned where you’re supposed to be meddling.

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

Another big advantage of getting a dev environment setup is if you can get step by step debugging in place as well. You can then use that to follow the trail of a user action from the UI triggers all the way down.