3 ms·
> My paltry 50-60wpm doesn't feel like an impediment to putting thoughts into text, but maybe others feel differently. That may be high enough that you don't h
by Izkata 5y ago
> My paltry 50-60wpm doesn't feel like an impediment to putting thoughts into text, but maybe others feel differently.
That may be high enough that you don't have the impediment, but when you work with someone who types down around 10-15 WPM... You can definitely tell they're spending a lot of brainpower on hunt-and-peck instead of the problem they're actually trying to solve.
Basically there's diminishing returns on increasing WPM and you may be at or past the tipping point. I expect it'll be different not just for different people, but also for whatever they're currently working on.
- usrbinbash 5y agoThe thing is, when a programmers starts to generate input, the problem is already solved, he is merely putting the solution into whatever representation the tools demand. I am not defending 10-15 WPM here ofc. just statingt that the majority of work happens before we start typing in code, and after we typed it.
- foxfluff 5y agoIt's a type-think-type-think cycle (or type-test-think-type-...) and the more time and effort you spend on the typing part, the more it distracts you from the rest. Typing for a few minutes isn't any better than compiling for a few minutes before you can test. It just interrupts the more interesting work.
- usrbinbash 5y ago> It's a type-think-type-think cycle Depends entirely on the individual developer. For me its think-think-think-think-drinkcoffee-think-type. And after the first iteration, the typing to make changes is usually miniscule compared to the initial amount.
- BlueTemplar 5y agoThat's due to unfamiliarity with the input device. And if they end up having to use it several hours per day, this slowness will go away in a few weeks.