It might sound kinda silly to think about typing. Does it really matter? Isn't our job as programmers to think? and think of ways to solve problems using code? Yes, I do find myself in states where I know what I'm doing and the bottleneck becomes typing. Also, I do remember when I was in University, my really good friend, who was also an exceptional programmer said that I should learn to type. So I did, got decent at it. His reasoning was simple, you can loose a train of thought if you start focusing on the typing, instead of the code. You can loose a train of thought, if it takes too long to get it out from your head and into your editor. At least that's what I think his reasoning was ten years ago.
Years later when I picked up vim, I wanted editing text to become automatic. Vim allowed me to do that, after a few months, moving around an editor became easy. You are no longer thinking how to get to that line twenty two lines below and change the words inside the quotes. It just gets done.
Recently I was watching a keyboard video and noticed the guy was typing insanely fast. So I got curious and wanted to know how fast was my typing. To my surprise it was less that forty words per minute and the accuracy was really bad. So since, then I decided spend a few minutes improving my typing before I started working on anything. It has gotten better since, I managed to get above sixty words per minute at times but the accuracy is still not great. Turns out I've picked up some bad habits in the last decade.
It might sound silly, but it's turned into a fun thing to do before I start work. I want to improve all the little things I can to get my programming to be better, this might not be a big deal, but since I spend so much time typing, might as well get better at it. It's also something I can see tangible results with, which is a nice change of pace.
I've been using keybr, to my surprise it's the same tool I used ten years ago to get better at typing. Type racer is also fun one.
Happy typing :)