4 ms·
Typing is bursty, agreed. I'm not saying someone who is an extremely slow hunt-and-pecker is ideal. What I'm saying is that, past an average typing speed, obse
by the_af 3y ago
Typing is bursty, agreed. I'm not saying someone who is an extremely slow hunt-and-pecker is ideal.
What I'm saying is that, past an average typing speed, obsessing over WPM gets you diminishing returns, because that's not where the bottleneck is. You should rather spend time improving other aspects of your process, but of course, "thinking better/smarter" is harder to improve.
For the record, I never measured WPM but I'm mostly a fast 2-fingers typist. All keys are typed with my index fingers, and the spacebar with the thumb and some of the special (shift, CTRL, etc) keys with some other finger.
I will lose every competition with a WPM-focused typist, but I can guarantee you my effective tasks -- the actual job we're meant to complete -- will not take me longer, unless said job is transcribing a document (which is never my job).
- Exuma 3y agoIf you are a 2 finger typist and also think people are "obsessing over WPM" because they're wanting to utilize their own tools to the fullest advantage, that sounds like some mental block kind of thing. If you can type at least 80 consistently then thats probably would I imagine the dividing line is between "flow/concentration not breaking" and "breaks constantly" Try a 50 word monkeytype https://monkeytype.com/ https://monkeytype.com/
- the_af 3y ago> If you are a 2 finger typist and also think people are "obsessing over WPM" because they're wanting to utilize their own tools to the fullest advantage, that sounds like some mental block kind of thing. I get frustrated by this kind of replies on HN. Please don't try to "fix" me. I'm telling you my WPM are not limiting, because -- like almost ALL coders and engineers -- I spend most of my time elsewhere, and that 2-fingers is fast enough. I will not solve a Data Engineering problem by typing fast. I probably type faster with 2 fingers than you. Maybe not, but I've seen me "win" over people who type with all fingers, and that's good enough for me. So thanks, but no thanks?
- Exuma 3y agoI'm not trying to fix it, just engaging in a dialog, and I said it "sounds like", because your first thought when reading about people using their tools effectively is that they're "obsessing" about it. A lot of people care greatly about efficiency (me), and having someone who can't actually type fast or seem to care about efficiency then tells you you're obsessing about it seems like the hallmark "I cant do X thing so I will criticize it instead" Are you at least over 60 WPM? I think I said in another comment that I think 60 WPM is probably the lowest I can imagine not constantly breaking your focus while trying to hold ideas in your mind, especially if you do data engineering and youre going multiple layers deep.
- the_af 3y agoI can guarantee you it's not a case of "I can't do this, so I'll criticize it". I'm actually a decent 2-finger typist, and this has never limited me when troubleshooting a problem or designing a solution. Engineering problems are seldom solved by typing really fast. I'm fine with you improving your WPM, I just don't think it's a worthwhile endeavor -- it's not making you more efficient where it matters. Likewise, I could improve my WPM, this is not rocket science and anyone can do it with training. It's not even hard training. But why? I could also train to run faster, but would it help me do my job better? edit: out of curiosity, and this proves nothing either way, I tried your monkeytype link and got 90 WPM with 97% ACC.
- Exuma 3y agoAre you sure about that? I trust you if you are truly, TRULY sure... Imagine you had a tool similar to those ChatGPT IDE auto-complete plugins, except instead of doing chat GPT it typed what was in your mind. Imagine you start work in the morning, and there is a 0ms response time from what you think, and huge blocks of code would appear instantly. Is your work such that you TRULY only type 300 words per day? Or, do you also... write tests, write boilerplate, write for loops you've written thousands of times, write and read files, call/build APIs, write command line tools. If you can imagine some kind of "instant feedback" typing thing quite literally not improving your quality of life whatsoever, then I guess you are just in a rare boat. I can't visualize any circumstance where 80WPM typing would not benefit them, but I suppose there might be a world of developers out there who truly live in a vaccuum like one of my other comments said... they just come in to work, dont communicate with anyone, dont write anything other than a 50 line file with a few hundred words in it, and leave after 8 hours)