It reminds me of a guy I used to work with. He two-finger typed looking at his keyboard all the time, but the code he did end up writing was exactly what was needed. Consistency and quality was much more important than cold, hard "productivity".
Typing hardly registers as a factor when it comes to how long it takes for me to code anything, at least.
I can. Actually, when I learned touch typing I realized how much was I slowed down by typing before.
You might argue that I need to think for a time before I start typing. That's right. But:
1) Once I start, it flows and it's like I'm reviewing the code as I type, correcting and expanding.
2) Writing fast somehow makes me think faster for the next "pre-typing" thinking cycle.
If I'm solving a hard problem (i.e. architecting a system or coming up with an algorithm) then 99% of my time is spent thinking rather than typing.
-- Do I bother you?
-- Don't waste yourself.
-- What's your style?
-- My style? You can call it the art of fighting without fighting.
-- The art of fighting without fighting? Show me some of it.