3 ms·

The author is missing the point. If your editor doesn't have abbreviations, snippets, completion, etc., you're doing it wrong. If you can type above ~80 WPM (

The author is missing the point. If your editor doesn't have abbreviations, snippets, completion, etc., you're doing it wrong. If you can type above ~80 WPM (which basically just means you can touch type), then using the proper tools your effective WPM is easily above 150 and thus totally irrelevant. Or put in other words, once you can touch type, you are far better off improving your tools and workflows than practicing typing. In a competition you might train your legs, but in real life you get in a car.

stkdump 3y ago
If he is writing 125 lines per week, then it is hardly going to matter. He could be typing with his nose and get the job done.
- dataflow 3y ago
  > If he is writing 125 lines per week, then it is hardly going to matter. He could be typing with his nose and get the job done. Writing 125 lines is not the same as getting 125 lines of code into production
  - stkdump 3y ago
    The sad reality of large software companies. At this point I wouldn't be surprised if there are engineers who spend their entire career without getting any of their code into production before each of their projects are cancelled.
UglyToad 3y ago
Agree with this, if one is thinking in terms of typing letters out you're working at entirely the wrong level of abstraction and with the wrong primitives. I often use the example of ".toString" being meaningful whereas ".tosling" is nonsense (unless you have defined it elsewhere). I'm not even sure if that's the correct capitalization of the to string method in JS, but I shouldn't have to care. If my tools can't tell me which one is valid to use in the current context, then the tools are bad and I should look for better tools. (This may not be universally applicable and maybe Lisp is the promised land etc etc. But raw text input speed is a silly metric to prioritize and leads to a local maxima in programming)

stkdump 3y ago

If he is writing 125 lines per week, then it is hardly going to matter. He could be typing with his nose and get the job done.

dataflow 3y ago
> If he is writing 125 lines per week, then it is hardly going to matter. He could be typing with his nose and get the job done. Writing 125 lines is not the same as getting 125 lines of code into production
- stkdump 3y ago
  The sad reality of large software companies. At this point I wouldn't be surprised if there are engineers who spend their entire career without getting any of their code into production before each of their projects are cancelled.

UglyToad 3y ago

Agree with this, if one is thinking in terms of typing letters out you're working at entirely the wrong level of abstraction and with the wrong primitives. I often use the example of ".toString" being meaningful whereas ".tosling" is nonsense (unless you have defined it elsewhere). I'm not even sure if that's the correct capitalization of the to string method in JS, but I shouldn't have to care. If my tools can't tell me which one is valid to use in the current context, then the tools are bad and I should look for better tools. (This may not be universally applicable and maybe Lisp is the promised land etc etc. But raw text input speed is a silly metric to prioritize and leads to a local maxima in programming)