How about we solve the much easier problem of "typing much fewer words"?
We don't even have a good auto-complete story yet in most IDEs, even less so a general purpose predictor that puts whole worlds at our disposal as we type.
How about we solve the much easier problem of "typing much fewer words"?
We don't even have a good auto-complete story yet in most IDEs, even less so a general purpose predictor that puts whole worlds at our disposal as we type.
If auto-complete could reach the point where it was near perfect, then it should probably be able to write entire paragraphs or functions based on context and some minor cues. But that's not going to happen.
Where auto-complete becomes valuable is on limited keyboards, such as phones. Even there (on Android), I find it so sub-par that quite often the variant of the word I want is simply not offered to me until I have typed all but the last character. This is maddening.
swi<TAB>
switch <cursor> {
case <tab location>:
<tab location>
default: <tab location>
}Actually, if I could say “switch on enum X” then have all cases generated, that would be a huge productivity gain.
[1] https://code.visualstudio.com/docs/editor/userdefinedsnippet...
I use mostly Python, Elixir, and Clojure (my unnaturally desperate love, which I don't use much). For those languages, the syntax is either less verbose (python/clojure) or less predictable (elixir).
If I were doing Java or C/C++, I would probably learn to love templates and expansions.
(Search for autocorrect in Settings and scroll down to hardware keyboard.)
It's interesting to try to use. I type faster than it is useful to me.