I myself am bottlenecked by my brain, not my typing speed.

If you ever have a thought that you want to put into words but need to wait for your fingers, you are being bottlenecked by your typing. Most people think and speak faster than they can type, especially in short bursts; and I'm saying that, as someone who can comfortably type at ~160-180wpm and burst over 200 for a few seconds at a time, I still find myself waiting for my fingers. Holding a conversation over IM is one of the most common places where this bottleneck becomes very noticeable.

> If you ever have a thought that you want to put into words but need to wait for your fingers

I'm not sure, I don't think that happens a lot to me, especially because I speak and type in multiple languages. I as well, feel bottlenecked by the brain, not typing speed. Even when I use voice-to-text software, I struggle to speak out loud my thoughts in a well-structured and well-paced manner, which somehow doesn't happen during normal conversations, only when I'm trying to write my thoughts down.

That being said, as someone who keeps their hands on the keyboard a dozen hours a day, of course I would love to find a way to type much, much faster and more accurately. I bet it comes in very handy when taking notes during Zoom meetings, etc., but my vim-muscle memory freaks out even thinking of having to rebind hjkl keys to something else. I wonder if vimmers who switched to Dvorak or Colemak can share their perspective. I've never gotten brave enough to give them a try, always felt like a waste of time for questionable benefit, but that's probably how most people think about vim-navigation, which has become an inextricable part of my keyboard workflow and I am very grateful for my younger self for learning vim-navigation.

Also when trying out different ways to form a sentence, or prototyping simple code. Typing fast is not about throughput, it is about latency.[1]

[1]: https://entropicthoughts.com/typing-fast-is-about-latency-no...