|
|
|
|
|
by super_mario
5043 days ago
|
|
People who say typing is not their bottleneck are saying they are not I/O bound but CPU bound. Makes me think what other things you need to improve before you notice your typing can't keep up? But that's kind of backwards. You will never know until you can type fast and freely, liberating your brain to actually think about the problem and code and not finding keys on the keyboard. Besides not everything you do is original and new or inventive. Sometimes you are just doing crap that you know how to do already, and typing or not using smart editor is the bottleneck. But people who can't type usually don't know this. What you don't know can't hurt you, or it can perhaps? |
|
At the risk of painting with a wide brush, I am currently under the impression that any developer who sits down and cranks out code non-stop at their maximum typing rate is either :
a) cranking out a complete mess that will require extensive refactoring down the road
b) the protagonist of "Hackers" or "Swordfish"
For what it's worth, I am a reasonably fast typist (~115 wpm, qwerty) and can't even imagine myself ever coding as fast as I can type. I wouldn't mind for this to be the case, though :)