Do programmers still print code to review?

Question

Back in the day, programmers used to print code out on continuous form green and white paper.It seems like this has mostly fallen out of fashion. I wonder if eyeballs on code not on a screen might have been useful in spotting bugs?

throwthat1 · Accepted Answer

Hope not

mtmail · Answer

Green and white paper was a long time ago. As soon as I had a laptop and mobile internet connection I stopped printing code. I remember printing with syntax highlighting was hard (company had only black&white laser printers).

tjr · Answer

One reason that I used to print out code for review was so that I could take a bunch of code somewhere else away from my desk, such as to a coffee shop or to a more comfortable chair. With lightweight, high-resolution laptops and tablets, this is much less of an issue than it used to be.
Though sometimes I do prefer to read offline altogether, but it's probably been something like 5+ years since I last printed out code to review away from my desk.
Was it more useful for spotting bugs? Maybe some kinds of bugs. If all you have to look at is the printout in front of you, you might be inclined to read and think about it more deeply than you might have otherwise, with the full capabilities of your computer at the ready. On the computer, I might more easily focus on, Does it compile? Does it run? Does the output look right on the screen? But when all you have is the code, my thoughts might tend more toward, Does this theoretically make sense?

yuppie_scum · Answer

Why would you do that when you can send a Git link which can be commented, tracked, given proposed edits, etc..

jamesfinlayson · Answer

I remember seeing this in a video once but never in real life. As others have alluded to, doing it on a computer has its benefits - you can check the documentation for a given function call for example (and see that all different possible error codes are handled or whatever).

JoeMayoBot · Answer

I recall this being necessary on older main frame systems where monitors either didn't exist, there was limited time on a shared console, or you didn't have access at all. However, once we had networks and workstations/PCs there was a decreasing need for paper. I believe that elimination of paper was a long-time goal and good for the environment. As far as code review goes, we have IDE's with incredible navigation, linters, debuggers, unit tests, and amazing environments to submit PRs with diffs and collaboration tools. Also, since we have automated tools that produce a huge amount of automated/generated code in some environments, the thought of printing all of that out feels like a long laborious task.