I can, but I find the friction it induces to be extremely irritating. I have to memorize snippets of documentation before switching back instead of just having it open on the other monitor to reference at a glance. Plus the act of switching windows itself is extra keystrokes/touch gestures and tedium. Coding on a small touch screen sounds like absolute hell. Like being forced to drive in stop-and-go traffic with a manual shift.

I'll do it only if I have no other choice (i.e. logged into a remote terminal-only server at work). If I have some flash of inspiration I'll write it down in Google Keep and try it out when I get back to my 3-monitor workstation.

But hey, we're all wired different

How are they more keystrokes between one screen and N screens? Don't you have to switch windows regardless of their visibility? I mean if you copy then paste elsewhere you still the same number of key strokes, don't you? Maybe I'm missing something.

Regardless what I'm suggesting, and I believe OP too, is NOT to replace your setup with a mobile one, only that they can complement each other. Namely if you are on your way somewhere, you do not have to stop programming, you can still do it even though in a different way, so I do not believe comparing them helps. The point is not to convince somebody to go from their favorite setup to something they like less, rather to show other ways in which some parts of the process are still acceptable on the go. Nobody is suggesting to remove a screen or keyboard.