51–60 of 106 posts
My typing speed is about 75 wpm, which probably sucks by HN standards. I don't type nearly as fast as I think. When I'm writing Java code, I find that my typing speed is often a bottleneck. In Ocaml or Lisp, it never is.
Earlier quoted context omitted.
Thank you Edit: why is learning to type a dirty little secret?
I think the secret is that those who type slow are picking up speed by being hasty in their code decisions. I'm skeptical, since far more development time is spent thinking about what to do than in banging out text to implement it. And maybe some faster typists just emit more bad, buggy code.
If it's a "lines of code" contest, then sure, learn to type fast, but if it's about producing good concise code I don't think typing speed makes much difference. If you want to program enough, you'll naturally become fast enough.
But hey, don't let that get in the way of smug superiority.
The only time I've managed to make a significant boost was when I bought a Das Keyboard. Not having any labels on my keys means I have learned to absolutely never peak at the keyboard. It's improved my speed overall, but especially with the number row.
I have known a lot of programmers who don't type fast. I don't think it's a massive impediment, but I do think there's a strong correlation between bad programming and lack of typing ability.
I don't think any of the people I personally know and consider uber programmers type really badly. Certainly could be though and I just haven't noticed.
Earlier quoted context omitted.
I don't do the home row touch-typing stuff, either. Nothing formally taught, all organically grown typing from using computers since I was a teenager. I'm typically in the range of 80-100 wpm depending on the test. Primarily only using the index fingers, thumbs for shift keys, spaces and sometimes the other fingers will hit keys in the farthest reaches, depending on what the index fingers are doing. It's kinda neat--…
The issue is probably staring at the keyboard while you type, rather than not touch-typing "properly". I learned to type exactly the same way, not quite proper, but at 80-100 wpm. I switched to the Dvorak keyboard layout about two years ago. Same speed, but it feels better -- much more time on the home row, for one thing. I think it's worth trying if you're interested, but it's your life. ABCD ( http://www.gigliwood.…
"... Yeev noticed that one of the electives, surely placed there by mistake, was Typing. Like, on a typewriter ..." What an elective? Mine was compulsory complete with manual typewriters and battle-axe teacher. One thing I do miss about those old clunkers was the solid feel the keys had. You had to learn to position your index fingers at 'F' and 'J' remember where each key was positioned and hit hard. So letters like…
Earlier quoted context omitted.
Thank you Edit: why is learning to type a dirty little secret?
I think the secret is that those who type slow are picking up speed by being hasty in their code decisions. I'm skeptical, since far more development time is spent thinking about what to do than in banging out text to implement it. And maybe some faster typists just emit more bad, buggy code.
I'm more like an oil-painter. I have to put something on canvas to think. Always typing small expressions into REPL to see where they take me. Writing down a function from top of my head and see if it looks right---I mean, not only logically, but also whether it feels natural and straightforward on screen. Emacs is an extension of my brain. If I have to type slowly, it really gets in my way. If some bad setting on driver or some slow connection to a remote machine puts a delay in the response of keypress, it drives me crazy. I couldn't stand if my own fingers are the cause of the delay.
(BTW, the original article claims "Slow-typist => Bad-programmer". Saying some fast-typist write bad code has nothing to do with the claim. You have to show a good programmer who types slow to refute it.)
Earlier quoted context omitted.
I think the secret is that those who type slow are picking up speed by being hasty in their code decisions. I'm skeptical, since far more development time is spent thinking about what to do than in banging out text to implement it. And maybe some faster typists just emit more bad, buggy code.
I agree with you. If your bottleneck in development is typing speed you're doing something terribly wrong. If it's a "lines of code" contest, then sure, learn to type fast, but if it's about producing good concise code I don't think typing speed makes much difference. If you want to program enough, you'll naturally become fast enough.
In my experience, good, concise code is rarely written on the first pass. Also (and unfortunately), more often than not people who don't type well are unwilling to spend time on rewrites...
Earlier quoted context omitted.
I agree with you. If your bottleneck in development is typing speed you're doing something terribly wrong. If it's a "lines of code" contest, then sure, learn to type fast, but if it's about producing good concise code I don't think typing speed makes much difference. If you want to program enough, you'll naturally become fast enough.
> If it's a "lines of code" contest, then sure, learn to type fast, but if it's about producing good concise code I don't think typing speed makes much difference. In my experience, good, concise code is rarely written on the first pass. Also (and unfortunately), more often than not people who don't type well are unwilling to spend time on rewrites...