I find it rare to be able to think of things worth typing faster than 10-15 "wpm" equivalent of code. And typically much less, perhaps a few loc per day.
Typing 118 WPM broke my brain in the right ways
101–110 of 233 posts
Re: Typing 118 WPM broke my brain in the right ways
#102I've started to learn touch typing many times, but don't use it. The main problem is that as soon as I want to touch type while working (e.g. coding), I only know the letters, but not the symbols, numbers or even uppercase letters. I think I can force keybr to add those, but they are not part of real world examples, while the words are natural enough. Is there any progressive way to introduce those just like keybr in…
Just switch to source code typing in the settings.
Re: Typing 118 WPM broke my brain in the right ways
#103Earlier quoted context omitted.
Staying at home row is not really about ergonomics. The best thing you can do (without breaking the bank, i.e., no bespoke split keyboard setups) for your hand ergonomics at the computer is to get a vertical mouse and tilt your keyboard downwards and away from you (the opposite of what most keyboard feet do, which is tilt your keyboard up and towards you). Both of these keep your wrist neutral/in slight flexion, wher…
Interestingly, vertical mice I've tried (yes plural) feel intensely uncomfortable and make my wrist hurt. I actually quite like to use a trackball, but I'm not sure that did much for me either. Best I've ever done is just use the mouse less I guess. Maybe I'll learn to use a pen tablet as my primary pointing device instead.
I'm a big fan of using the mouse less. When I was having issues, I learned to use the mouse with my left hand. I got used to it enough to be nearly as fast, but I never liked it so it encouraged me to just use keyboard shortcuts.
I thought I invented it, but I've since seen occupational health and safety websites recommend alternating.
Here's a link to an Australian gov PDF: https://www.comcare.gov.au/about/forms-pubs/docs/pubs/safety...
I've seen it in NZ too. I think they suggested swapping the mouse buttons but I prefer to just leave them and do my left clicking with both fingers when using my left hand.
Re: Typing 118 WPM broke my brain in the right ways
#104The site he uses, https://www.keybr.com/typing-test , has such lovely design. I am a big fan.
I find the way that it handles errors to be super annoying—I type fairly quickly and hitting backspace is built into my muscle memory in a way that just seems totally incompatible with that site, even with the "Stop cursor on error" setting unticked.
Re: Typing 118 WPM broke my brain in the right ways
#105Earlier quoted context omitted.
I sorta disagree, however fast you can type, the computer can manipulate text faster. Our brains are huge slow things. We should employ them at what they are good at, coming up with better abstractions and better frameworks. The desire to type faster is a strong signal indicating that you need better macros.
Saving five minutes by typing faster is less valuable than spending five minutes thinking. Typing speed is not a limiting factor for writing good software. And I say that as someone who can type faster than most of my peers
People typing faster can make a huge difference at work: I get asked for help a lot, and when I ask someone to do something on their computer and they do it painfully slowly, that can represent a lot more time that I spend helping them rather than thinking about my own tasks. I thought this perspective was missing from the discussion, so now I've added it.
Re: Typing 118 WPM broke my brain in the right ways
#106Earlier quoted context omitted.
I used to type >140 WPM at high accuracy when I was younger without home row. These days I think I likely sit closer to 90 WPM or so, since I really just don't really need to type super fast very often and am pretty out of practice. I reckon home row is probably not terrible or anything, but like a lot of weird old ergonomics advice, I just don't trust the idea that you must or possibly even should use home row. For…
WASD is my home row, still 120-140. I lowkey judge any developer who is noticable slow at typing as I can't imagine they're using a computer effectively at such a pace given how much keyboard hitting needs to occur during regular use alone. Not that it's a high bar but I'm surprised more companies don't test wpm when hiring over rote crap like LC.
Same.
Also, if I leave WASD for home row I quickly feel pain. Seriously, place the middle finger on W (alao used for S), ring on A, and indicator on D. It's so much more ergonomic it's insane.
Re: Typing 118 WPM broke my brain in the right ways
#107Earlier quoted context omitted.
Not OP but I pivot my wrists and use my ring fingers. I always found it difficult to reach and press keys with my pinkie. Small hands, I guess? Does anyone else do this?
> I always found it difficult to I used to find it difficult to a lot of things, until I practiced enough to be able to do them, which is usually what that predicate implies. It's like people that say they have to use one foot for the brake pedal and the other for the accelerator because they find it difficult to use one for both.
My pinkies are double jointed. They lock up the second I try to bend them on their own without also flexing my ring finger/that half of my hand.
Easier said than done.
Re: Typing 118 WPM broke my brain in the right ways
#108Earlier quoted context omitted.
I used to type >140 WPM at high accuracy when I was younger without home row. These days I think I likely sit closer to 90 WPM or so, since I really just don't really need to type super fast very often and am pretty out of practice. I reckon home row is probably not terrible or anything, but like a lot of weird old ergonomics advice, I just don't trust the idea that you must or possibly even should use home row. For…
Staying at home row is not really about ergonomics. The best thing you can do (without breaking the bank, i.e., no bespoke split keyboard setups) for your hand ergonomics at the computer is to get a vertical mouse and tilt your keyboard downwards and away from you (the opposite of what most keyboard feet do, which is tilt your keyboard up and towards you). Both of these keep your wrist neutral/in slight flexion, wher…
I wasn't getting RSI per se, more like my arms were fatigued after a day of development.
I did the pricey split keyboard thing. One advantage there is that my vertical mouse sits between the keyboard halves which means I don't have to "reach around" to grip it which has saved a whole bunch of muscle movement.
Re: Typing 118 WPM broke my brain in the right ways
#109Interesting, I can already type at 110wpm with 100% accuracy (after some warm up, getting used to the system, confessedly)
I would warn against overoptimizing for rote copying though. It's like making benchmarks and optimizing a language for a Hello World or echo test program.
I found an option that starts prompting whole books, which might be a fun way to read a book or at least add some additional cognitive load.
I originally though the article would be about literally writing. Waking up and writing 5 minutes before going on the day? Writing and downloading your brain into paper instead of scrolling to cleanse your brain? Sounds amazing!
Re: Typing 118 WPM broke my brain in the right ways
#110Earlier quoted context omitted.
Interestingly, vertical mice I've tried (yes plural) feel intensely uncomfortable and make my wrist hurt. I actually quite like to use a trackball, but I'm not sure that did much for me either. Best I've ever done is just use the mouse less I guess. Maybe I'll learn to use a pen tablet as my primary pointing device instead.
Interesting! My personal experience is that using a vertical mouse very quickly cured wrist and forearm pain that I had, and that the reason is because the "handshake" position is the most neutral hand/forearm posture from an anatomical perspective. But everyone is different, of course
I also agree that it doesn't feel like it makes any sense, hence trying it a few times. I never actually tried going to a medical professional to figure out why though, and thankfully it has not gotten worse (mostly better, with being more careful.)