I touch type about 100-120 wpm (with lots of caffeine and a tail wind a bit more...), but when i am trying to write code I spend as little time typing as possible.
I'll sit there and think about it or write the code down on paper or draw a little diagram or something, then I'll run it in my head. (Sometimes I just do all of it in my head).
From my perspective, typing is the busywork section of programming, the faster I can get it done, the more fun I'm going to have writing code.
However, I think that overall, having your IDE set up properly would be more advantageous that being a ridiculously fast typist.
Fast typing, however, does make you really good at writing documentation.
A lot of the time documentation is poor because the programmer is a bad typist (maybe just mediocre) and doesn't want to spend the time inputting the full length description of functionality.
If you are a pretty good typist, writing out the full description is as easy as thinking about it.
From my perspective, typing is the busywork section of programming, the faster I can get it done, the more fun I'm going to have writing code.
However, I think that overall, having your IDE set up properly would be more advantageous that being a ridiculously fast typist.
Fast typing, however, does make you really good at writing documentation.
A lot of the time documentation is poor because the programmer is a bad typist (maybe just mediocre) and doesn't want to spend the time inputting the full length description of functionality.
If you are a pretty good typist, writing out the full description is as easy as thinking about it.