|
Isn't it fun examining another developer's code when there isn't much documentation, if any? Happened to me at my workplace when one of my former coworkers just came in for one minute to quit and walk out. I inherited all of this person's applications, and it was tough as hell to figure out what was going on. There was no easy way to dissect what the hell the code was doing. It gets even harder when the code has global variables that are being used in other code files. All I can say is that if you do this often enough, you'll get slightly more accustomed to dealing with other people's code, but it will never be easy, especially if it's spaghetti code or not documented.
Also, if you can figure out what the application/code needs to do, you can either try rewriting it to your heart's content, or add your own documentation to the code. You just need to make sure that all the business logic remains intact if you do happen to rewrite it.
|