Microdecisions and Typing

You are viewing an old revision of this post, from August 15, 2013 @ 10:39:25. See below for differences between this version and the current revision.

I remember learning to touch type when I was in high school. It was really useful – I could look at the screen instead of my keyboard when I typed, and that allows me to monitor what was going on.

That is, I learned to touch type through instant messenger and online games (where you don’t necessarily want to look down for a few seconds).

The problem with learning to touch type in that fashion was twofold:

  1. First, accuracy was less important than speed. This lead to a high (ish) error rate.
  2. Second, speed was achieved on “familiar” words; I got good at typing regular words, and the keys the words those used.

That was good enough through college – getting 50 words per minute was fine for essays, and my error rate was under 10%.

More recently, however, I’ve become aware of how frustrating it is to have a high error rate in typing.

Errors are nasty things. You need to watch closely for them, and then identifying them requires you to stop your chain of thought, correct it, and then move on. It’s mentally “draining” particularly for words you’re not really experienced with.

Worse, the less familiar with typing and the keyboard you are, the more you have to focus on articulating what’s in your brain – need to recall where the keys are, how to spell the word, and so on.

It’s not much – and in most cases, barely noticeable – but it adds friction to the process of getting things out of your head and onto the computer.

If you feel more comfortable with a pen and paper than with a keyboard, that’s probably because of the additional marginal energy you need to exert to put it through your input device (mouse/keyboard).

And, of course, the problem is more apparent when programming. Hitting brackets, equal signs, etc – not normally used in English – are very, very necessary in programming.

So, a few months ago I endeavored to learn to touch type. The good news: it’s not very difficult, doesn’t take that long, and works pretty well. The bad news: your typing speed drops a lot initially.

For general purpose “learning to type” I found TypingWeb to be the best. The interface is clean, the lessons helpful.

TypingWeb
For special characters, typing.io is excellent. You can type through code from open source projects, and – in the premium version – upload your own code and type through that.
Typing.io

Typing.io also has a really useful grading summary. It counts – unlike so many other typing tools – backspaces and eliminated characters to develop an efficiency score. That’s great – an error rate of, say 2% doesn’t fully encompass how much trouble you go to in order to fix the errors,. Counting incorrectly typed, collaterally typed, and backspaces does account for that trouble – and from experience, I’ll say that an error rate of 5% can lead to an overall efficiency of 80% – 85%. That’s not very good.

The above lesson was a little easier than most – Python, using variable names I’d typed quite a bit before – but coding feels so much smoother when the unproductive keystrokes are under 5% (usually, aka for Javascript or PHP, I’m at ~60 WPM with 9% – 12% unproductive keystrokes).

I’m going to keep practicing until I can get to > 75 WPM with < 3% error rate across multiple languages (PHP, Javascript, C, Clojure, Python, etc). At that point I think I won’t have to worry about what to type – it’ll just be seamless – and I’ll reduce the friction, very slightly, from getting things inside my head onto the computer.

Post Revisions:

Changes:

August 15, 2013 @ 10:39:25Current Revision
Content
I remember learning to touch type when I was in high school. It was really useful – I could look at the screen instead of my keyboard when I typed, and that allows me to monitor what was going on. I remember learning to touch type when I was in high school. It was really useful – I could look at the screen instead of my keyboard when I typed, and that allows me to monitor what was going on.
That is, I learned to touch type through instant messenger and online games (where you don't necessarily want to look down for a few seconds). That is, I learned to touch type through instant messenger and online games (where you don't necessarily want to look down for a few seconds).
The problem with learning to touch type in that fashion was twofold: The problem with learning to touch type in that fashion was twofold:
<ol> <ol>
<li>First, accuracy was less important than speed. This lead to a high (ish) error rate.</li>  <li>First, accuracy was less important than speed. This lead to a high (ish) error rate.</li>
<li>Second, speed was achieved on "familiar" words; I got good at typing regular words, and the keys the words those used.</li>  <li>Second, speed was achieved on "familiar" words; I got good at typing regular words, and the keys the words those used.</li>
</ol> </ol>
That was good enough through college – getting 50 words per minute was fine for essays, and my error rate was under 10%. That was good enough through college – getting 50 words per minute was fine for essays, and my error rate was under 10%.
More recently, however, I've become aware of how frustrating it is to have a high error rate in typing. More recently, however, I've become aware of how frustrating it is to have a high error rate in typing.
Errors are nasty things. You need to watch closely for them, and then identifying them requires you to stop your chain of thought, correct it, and then move on. It's mentally "draining" particularly for words you're not really experienced with. Errors are nasty things. You need to watch closely for them, and then identifying them requires you to stop your chain of thought, correct it, and then move on. It's mentally "draining" particularly for words you're not really experienced with.
Worse, the less familiar with typing and the keyboard you are, the more you have to focus on articulating what's in your brain – need to recall where the keys are, how to spell the word, and so on. Worse, the less familiar with typing and the keyboard you are, the more you have to focus on articulating what's in your brain – need to recall where the keys are, how to spell the word, and so on.
It's not much – and in most cases, barely noticeable – but it adds <em>friction</em> to the process of getting things out of your head and onto the computer. It's not much – and in most cases, barely noticeable – but it adds <em>friction</em> to the process of getting things out of your head and onto the computer.
If you feel more comfortable with a pen and paper than with a keyboard, that's probably because of the additional marginal energy you need to exert to put it through your input device (mouse/keyboard). If you feel more comfortable with a pen and paper than with a keyboard, that's probably because of the additional marginal energy you need to exert to put it through your input device (mouse/keyboard).
And, of course, the problem is more apparent when programming. Hitting brackets, equal signs, etc – not normally used in English – are very, very necessary in programming. And, of course, the problem is more apparent when programming. Hitting brackets, equal signs, etc – not normally used in English – are very, very necessary in programming.
So, a few months ago I endeavored to learn to touch type. The good news: it's not very difficult, doesn't take that long, and works pretty well. The bad news: your typing speed drops <em>a lot</em> initially. So, a few months ago I endeavored to learn to touch type. The good news: it's not very difficult, doesn't take that long, and works pretty well. The bad news: your typing speed drops <em>a lot</em> initially.
  <a class="post-image" href="http:// www.typingweb.com/"><img class="alignnone size-full wp-image-325" src="http://www.inscitia.com/ wp-content/uploads/ typingwebLogo.gif" alt="TypingWeb" width="263" height="60" /></a>
