Something I've learned through my dependency auditing work: "linearly skimming or reading a whole codebase in alphabetical folder/file order" is vastly more effective for understanding a codebase's structure than it has any right to be
@joepie91 Awesome advice. I usually do some weird depth thing, and it's embarrassingly inefficient. I'll try alphabetical next time I need to go code digging.
@KFears I find that depth-wise traversal works pretty well for dense modular code with explicit references, to be fair - but it seems to completely break down in boilerplate-heavy code, do-everything functions, and so on (and those are especially where linear traversal works well!)
My metric for the time being is "does depth-wise traversal annoy me? Then I should switch to linear"
