Earlier 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…
Typing 118 WPM broke my brain in the right ways
201–210 of 233 posts
Re: Typing 118 WPM broke my brain in the right ways
#202Earlier quoted context omitted.
Maybe some people confused wpm and characters per minute... For writing software having 100% accuracy with numbers and special characters is more important than speed. I don't think 100 wpm is real for coding.
This is why I built wpm.silver.dev. Theres no tolerance for typos on code and way more special characters than MonkeyType. 120 on monkeytype can be 50 on wpm
Layouts with nicely placed special characters are all very non-standard. Building a custom keyboard nowadays is quite easy, but it takes some courage to train something that is seriously less standard than Dvorak ever was.
Re: Typing 118 WPM broke my brain in the right ways
#203Typing fast is an underrated skill for developers. A lot of the value added by various intelligent tab completion and LLMs is easily replicated by typing variable and function names at 100+ wpm. Not a fan, however, of the desire to disparage the "right" way of doing things that's done in this blog. I type the "proper" way, home row and all, and can reach 150+wpm with high accuracy. So, based on this evidence, you're…
The only time typing speed has helped me is when people try to gish gallop me when I’m messaging them and I’m able to gish right back faster than they can respond. That’s…not exactly healthy though.
Re: Typing 118 WPM broke my brain in the right ways
#204Earlier quoted context omitted.
Same. Can touch type accurately while maintaining eye contact during a meeting. Young people find it unnerving.
What? You guys are talking about this as if touch typing is some rare skill. I'm pretty sure everyone around the office touch-types, all my friends definitely do.
Re: Typing 118 WPM broke my brain in the right ways
#205Earlier quoted context omitted.
What? You guys are talking about this as if touch typing is some rare skill. I'm pretty sure everyone around the office touch-types, all my friends definitely do.
I worked at FAANG and at a few mid tier companies and in my experience that hasn’t been the case with majority of my coworkers surprisingly
Re: Typing 118 WPM broke my brain in the right ways
#206Earlier quoted context omitted.
Maybe some people confused wpm and characters per minute... For writing software having 100% accuracy with numbers and special characters is more important than speed. I don't think 100 wpm is real for coding.
This is why I built wpm.silver.dev. Theres no tolerance for typos on code and way more special characters than MonkeyType. 120 on monkeytype can be 50 on wpm
Re: Typing 118 WPM broke my brain in the right ways
#207This is cool but I feel like typing speed and vim skills are going to play less of a role in overall development speed as AI use increases. But certainly it won’t hurt to type fast, even if it’s mostly typing prompts.
I feel like it will always be relevant. Both typing fast and vim.
I always bet on vim / neovim.
Even as tools like Cursor and Windsurf grow, Neovim will always catch up and beat them. Developer attitude of “I can do it better” or “I can build that” will always compete with leading tech products. Tools like aider are already gaining large adoption
Always bet on vim
Re: Typing 118 WPM broke my brain in the right ways
#208This just makes me want to get back into learning stenography again. It requires a hell of a lot of practice, but being able to write at 200 WPM (without frantic finger movement) would be quite nice. Here's a demo/explainer at 200 WPM for example: https://www.youtube.com/watch?v=7jVXrX5TDk4
Its really fun once you get into it if you have the time, are somewhat linguistically inclined, and like messing with emacs configs/keyboard layers. Its not necessary for programming, but my reasoning was that I was going to be spending 8+ hours a day on the computer for the foreseeable future so it was probably worth putting the time in learning given I was already interested. Its much less physical effort to type,…
Re: Typing 118 WPM broke my brain in the right ways
#209Earlier quoted context omitted.
I worked at FAANG and at a few mid tier companies and in my experience that hasn’t been the case with majority of my coworkers surprisingly
Huh, really? I'm very surprised, I'll look around the office with more intention and take an informal mental poll.
Re: Typing 118 WPM broke my brain in the right ways
#210> Plot twist: I don't type "correctly" at all. My fingers just go wherever they want. It's like anarchist typing. My left pinky probably hasn't touched the 'A' key in months, but somehow I'm still in the 99.5 percentile. Turns out the "proper way" is just a suggestion. Like following PEP 8 or using semicolons in JavaScript. Sure, it's nice, but if your way works better, who cares? This is super interesting - I have t…
If you never have to type something you're reading, I'm sure unique typing styles are just fine.