3 ms·
One quality I find with above-average programmers is they type so much faster than the average programmers. 100-140 WPM on average. What's the importance? Th
by j45 14y ago
One quality I find with above-average programmers is they type so much faster than the average programmers.
100-140 WPM on average.
What's the importance? They code quicker, hit walls quicker, debug quicker, fix quicker, ship quicker. They also have to be able to think quicker once the steps ahead of them are clear.
Getting through this cycle quicker I think makes a programmer much more effective at building lots more software, and through it, finding the lessons from the experiences a lot quicker.
- slurgfest 14y agoIf you just do a whole lot of typing you will tend to get faster, so if this is true, I'm not sure it wouldn't just be because of experience writing code.
- j45 14y agoYeah, I meant typing faster + programming gets you more efficient.
- spacemanaki 14y ago> One quality I find with above-average programmers is they type so much faster than the average programmers. Correlation, causation, etc... I imagine that most above-average programmers have spent a lot of time programming, which does involve some typing. So they get relatively fast at it. But I would just caution against bringing up typing speed since it shouldn't be a goal in and of itself. > They also have to be able to think quicker once the steps ahead of them are clear. Not really sure how typing quickly helps you think quicker. I've seen programmers who appear to love banging their fingers against the keyboard but never stop to think, and suffer for it. (anecdata, etc)
- j45 14y agoThe connection I was making is Above average programmers seem to do everything quicker, including typing. Didn't mean to imply it was 100% of the time, or the other way around that people who type fast are probably good programmers -- it's just one observation point that I compare their output with. Another post here mentioned the idea of 'actions per minute', I like that idea a lot.
- T-hawk 14y agoInput speed is totally a major part of being a productive programmer. Not necessarily raw words-per-minute typing (it helps, but how much of programming is words, compared to symbols?) But navigation speed around your machine and environment makes a huge difference. Things like cutting a block of code and jumping down two screens to paste it. Or memorizing all the keyboard shortcuts for your debugger, so your mind stays on the problem rather than nosing around toolbar buttons. Or operations as mundane as fixing the indenting of a block of code, that a programmer could easily do a hundred times in a day. Save five seconds on that and it seriously adds up. I naturally zip around (Windows) environments very fast. I can typically compile and alt-tab over to the output directory and copy and paste to a deployment folder in under two seconds, often before the programmer watching next to me registers that I've done it. This seriously matters! Like you say, programmers with this practiced skill set can code quicker and debug quicker and ship quicker. (There are downsides; I can't stand pairing with a slower typist, drives me crazy.) Laptops are right out for serious productivity for me, for this reason. My hands know all the (Windows) keyboard shortcuts in the Ins-Del-Home-End block of keys, so my navigation speed on a laptop keyboard without that usual layout drops to half or worse. Actions per minute as a metric can go beyond Starcraft. It matters for programming too. I dearly wish to see the day when neural human-computer interfaces become readily available and accurate. Imagine just thinking 'click' at a toolbar button and there it goes. Not just for typing and programming either, but how about games? Imagine playing Starcraft at the speed of pure thought, with no APM constraints to get in the way...
- j45 14y agoI really like the idea of 'actions per minute'. It's a really nice way of summing up what I was describing.