I mean how much do you even have to type to program, if I produce a page of good code in a day, thats a good day, and it doesn't take long to type.
In any case I don't think it makes sense to use typing speed as a measure of programming competence because typing speed is never the bottleneck in producing real, useful code.
> I also don't look at the keyboard
> I just know where the keys are from muscle memory
You are touch typing though. You may have an unconventional style, but that is irrelevant.
(template systems are an editor extension where you type "i" "f" "tab" and magically an entire if statement stanza instantly appears all perfectly formatted and ready for the details to be filled out.)
So if I type at 40 wpm, but 4 keystrokes of mine do more than 16 keystrokes from someone who doesn't use a template system, does that mean I'm effectively typing at 160 wpm? I guess so.
I also use an extension that magically aggressively indents so I don't indent, my editor takes care of it for me, so I guess I'm typing at infinite wpm when formatting code, compared to someone who hand indents.
Is that wrong? Does being bad at typing force you to be more thoughtful and actually make you a better programmer? Or does it just mean it takes you longer?
My thinking is that you are not doing much thinking while you are actually typing, so not being able to type proficiently just means you're slower and that's it. So all else being equal, a programmer that can't type well is a red flag.