It’s probably not necessary to print it out, but it’s a great way to establish the discipline for doing it in an IDE/editor. A company I used to work at did co

It’s probably not necessary to print it out, but it’s a great way to establish the discipline for doing it in an IDE/editor. 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.