4 ms·
A lot of horseshit is talked about how quickly you can type. Fundamentally, I assert it's really pretty unlikely that your throughput at the keyboard is a limi
by edderly 16y ago
A lot of horseshit is talked about how quickly you can type.
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.
- slantyyz 16y agoYou're right. When I'm writing code, I often don't find the typing to be my impediment. 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.