> It's also important to not traverse files top-to-bottom (which yes, is very tempting). Optimal code traversal is tree-like, you jump from definition to definition, skipping over the irrelevant, and gathering necessary info on demand.

A (successful!) ex-colleague of mine read thousands of lines long files top to bottom.

I don't know how, but somehow this worked for them.