I definitely prefer real books when reading technical documentation. However, when I'm at work, as long as I'm staring at a computer screen, nobody bothers me.

I definitely prefer real books when reading technical documentation. However, when I'm at work, as long as I'm staring at a computer screen, nobody bothers me. The minute I start looking at a printed book, somebody with some (real or imagined) authority comes along and says, "watcha readin', commandlinefan? Why are you reading a book? Not enough real work to keep you busy? Why are you reading about Scala, why don't you ask Srinivas, he knows Scala? 'cause you should know by now that nothing matters except the deadlines, just work without understanding what you're doing or looking for optimal ways of implementing things because if we miss those deadlines it doesn't make any difference whatsoever but it's the only fucking thing we keep track of and the only fucking thing we measure performance based off of", so I settle for the far inferior freely available online documentation or the eye-straining PDF scans I can find.