For general purpose "learning to type" I found <a href="http:// www.typingweb.com/">TypingWeb to be the best</a>. The interface is clean, the lessons helpful. For general purpose "learning to type" I found <a href="http:// www.typingweb.com/">TypingWeb to be the best</a>. The interface is clean, the lessons helpful.
<a class="post-image" href="http:// www.typingweb.com/"><img class="alignnone size-full wp-image-325" alt="TypingWeb" src="http://www.inscitia.com/ wp-content/uploads/ typingwebLogo.gif" width="263" height="60" /></a>  <a class="post-image" href="http:// typing.io/"><img class="alignnone size-full wp-image-326" src="http://www.inscitia.com/ wp-content/uploads/ typingiologo.png" alt="Typing.io" width="214" height="60" /></a>
For special characters, <a href="https:/ /ssl.typing.io/ pricing">typing.io is excellent</a>. You can type through code from open source projects, and – in the premium version – upload your own code and type through that. For special characters, <a href="https:/ /ssl.typing.io/ pricing">typing.io is excellent</a>. You can type through code from open source projects, and – in the premium version – upload your own code and type through that.
<a class="post-image" href="http:// typing.io/"><img class="alignnone size-full wp-image-326" alt="Typing.io" src="http://www.inscitia.com/ wp-content/uploads/ typingiologo.png" width="214" height="60" /></a>  
Typing.io also has a really useful grading summary. It counts – unlike so many other typing tools – <em>backspaces</em> and eliminated characters to develop an <em>efficiency score</em>. That's great – an error rate of, say 2% doesn't fully encompass how much trouble you go to in order to fix the errors,. Counting incorrectly typed, collaterally typed, and backspaces <em>does</em> account for that trouble – and from experience, I'll say that an error rate of 5% can lead to an overall efficiency of 80% - 85%. That's not very good. Typing.io also has a really useful grading summary. It counts – unlike so many other typing tools – <em>backspaces</em> and eliminated characters to develop an <em>efficiency score</em>. That's great – an error rate of, say 2% doesn't fully encompass how much trouble you go to in order to fix the errors,. Counting incorrectly typed, collaterally typed, and backspaces <em>does</em> account for that trouble – and from experience, I'll say that an error rate of 5% can lead to an overall efficiency of 80% - 85%. That's not very good.
<img style="margin-left: -325px;" alt="" src="http://www.inscitia.com/ wp-content/uploads/081513_ 1526_Microdecisi11.jpg" width="938" height="594" />  <img src="http://www.inscitia.com/ wp-content/uploads/081513_ 1526_Microdecisi11.jpg" alt="" width="938" height="594" />
The above lesson was a little easier than most – Python, using variable names I'd typed quite a bit before – but coding <em>feels</em> so much smoother when the unproductive keystrokes are under 5% (usually, aka for Javascript or PHP, I'm at ~60 WPM with 9% - 12% unproductive keystrokes). The above lesson was a little easier than most – Python, using variable names I'd typed quite a bit before – but coding <em>feels</em> so much smoother when the unproductive keystrokes are under 5% (usually, aka for Javascript or PHP, I'm at ~60 WPM with 9% - 12% unproductive keystrokes).
I'm going to keep practicing until I can get to &gt; 75 WPM with &lt; 3% error rate across multiple languages (PHP, Javascript, C, Clojure, Python, etc). At that point I think I won't have to worry about what to type – it'll just be seamless – and I'll reduce the friction, very slightly, from getting things inside my head onto the computer. I'm going to keep practicing until I can get to &gt; 75 WPM with &lt; 3% error rate across multiple languages (PHP, Javascript, C, Clojure, Python, etc). At that point I think I won't have to worry about what to type – it'll just be seamless – and I'll reduce the friction, very slightly, from getting things inside my head onto the computer.

Note: Spaces may be added to comparison text to allow better line wrapping.