Live data from Hacker News

Typing 118 WPM broke my brain in the right ways

balaji-amg.surge.sh

171–180 of 233 posts

Re: Typing 118 WPM broke my brain in the right ways

#171

this is fun. my first test hits 125wpm. bursts up to 162wpm. 100% accuracy. seems too easy, though -- no capitals, nums, etc?

Wow, insane numbers!

Give typequicker.com/practice a try -(we’ve got a few text topics to choose from and capitals, numbers, etc) - just hit configure

Re: Typing 118 WPM broke my brain in the right ways

#172

I 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.

Yeah this is really good site!!

I used it for a while but plateaued after some time. Using https://www.typequicker.com/practice now - has more detailed stats and a daily typing test with a leaderboard to motivate me to do at least a little each day Lol

Re: Typing 118 WPM broke my brain in the right ways

#174
post #91

Earlier 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

You could save five minutes by typing faster _and_ also spend five minutes thinking.

You are not considering all of the indirect effects. I.E.

Someone who types twice as fast is more likely to be comfortable to throw in that extra line of docs/comments that explains that whacky line of code.

Someone who has taken the time to improve the speed of the thing they are supposed to do for most of the working day, is a little more likely to be someone who cares about their job.

Re: Typing 118 WPM broke my brain in the right ways

#175
post #77

Earlier quoted context omitted.

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.

Typing fast may be the least important thing towards developing a well designed, long-lived product.

Try communicating with a coworker when the "I" in "IM" is closer to "wait several minutes while he hunts and pecks the next reply".

Re: Typing 118 WPM broke my brain in the right ways

#176
Great post OP.

I myself took my type from ~65 wpm to 124 average wpm[1] in about 6 months as opposed to 1 year by OP by moving to zsa moonlander. If anyone wants I can share the journey in a post. But can definitely recommend improving your typing speed for all the reasons already outlined!

[1] https://monkeytype.com/profile/navxio

Re: Typing 118 WPM broke my brain in the right ways

#177

Typing 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…

> A lot of the value added by various intelligent tab completion and LLMs

Saving typing was never a value add for intelligent tab completion, it is mostly used for discovery and recall (what members does the type of this expression have?), not to accelerate your WPM. After around 20-30 wpm, typing speed is not a bottleneck in programming, but size of the API and how much you can fit into your head most definitely is.

Re: Typing 118 WPM broke my brain in the right ways

#178
post #77

Earlier quoted context omitted.

Typing fast may be the least important thing towards developing a well designed, long-lived product.

Try communicating with a coworker when the "I" in "IM" is closer to "wait several minutes while he hunts and pecks the next reply".

[deleted]

Re: Typing 118 WPM broke my brain in the right ways

#179
post #40

Typing 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…

When I was in the 8th grade (back in the 1900s), I took a typing elective class, because I figured if I was going to be in front of a keyboard typing for a living as a programmer, I should learn to do it right. That was a rare very good decision for kid me back then, and it's paid off ever since.

9th grade for me. The teacher actually just graded us on speed and accuracy, that was my only C in high school. It served me well, however, I got up to 40 WPM and have kept to around 30 during my career (always fast enough it seems). Also, model M PC Jr. keyboards, so I can’t really complain too much.

Re: Typing 118 WPM broke my brain in the right ways

#180

Typing 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…

[deleted]
Post reply on HN