"Very fast. Let me explain.
"I work in 2 modes: (A) At the computer and (B) Away from the computer.
"When I'm in Mode A at the computer, I'm cranking out lines of code, testing, revising, testing, revising, etc. This process must be very fast. Several hundred lines of code (or whatever) in less than an hour. A complete cycle in less than a couple of hours. My guideline is that if I'm not working that fast, then I must not be prepared to work that fast, so I don't deserve to be at the computer. I should be in mode (B).
"Mode B is generally much slower. Reviewing code, specs, or notes. Refactoring code. Laying things out with pen and paper. When I have enough work clearly laid out, I know it's time to get back to the computer and return to Mode A."
Also just another point. don't over work yourself, we're all humans (except those damn bots) and you have to give yourself down time to let your brain simmer on the latest and greatest thoughts.
http://www.youtube.com/watch?v=CPjN07JyVjo&NR=1 http://www.youtube.com/watch?v=pcE_JHx5_gA
If you are into bulk writing, then I'd pick a twiddler and text to speech rather than a heads-up-display.
I think one of the reasons driving/cycling/walking is so productive thinking time is precisely that you are constrained. You can't just waste time, you can't launch into stupid half thought out plans.
Edit: I forgot to mention, the same can be done with babies. When you have a baby, and have to feed it, rock it, clean up after it, change it etc. You're forced to just think about problems. It's excellent thinking time. Babies do come in useful after all!