What is the way to understand someone else's giant uncommented spaghetti code? [closed]
- by Anisha Kaul
Possible Duplicate:
I’ve inherited 200K lines of spaghetti code — what now?
I have been recently handled a giant multithreaded program with no comments and have been asked to understand what it does, and then to improve it (if possible).
Are there some techniques which should be followed when we need to understand someone else's code? OR do we straightaway start from the first function call and go on tracking next function calls?
C++ (with multi-threading) on Linux