Re: That seems like a strange response to me
I was taught to touch-type, on a massive old machine (shame so many of my comments into web pages are done using a tablet, where I'm down to one-finger typing!) yet I still think that auto-complete can be very handy.
Just so long as it isn't trying to do too much, in which case it just becomes utterly infuriating. The worst thing that it can do is *insert* the current-choice-of-completed-word, by which I mean it moves the cursor to *after* its choice, as it then that you can unwittingly choose the wrong thing. Another truly painful action is to scroll the window, moving the line of text "because that way there is space for the list of options to be drawn".
When the auto-complete just shows a list of words that start with the prefix you've typed so far, allowing you to quickly select one OR simply carry on typing your word without hindrance (btw, dropping from the list those that now don't match the longer prefix) that can be really, really useful. Even if you do know all the possibilities. ESPECIALLY if it stops people complaining that the variable/function names are too long, too much to type in! Decent auto-complete also allows things like using the cursor keys to lengthen (and shorten) the current prefix, scroll the list of matches etc. Even allowing simple matching, without resorting to a full-fat search: I know the function name has something to do with "Flibble" but was it "DoFilbble" or "CommenceFlibble" or... so type [magic-character]Flibble and the autocomplete list is populated.
I should perhaps own up to the fact that I have been responsible, in the pre-GUI days, of adding auto-complete into the TUI of a few commercially released applications, where it appeared to be appreciated by our Users. At least, no-one phoned to complain about *that* part of the programs...