Is there a good way to map out the process of code?

Posted by QuitTypical3210@reddit | ExperiencedDevs | View on Reddit | 18 comments

Usually, I just copy the links from the repo with the lines of code and sort of make a list of how code map together. But it’s mess and gets hard to look back onto.

But I’m wondering if there is a better way to do this? Basically wanted to map out how a specific legacy feature works such as how the code interacts over services, the if/else, and where it gets information from. Starting from the UI, through the UI internals all the way down to the services. Since just looking at the code is a total nightmare.

Main reason for doing this is it to ensure I’m not missing any “extra” changes that occur to the information being used and that I’m not missing anything.