It depends on the type of work you're doing. I've been using vim for many years and I am frequently limited by my typing speed when it comes to some things like scripts.

When it comes to work that doesn't require deep thought, it matters. I'm much more likely to achieve a task that someone else might dismiss "because it requires too much typing."

It also helps a lot with refactoring, which is mostly a mechanical process. I'm much more willing to do large refactoring than some others due to the fact that I'm very good with my editor.

Point is that you're right, but you're also describing a subset of problems which require deep thought, and not fully considering the benefits that might be had from the alternative.

I guess it depends a lot on the sort of programming that you're doing. But there's still a lot of activity around the challenging bits that don't require a lot of thinking. Things like organizational/cleanup, some types of refactoring and testing, dealing with git and other commands.

For some people/tasks, these are the exact types of things accomplished faster in an IDE.

>My bottleneck is nearly always thinking time. Typing time is irrelevant.

I don't agree. Code is communication. Imagine you had to sound out every letter of every word while speaking - it wouldn't just be slower, you'd lose your place or simply not bother saying certain things.

And yet... I still manage to produce award-winning breakthrough software.