[erikpukinskis]

Your assumption, which I think is wrong, is that WPM (or maybe APM) is the bottleneck for most work. I suspect reading/comprehension, problem solving, planning, usability, and access to the right tool, discovery of tools, responsiveness of tools, teamwork... These things are much more likely to be the bottleneck.

As a programmer, I suspect I could probably type the entirity of a days work into the computer in a half hour.

[jacquesm]

I can't even read a phone screen without reading glasses on, I absolutely loathe reading more than a paragraph of text on one and I really couldn't imagine getting any significant amount of work done on a mobile platform.

If we count tablets as mobile too (they're wireless after all and plenty of them come with SIM slots) then the consumption part gets a bit better, in landscape mode you can read PDFs on them but the part of work that requires significant input would - for me - not be an option.

[danielbarla]

I suspect that this is highly related to the task being done, and the context.

Some days, I'd totally agree with you; I'm not really sure of the next step(s), and have to give myself lots of time to think about things. This tends to apply when I'm entering unknown territory, and my tasks are relatively fuzzy and uncertain.

On the other hand, some tasks are extremely straight-forward (repetitive / memory-based), and more or less completely WPM and flow-bound. Even working with relatively efficient editors (using shortcuts, macros, VI bindings, etc), it's hard to type out (or otherwise input) much more than 2000 lines of code in a day. These types of tasks certainly require efficient input, and could be greatly enhanced by even better human-to-machine interfaces.

(I'm also a programmer, and these do come from my own experiences)

[hderms]

I think you're right on some counts, but there is a part that I think most people overlook when they dismiss rapid input as being a useful feature.

A lot of modern languages/platforms are able to be used as a REPL console. Same with commandline tools.

Being able to rapidly experiment with bits of code to identify the correct solution can be incredibly valuable.

[Dewie]

> Your assumption, which I think is wrong, is that WPM (or maybe APM) is the bottleneck for most work.

I don't care if it's a bottle neck. I want an efficient means of typing, so that I can keep my focus on other stuff. Maybe I could do a lot of my typing using a terrible interface like my phone, but it would be very aggravating.

[jgalt212]

Yes, but it takes you the rest of the day to edit and test the 30 minutes of typing you are ready to ship. Presumably, most of this testing or editing would involve a fair amount of keyboard interaction.