I actually started writing shorter lines of code once I got my large external monitor. I've found it's really convenient to set my editor to take up 50% of the screen vertically and have either a command line or browser on the other half of the screen (and reference windows on the laptop screen). In this setup, the editor is actually slightly narrower and taller than when full-screen on my laptop.

Switching between screen sizes really made me realize the importance of making sure all my code breaks at column 80, which makes it easier to read in terminals, on other people's screens, etc. as well. Good practice, I think.

I used to have a problem with readjusting window sizes and positions between the laptop and my 24" display until I discovered full-screen apps in the recent OS X. Now I just run the text editor full-scren on both

My shell work isn't the issue. Or rather in isolation it's not. I'll run upwards of 40-50 shell sessions (on multiple hosts, with screen sessions on many of them). The net state of all of those sessions, including spatial relations between shells and color coordination (helpful for state recognition) is the hard thing to replace. Note: it's not that I carefully choose the colors of all shells, but I do have a couple of scripts that will kick out terminals in either lighter or darker shades (lighter == remote terminals, darker == local) to indicate stuff whose state I want to specifically register.

Full desktop sessions and browser state are the big ones.

I might be able to look at NX or another remote desktop solution, but those would be at best poor substitutes.

We don't all work solely in the command line which makes the advice worthless.