Earlier quoted context omitted.
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
I like it but it's not really a comparable/usable result. My IDE auto suggests a lot of things and a lot of "words" could be reduced to a single tab key press. For example, in golang, I have not typed a full if err != nil {} in years. "err.nn"+tab auto completes to the if, and "err.re" auto completes to the if + return err. To be able to compare what speed I really code at, I should be able to use these to speed thin…
Typing 118 WPM broke my brain in the right ways
231–233 of 233 posts
Re: Typing 118 WPM broke my brain in the right ways
#232Earlier quoted context omitted.
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
By far the biggest two things screwing me up here are problems with the app itself: The single-quote opens up the browser's quick-search, leaving the app and screwing up the flow, and the automatic yellow text that moves at a constant speed is extremely distracting if it ever gets ahead of me because of how much more visible it is compared to where the cursor actually is. And it's almost guaranteed to happen on the o…
Will look into the singlequotes issue!
Re: Typing 118 WPM broke my brain in the right ways
#233I really recommend MonkeyType. The UI is great, the stats are clear, and the modes are really elegant. https://monkeytype.com/ I used it daily like the author for about 6 months to improve from 80wpm to about 120wpm.
I'm curious: - how many minutes per day? - after each test, did you redo wrong/slow words? My current typing speed, as measured by Monkeytype, is 80wpm (after a deduction for errors).