▲ | jjmarr 14 hours ago | ||||||||||||||||||||||
Steno will get you to 200+ wpm, not 100. I've been trying to learn steno on and off for 5+ years. The problem is I already have 150 WPM on qwerty and I cannot think of a message on Teams faster than I currently type. The opportunity cost is far too large to justify unless you need to transcribe someone else's speech. | |||||||||||||||||||||||
▲ | vundercind 11 hours ago | parent [-] | ||||||||||||||||||||||
I top out around 100 wpm but still rarely bother to push myself to hit my max—and pretty much never when writing code. I can’t really relate to “I need to type faster!” programmer optimizations, nor complaints about things like static typing slowing people down because it’s a few more characters (more thinking, I’d get, but some folks do seem bothered by the extra keystrokes) since input speed is nowhere near being my bottleneck when I’m writing code. I suppose there must be people out there who simply think a ton faster than me, and of course some others are much slower typists than me, and for those folks that stuff’s a bigger deal. | |||||||||||||||||||||||
|