How One Programmer Is Coding Faster By Voice Than Keyboard

Posted by samzenpus on Sunday August 18, 2013 @10:14AM from the greased-lightning dept.

mikejuk writes "Is it possible that we have been wasting our time typing programs. Could voice recognition, with a little help from an invented spoken language, be the solution we didn't know we needed? About two years ago Tavis Rudd, developed a bad case of RSI caused by typing lots of code using Emacs. It was so severe that he couldn't code. As he puts it: 'Desperate, I tried voice recognition'. The Dragon Naturally Speaking system used by Rudd supported standard language quite well, but it wasn't adapted to program editing commands. The solution was to use a Python speech extension, DragonFly, to program custom commands. OK, so far so good, but ... the commands weren't quite what you might have expected. Instead of English words for commands he used short vocalizations — you have to hear it to believe it. Now programming sounds like a conversation with R2D2. The advantage is that it is faster and the recognition is easier — it also sounds very cool and very techie. it is claimed that the system is faster than typing. So much so that it is still in use after the RSI cleared up."

2 of 214 comments (clear)

Min score:

Reason:

Sort:

Try that with LISP by sourcerror · 2013-08-18 10:16 · Score: 0, Troll

I'd like to watch him try that with LISP. Though it might work perfectly with COBOL.
Form over function. Typical iSheep by Taantric · 2013-08-18 11:13 · Score: 1, Troll

You can see why he got RSI in the first few minutes of the video. He is using a Macbook Pro attached to three large monitors. First of all Macbooks have the worst fucking keyboards. It is complete and utter victory of form over function. Steve Jobs wanted his machine to look beautiful, who gives a fuck if it is uncomfortable to type on. Secondly look that the absurd height he has placed his monitors. Of course your neck and shoulder muscles will be wrecked working like that day after day.