4 ms·
I've reached a point with typing where I can ~95% touch-type. This is fairly recent for me, let's say in the last two years. However, most of what I do with a k
by esperent 6y ago
I've reached a point with typing where I can ~95% touch-type. This is fairly recent for me, let's say in the last two years. However, most of what I do with a keyboard is code, and I'm not convinced that touch typing speeds up my coding that much.
However, if I'm wrong I'd like to put in the effort to reach the final 5%, or even maybe switch to a different keyboard layout, or teach myself stenography.
Does anyone have any data or insight on touch typing/stenography and coding speed rather than typing speed?
- tyingq 6y agoI would guess that coding speed is also tied up with knowing the features of your editor well. There's really efficient ways of moving blocks around with vi, or applying regex patterns for example. I've certainly watched over the shoulder of people flying through refactoring, even though their actual typing speed wasn't notable.
- toast0 6y agoNo data, but I don't think you generally need to type all that fast for coding. You just need to type well enough that it's not an impedement or a distraction. It's ok to look for some of the symbols you don't use that often. Fast typing helps a smidge with the easiest problems on topcoder. Of course, that's after you commit to single character variable names.
- gen220 6y agoI find touch typing to be most valuable to me in pair programming with coworkers, or live programming for teaching. I don’t need to think about what my fingers are doing, and I can focus on what I’m speaking or what I’m going to do/talk about next. This reduces the frequency and duration of pauses, and makes the presentations more engaging. The goal is to be modifying text just a bit slower than people can keep up with, and taking explanatory pauses after dense changes. Obviously helps if you can navigate your editor sans mouse.