[jsweojtj]

I completely agree with this. I've been working on my own 30 day challenge to boost my typing speed, and the reason is similar to what's stated in this article: it's about latency, it's not the seconds saved.

It's mentioned in the article, but I mostly think of it as: the faster one types, the shorter the iteration time. When you can type roughly as fast as you'd normally speak, it's a totally different experience than t-y-p-i-n-g each word of a sentence.

[leetcrew]

I kinda agree, but I've also been humbled time and time again by older devs who literally hunt and peck with two fingers. I even asked one how she fixed so many nasty bugs each week while barely knowing how to type. her response: "I think deeply about problem, then type correct solution first or second time".

[tom_]

You can type quickly and still think deeply about the solution or whatever. Typing fast won't help when you're stepping through the code one line at a time, and it won't help when you're just sitting there with your eyes closed at your desk waiting to find out what to do next. But it is still helpful when you're talking to people in Slack.

[jsweojtj]

Sure, I think the depth of thinking or problem solving is clearly important.

But, I don't think your claim is in tension with the article's claim that being able to type fast lowers a barrier (or provides a benefit) that's more than simply the "time it takes to literally type".

There's more there there.