Atwood specifically addresses the fallacy of "thinking vs typing as the bottleneck for programming" with the statement [1]: "What I'm trying to say is this: speed matters. When you're a fast, efficient typist, you spend less time between thinking that thought and expressing it in code."
It's not about averaging 90wpm in code. No programmer I know does that. It's about not averaging 10wpm once you've finished thinking and want to materialize your thoughts or revert a mistake.
My work is typing, primarily code and email. Every minute I spend typing my thoughts is a minute of thought wasted.
[1]: http://www.codinghorror.com/blog/2008/11/we-are-typists-firs...