@alexdeathway@programming.dev to Experienced Devs@programming.dev • edit-21 year agoWhat's your approach for understanding a big codebase?message-square16arrow-up125file-text
arrow-up125message-squareWhat's your approach for understanding a big codebase?@alexdeathway@programming.dev to Experienced Devs@programming.dev • edit-21 year agomessage-square16file-text
minus-square@deegeese@sopuli.xyzlinkfedilink8•1 year 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-squareluciole (he/him)linkfedilink5•1 year 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.