[synkarius]

Like the author of the article, I've been making the switch to programming by voice. At first, the delay was really jarring, but you get used to it.

You're also completely correct about how when you speak a chain of commands, one of the commands in the middle getting messed up can invalidate the rest. That happens a lot. You learn to speak in shorter chains, and also to make the commands phonetically distinct.

That said, both the delay and the inaccuracy problems can be greatly ameliorated by a fast CPU and a good sound card. I don't have any benchmarks, but I have noticed the difference since upgrading.

[tracker1]

I know someone who does a lot of voice input, he tends to use simple sounds that are distinct as a trained syntax... like: "woof" for moving to the end of a line, and "bark" for moving back.. and other words/sounds that aren't common in conversation... he said it took some getting used to but the accuracy got a lot better.

[synkarius]

I use the word "bark" too, albeit for a different purpose. I think that sort of spec selection is just a habit that you naturally get into when creating a lot of voice commands.

Incidentally, I've learned a bit of Korean, and it's caused me to notice that Dragon recognizes words which don't end in multiple unvoiced consonants more easily than those that do. (For example, "taze" is better than "taste" and "pad" is better than "pact".)