2 ms·
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
by tjr 3y ago
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?
- eternityforest 3y agoI like to step through stuff on the debugger when I'm testing stuff, even if it appears to work, so that I can see if every intermediate step looks as I might expect, and if I notice anything new with the enforced line by line checking.