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 7 months ago | parent | next [-]

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.

▲

rgoulter 7 months ago | parent | next [-]

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

One common loop in programming is "hypothesize, test, evaluate".

If you're exploring or playing around, the quicker you can execute iterations of this, the more likely it is you'll succeed in what you're trying to do.

In that case, stuff like "unused import is a compiler error" or "static typing required" slows down iteration, so gets in the way of rapid prototyping (or whatever).

"Typing quicker" wouldn't benefit the 'hypothesize' nor 'evaluate' parts, sure, but it'd help you reduce the time it takes to test an idea.

	▲	josephg 7 months ago \| parent [-]
		> stuff like "unused import is a compiler error" For things like this I’d much rather spend the time to improve “quick fix” suggestions in my development environments. The computer can fix the problem much more easily than I can learn a new keyboard layout.

▲

TylerE 7 months ago | parent | prev [-]

I also see no need to type faster, but as I get older and have more and more RSI-type issues I'm starting to see more and more appeal into being able to type at the same speed with fewer keystrokes.

Always seemed to me like they'd be terrible for programming with all the punctuation though.

I also need a mouse way too much (and I have shakey hands so trackballs/nipple mice are not viable)

▲

rattray 7 months ago | parent | prev [-]

How'd you get to 150?

	▲	jjmarr 7 months ago \| parent [-]
		Honestly, lots of practice. I've been playing Roblox since 2008. Roblox has also always been text chat, so if I wanted to talk trash AND get kills, I had to be fast. That + a physical inability to handwrite so I've typed virtually everything. It's kind of useless. I almost never encounter a scenario outside of live transcription where I can conceptualize a character stream faster than my fingers can input the stream into a computer. The only programming scenario where that's an issue is LaTeX during a lecture because it's very verbose in places. I also do competitive debate which has a heavy focus on note-taking; high WPMs are useful there. But neither of these two things will be important once I graduate university.