alexdeathway@programming.dev to Experienced Devs@programming.dev · edit-25 months agoWhat's your approach for understanding a big codebase?message-squaremessage-square16fedilinkarrow-up123arrow-down13file-text
arrow-up120arrow-down1message-squareWhat's your approach for understanding a big codebase?alexdeathway@programming.dev to Experienced Devs@programming.dev · edit-25 months agomessage-square16fedilinkfile-text
minus-squaredeegeese@sopuli.xyzlinkfedilinkarrow-up8·5 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-squareluciole (he/him)@beehaw.orglinkfedilinkarrow-up4·5 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.