If I typed more quickly, maybe I would have more time for thinking. That might be very important.
If I typed more quickly, maybe I would have more time for thinking. That might be very important.
I tend to agree - when a developer is on a tear, and creating great code, the _last_ thing you want to have standing between them and their masterpiece is a 20 WPM habit.
* Hey, I taught myself to type as a kid, playing text adventure games and typing in BASIC programs from library books.
I never learned how to type, I just got good at it without trying since I've been using computers for >20 years.
Surely most if not all good programmers have at very least been using computers for a long while before becoming good programmers?
It was when I started college my freshman year and started to spend a lot of time on AIM talking to old high school friends that I really learned to touch type. There's nothing like having to keep up in a conversation to make you type more quickly.
Seriously, just putting your hands on the keyboard correctly and then continuing with a hunt and peck method, if you're typing a lot for your job, will certainly lead to being a good typist within a few months. It doesn't even take conscious effort.
I'd been dicking around with computers for about four years at this point, so I asked them if I could come in and take a typing test to be exempt. They sat and watched me type, and didn't even bother looking at my WPM before they let me skip the class.
I don't really know how you can use a computer on a daily basis, and not learn to type quickly. It's like driving a stick shift for years, and still glancing down at the knob to see where 2nd gear is.
I learned to type with all 8 fingers in about 30 minutes a day for about 2 weeks. I think I just used GNU Typist. Most efficient time investment of my entire life. Is my experience different from others?
Fundamentally, I assert it's really pretty unlikely that your throughput at the keyboard is a limiting factor to your productivity when writing code. It certainly is limiting if you're transcribing speech to text. To code: it's doubtfully reliable as a measure unless you're Rainman or worst case "headbanger" coders who substitute knowledge of what they write for knowledge of the result of what they execute.
Remember, you could always see someone post about how lines of code produced does not equal productivity. There's a recurring post about the guy who considered productive being reducing the size of his code.
Don't get me wrong, typing is a useful skill and good on those who master it at a high level. However it's no substitute for 'working smart' for e.g. :
Writing scripts when you need to.
Knowing your editor inside out.
Knowing your SCM (of choice) well.
etc.
At best I suspect the 'don't type fast' thing just seems to be indicative of the duffers in the industry who are just sucking a paycheck out of your company. Don't let it fool you that it's a definitive metric of software competency though.
My first ideas are usually not quite distilled, and after the initial burst (or brain fart) of code, I spend a lot of time reducing/refactoring the code.
Maybe, but I don't personally buy it (as a fast typer myself). I think programming shares a lot with writing where the editing is more important than the first draft. In my experience, typing speed doesn't significantly affect the quality of a writer's work, though perhaps it does the quantity.
You are proof of this. From what I've seen, your writing is good and goes down well on HN, yet you've identified as a "slow" typist. I don't see why your code should be any different.
- You don't get constantly interrupted looking for a key. Seriously, remember what this was like before you could type. Being able to type without thinking about it must free up a lot of mental energy and allow you to concentrate.
- If typing is easy, you tend to write more. You don't care if you have to rewrite a function. You don't mind using longer, more self-documenting variable names that make your code clearer.
Under 30 WPM, learning touch-typing should be a top priority. (Use Dvorak if you type mainly in English, it's 4 times as fast to learn than Qwerty.) Not having to lower your eyes and your head any more is so much more comfortable that it quickly becomes addictive. Of course, you will be slow at first, but you can get your speed back in two weeks (maybe even faster if you choose a Dvorak layout).
50 WPM (my speed, getting better over time) feels pretty comfortable, though Id' like to type a bit faster. If you hunt-and peck at that speed, touch typing will only buy you the comfort, but even that may be worth it.
90WPM is the speed of speech. Any faster is for contests.
Speech speeds for speeches and books on tape, where the listener can't interrupt and ask you to repeat, are typically around 150WPM http://www.humanfactors.com/downloads/aug00.asp but normal conversation is up around 170-280WPM http://itre.cis.upenn.edu/~myl/languagelog/archives/003423.h... and court reporters need to be able to transcribe speech at over 180wpm and typically 200wpm http://www.thehighschoolgraduate.com/editorial/DF/courtrepor... .
Try reading aloud something you're typing as you're typing it. You'll find that 90wpm is very slow speech. The only reason speeds like 50wpm and 90wpm can feel comfortable is that the actual process of typing is distracting enough that we don't have time to get bored.q
In ......... my opinion it's impo..r..t..ant to make ... these pauses.. when programming .... otherwise you might ... miss ................ something important.
Perhaps knowing the eventual time you must spend to type causes you to think more before you begin typing...
Who's to say?
That said, I can't imagine those blog posts come out quickly :)