News for hackers. Stuff that matters.
Re:Linux containers in 500 lines of code (2016) by giancarlostoro on Thursday November 02, 2017 @07:06AM (#15609308)
Printed out works are less distracting, you can also write on them with a pencil or highlight things you like. Also if the page ever disappears / becomes inaccessible you have a backup of it. Not something I do, but I can see the uses. A coworker did it to analyze someone else's code. Also it doesn't drain your eyes as much. I sometimes wish I could have a Kindle that just showed me code (with some syntax highlighting) so I could look at code on an e-reader type of display but never drain my eyes doing so.
Re:Linux containers in 500 lines of code (2016) by Bromskloss on Thursday November 02, 2017 @11:10AM (#15611092)
> Also if the page ever disappears / becomes inaccessible you have a backup of it.

I get the other parts, but this is the one thing where having it in a computer format would be _more_ practical. :-) I would rather go the opposite way, i.e. scan physical book for the purpose of keeping a backup.

Re:Linux containers in 500 lines of code (2016) by toomuchtodo on Friday November 03, 2017 @12:37AM (#15616731)
To soak up new code, infrastructure diagrams, etc I’ll print it all all, 3 hole punch it, and put it in a binder to leaf through with a pen or highlighter on the couch.

So much more information is retained I find doing it this way over using Visio or Sublime.