Techniques to read code written by others?
- by Simon
Are there any techniques that you find useful or follow when it comes to reading and understanding code written by others when Direct Knowledge Transfer/meeting the person who wrote the code is not an option.
One of the techniques that I follow when dealing with legacy code is
by adding additional debugging statements and based on the values I figure out the
flow/logic.
This can be tedious at times. Hence the reason behind this question, Are there any other techniques being widely practiced or that you personally follow when it comes to dealing with code written by other people/colleagues/open-source team?