News for hackers. Stuff that matters.
Re:We Are Typists First, Programmers Second by nradov on Tuesday November 18, 2008 @12:08PM (#368418)
It's not ridiculous at all. You may spend very little time actually typing in code, but most developers spend a lot of time typing things like API documentation, design proposals, e-mails, IMs, etc. The slow typists tend to write inadequate documentation and not exchange enough written communications with their colleagues.

Keyboards will continue to be the primary means for entering code and English text for quite a few more years. So it's rather silly to put off learning touch typing now while waiting for practical speech recognition or some kind of BMI to show up.

Re:We Are Typists First, Programmers Second by axod on Tuesday November 18, 2008 @12:50PM (#368467)
"API documentation, design proposals, e-mails, IMs, etc"

None of those are programming. They are communication and admin. Which are completely different.

Re:We Are Typists First, Programmers Second by briancooley on Tuesday November 18, 2008 @01:55PM (#368553)
Which wouldn't be a problem if you had infinite hours to do everything. If you are spending two hours a day doing that stuff instead of one hour because you type slow, that's one less hour that you could be coding, or learning, or whatever.
Re:We Are Typists First, Programmers Second by nradov on Tuesday November 18, 2008 @03:36PM (#368684)
Exactly. And they all have to get done in whatever limited time you have.
Re:We Are Typists First, Programmers Second by kingkongrevenge on Tuesday November 18, 2008 @05:50PM (#368860)
I disagree. Writing and coding are much the same. I interpret the replies to this as saying you should hurry through this stuff. Just shovel the crap out.

Well, if it's not worth writing with some care then it's not worth writing at all. If it's worth writing with care, then your typing speed is not going to be the relevant bottleneck, unless we're talking about a hunt and peck typist.

I take it as given that anything one writes, whether code or English, should be read and edited three times before moving on. 80 wpm vs 50 wpm ain't gonna matter if you're doing this.

Re:We Are Typists First, Programmers Second by kingkongrevenge on Tuesday November 18, 2008 @05:38PM (#368852)
> developers spend a lot of time typing things like API documentation, design proposals, e-mails, IMs, etc.

Here's what I've noticed about fast typists: They produce large volumes of hurried and poorly worded and edited crap. Yegge, my current boss, and one of my co-workers fit this mold. They type very fast, and I frequently have no idea what their writing is about, or am annoyed with the excess verbiage.

The best writing is re-writing. The best coding is refactoring. In both coding and writing the bottleneck is going through what you've written two or three times and making the necessary edits and stopping to think. First pass typing speed is absolutely not the bottleneck to producing anything of quality. If you want to churn out unreadable or unmaintainable crap, belting out functions at 90 wpm and then moving right on is a good way to go.

Re:We Are Typists First, Programmers Second by thomasmallen on Tuesday November 18, 2008 @08:06PM (#368983)
That's so very true. I can and do type quickly, but I usually find myself typing in small bursts of words and single lines of code (discrete thoughts), not bursts of sentences or methods. An involved one-paragraph email for me entails composition, proofreading, revision, proofreading, revision, and so on...typing doesn't take the majority of my time by any means. The same goes for the majority of my comments on websites such as this one.

It's not a matter of habit, I just always find ways to better express myself when I take my time and correct those "problem spots," be they in code, email, or other correspondence. It's not that I doubt my skill as a writer, but rather, I owe it to my reader to be thoughtful and patient, just as I hope they will upon receipt.

The only thing I need to prevent is overuse of "etc." It's a tempting habit and lazy, imprecise, etc. When one uses "etc," they leave it to the reader to complete their thought, which is weak and clumsy.