Print out your code. On paper

I do think there is merit to looking at code outside of an IDE (for the sake of keeping yourself focused on the task at hand), but that's what a typical code review provides.

Maybe a process like this is good for looking at "bad" code and theorizing how to improve it. But even then a lot of my problems span multiple files and multiple modules (and I don't suspect I am alone in this) so it seems inefficient to print all of that out.

A company I used to work at did code reviews this way, we printing out pages of code and go through it in a meeting room with multiple reviewers. It could be overkill for binary deliverables, but when the deliverables included source code it really forced you to focus on it, having no other distractions.

In an IDE you’d go-to-definition on a symbol, maybe get distracted, start reviewing some other file, a refactor here or there, and before you know it you’re down a rabbit hole and have lost context on what you were initially reviewing. On paper you have to mark it to come back to later, and continue the rest of the review.

Also, going through big blocks of code on paper in stead of a screen is easier on the eyes.