You should learn to type (properly)
skilldrick.co.uk
skilldrick.co.uk
These days I just a Dvorak layout and don't worry too much about whether or not I use the proper form. I also don't concern myself with typing speed too much - if the speed at which your can write is your bottleneck, you are either much too clever to be in normal software development or you should stop using COBOL.
This "typing is not the bottleneck" is such a cliché - I nearly wrote about it in the article. It presupposes that programming is some kind of pipes-and-filters activity where we're thinking and then typing and then compiling. I don't know about you, but when I'm programming I work in different states. Sometimes it actually is about getting the code into the computer as fast as possible. Not all the time, but sometimes.
The way I got better at typing and typing fast was to be on very busy IRC channels where getting a word in edgewise without missing any of the conversation required a lot of fast typing.
I understand that most of this was meant for the people that are hunt and peck type. I don't think it is at all necessary for people that are able to type at a rapid rate using their own style to relearn how to type.
I remember having to hunt and peck. But kids now use the keyboard from a younger age, I think the need for formal typing skills is not going to be necessary.
A competent touch typist should be able to type with his eyes closed, and without needing to concentrate at all. Typing becomes a reflex action, and you can concentrate on finding the right words, or on your code/problem itself.
I tried to write a Chrome extension for typing text on websites recently. But I never got it to select the correct text blocks, especially on sites with table layouts like HN.
I've since moved over to Colemak layout and I've never looked back (combined with a TypeMatrix keyboard).
brew install gnu-typist
gtypist
sudo apt-get install gtypisthttp://speedtest.10-fast-fingers.com/
You reached 395 points, so you achieved position 14664 of 1148922 on the ranking list
You type 588 characters per minute You have 98 correct words and you have 6 wrong words
Which is close to 99th percentile, although that website may have a bias towards slow typists. What speed would a touch typist expect?
405 points, 11978th, 530 characters per minute, 101 correct words 2 wrong.
101 wpm.
I'm going to go out on a limb here and guess that most professional developer types can probably do within some small percentage of these scores.
From wikipedia:"An average professional typist reaches 50 to 70wpm, while some positions can require 80 to 95 (usually the minimum required for dispatch positions and other typing jobs), and some advanced typists work at speeds above 120"
As far as traits that affect overall developer productivity typing is almost certainly not at the top of the list, and maybe not even in the top 5. However, it is important. If you introduce a degree of inefficiency and friction into communication, coding, documentation, etc. that'll obviously impact overall developer effectiveness.
Consider this thought experiment. Instead of a regular keyboard a developer uses a thumb-based keyboard for everything, perhaps a wired 360 controller with a chatpad attachment. Are they going to get fired over it? Maybe not. Are they going to be less productive than if they were properly touch typing with a regular keyboard? Probably so.
So again, it does not matter. Technique does not matter. Only results matter.
Now he's exaggerating a bit, but I am a slow typer that predominately uses index, middle and thumb. Now, I get stuff done, I'm a pretty smart coder but typing speed, to me, feels like a huge bottleneck. By far the most important area I need to improve on.
Unlearning bad habits is hard, any advice?
My typing teacher used these little cardboard cutouts that stood above the keyboard so you couldn't see the keys. These kept you honest. After that we just used some ancient DOS typing software that started you out typing strings of random letters composed of the homerow. As time went on it started introducing keys from the other two rows as well as numbers.
It was frustrating at first because of how slow I became at something I was normally fast at. However, in the long run my speed more than doubled once I learned how to touch type properly.
Also will infuriate your co-workers and family members when they come to borrow your machine!
Or you can switch to a sensible keyboard layout, of which Dvorak is the easiest to get support for (though not the only, and, abstractly, not necessarily the best, but mostly good enough). Now you get AOEU under your left hand and HTNS under your right, and guess what, you don't have to try to keep your fingers on the home row, because they're just there anyhow. It's difficult to imagine what a "non-touch-typing Dvorak user" would even be, at least once you've really internalized it.
Given how painful learning to QWERTY touch type can be, it's probably easier just to switch to Dvorak, learn the layout, then just naturally learn touch typing in the next couple of months without "trying". The total effort might be lower, even if the switch isn't free.
(This is all assuming we just take as a given that touch typing is desirable. I'm not sure about that, but I also think we lack the data to be sure either way, especially when it comes to long term effects.)
GNU Typist, and real discipline. Force yourself to do it their way.
I'd be interested to see if someone's done a survey on this.
When I was in High School we were required to take a typing class. I sat next to two of my nerd friends. When the teacher had little tests or races, we always came in 1st 2nd and 3rd in the class in terms of speed an accuracy, and between the 3 of us we probably used 8 fingers combined.