Sure, not having access to documentation sucks, but not having access to HN and Twitter compensates for it well :-)
I then switch to working on a different part of the program, or a different program altogether, and come back to them when I'm next online.
This has worked pretty well for me so far, as long as I'm not under a time crunch.
I've noticed that I eventually get "push anxiety" when I work offline for longer periods. Once we even had to do a detour on a road trip from Poland to Helsinki to stop by a colleague's office in Sweden to be able to push code I had written on the way. I guess I simply don't trust my laptop...