|
|
|
|
|
by beforeolives
1865 days ago
|
|
I never understood this way of thinking about touch typing as a distinct skill from typing. My experience was that when you're kid and use a computer for the first time, you need to look at the keys, and then over time you look less and eventually you can type without looking at all. I never saw it as a distinct skill that needs it's own name or needs to be taught in school (apparently I'm wrong about this). It's just typing to me. |
|
Touch typing is a special technique. Typing and touch typing being distinct things isn't a "way of thinking", it's a clear fact. It's not open to interpretation.
The keyboard is an instrument. Anyone can use it without learning the proper technique, but the technique helps a great deal. That's the whole point.
It is greatly comparable to musical instruments. For instance you can learn how to play the guitar yourself, but if you know the proper technique, you'll have better mastery in a shorter time. This is why it needs to be teached, especially to knowledge workers, who type, type and type all day long.
Maybe the skill you currently have is enough for you, but you shouldn't dismiss the proper technique, especially if you haven't tried it (you sound like you didn't really).
Though if you can answer yes to all the questions below, then you probably don't need the technique:
- Can you easily do 80+ wpm whether it is prose or code?
- Do you have more than 95% accuracy at all times?
- Do you never (no exceptions) look at the keyboard?
These things all make a difference. Having less friction with the input instrument results in a higher stamina in a knowledge worker, which means more productivity per unit of time. Few realize this.