What's your approach for understanding a big codebase? alexdeathway ( @alexdeathway@programming.dev ) Experienced Devs@programming.dev • edit-24 months ago message-square13fedilinkarrow-up116
arrow-up116message-squareWhat's your approach for understanding a big codebase? alexdeathway ( @alexdeathway@programming.dev ) Experienced Devs@programming.dev • edit-24 months ago message-square13fedilink
minus-square deegeese ( @deegeese@sopuli.xyz ) linkfedilink8•4 months agoGet 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.
minus-square luciole (he/him) ( @luciole@beehaw.org ) linkfedilink4•4 months agoAnother 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.
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.
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.