|
|
|
|
|
by FreshCode
4667 days ago
|
|
Sean, have you tried any of the ergonomic keyboards which you find pointless? Unless you have, your argument seems a lot like my ol' man's arguments against <Internet/Facebook/YouTube> a few years ago. Atwood specifically addresses the fallacy of "thinking vs typing as the bottleneck for programming" with the statement [1]: "What I'm trying to say is this: speed matters. When you're a fast, efficient typist, you spend less time between thinking that thought and expressing it in code." It's not about averaging 90wpm in code. No programmer I know does that. It's about not averaging 10wpm once you've finished thinking and want to materialize your thoughts or revert a mistake. My work is typing, primarily code and email. Every minute I spend typing my thoughts is a minute of thought wasted. [1]: http://www.codinghorror.com/blog/2008/11/we-are-typists-firs... |
|
Hence bursty sprint speed is more important than sustained speed. Mechanical keyboards are quite good at bursty sprint speeds in my experience. Sustained speed is another matter, I can see where the power return of each key press would cause soreness (like wearing shoes with springs), but its not a problem I have as a programmer who mostly just sprints.
> It's about not averaging 10wpm once you've finished thinking and want to materialize your thoughts or revert a mistake.
Yes, but you don't have that problem on a mechanical.
> My work is typing, primarily code and email. Every minute I spend typing my thoughts is a minute of thought wasted.
Right, the question is not about whether speed matters, but what kind of speed matters. Do you type for a minute without pausing?