Typing Speed Bottleneck
The cluster debates whether typing speed is a limiting factor in programming and coding productivity, with most arguing that thinking, problem-solving, and organizing thoughts are the true bottlenecks rather than finger speed.
Activity Over Time
Top Contributors
Keywords
Sample Comments
Are you actually limited by your current typing speed?
Most fast typers type much faster than they speak. Thus I don't really think this would help.
I find that the closer my typing speed is to my thinking speed (be it fast or slow), the better. If my typing lags behind my thinking, I have to slow down my thoughts or I’ll forget what I’m typing, but if I slow down my thoughts I can lose my way there and either forget what point I’m trying to make as I get bogged down in typing it, or my mind drifts. If my thoughts are slower than my typing, I can slow down my typing without detriment, but if my typing is slower than my thinking, it may be de
Obsessing over typing efficiency doesn't make much sense, but being able to reasonably quickly with a high level of accuracy type makes a huge difference. By being able to touch-type at ~30 words a minute (making a rough guess here, I have no data to back up where the speed actually lies) means that you can quickly and easily get the bit of typing necessary over with and get back to thinking, planning and studying for the next bit of typing that's necessary. As an anecdote, I type extremely fa
No, what you experience is normal. Typing speed is never the bottleneck, unless you write some boilerplate code - which, frankly, is something you should avoid and automate anyway. As a rough estimate, I spend more than half of my time drafting, either with pen and paper or in my head, and then half of the remaining time researching. Only a tiny fraction of time is pure typing.
Are you really any faster on average? Sure I can type 60 wpm (I haven't measured, but this is a reasonable speed for anyone to obtain with a little practice, maybe I'm only 40, or I might even get to 100), but that is in typing situations where I'm not having to think. If your job is to enter some document into a word processor (a human OCR), or transcribe a recording (human speech to text) then typing speed is your limit. However for most of us the limit is thinking. I can type
It's about what you type, not how fast you type it. /typed at 113 wpm
I can type about 70-80 WPM on my qwerty in typing tests. The limiting factor in my work isn't typing speed, it's my ability to form thoughts and to express them to the computer. So switching to a faster keyboard does absolutely nothing for me.
Thoughts go faster than fingers. It's already hard enough to keep up with my stream of thoughts when coding, when I'm touch typing pretty fast. I can't imagine my coding experience if I had to look at the keyboard to input my thoughts into the editor. It's subjective, everyone has a different experience, but I feel I would be severely impaired.
The problem for me is rarely typing speed, unless if I'm transcribing something.No, the bandwidth chokepoint is organizing thoughts, and those thoughts into sentences (or into code snippets).It is always nice to be able to express things as quickly as possible, but I'm not sure how much this might actually speed someone up (practically) past a certain threshold (say, 70wpm). The biggest thing that comes to mind might only be accuracy, which can boost output.