2 ms·
Great points Also, A list of the kinds of broad abstractions to look for might be useful; * Each module and it's purpose * Every global resource (whether glo
by joe_the_user 11y ago
Great points
Also,
A list of the kinds of broad abstractions to look for might be useful;
* Each module and it's purpose
* Every global resource (whether global variables, message names, anything that the entire system has to deal with).
* The "style" that each coder used. Even "terrible" programmers tend to have a consistent approach and understanding that approach can make code much less opaque.
I also like to page though documents more quickly than my conscious mind can follow so as to get an unconscious feel for a code base. That might be just me.