3 ms·
Having programmed and navigated my PC via voice exclusively for about 6 months, done a ton of research and written several articles about it and what options ar
by geewee 4y ago
Having programmed and navigated my PC via voice exclusively for about 6 months, done a ton of research and written several articles about it and what options are out there [0][1], I think might be pretty ground-breaking stuff.
Inputting code with voice is generally difficult, often due to variable names, casing, punctuation etc being hard to get right in voice-to-text. I think this might help quite a lot with that.
_However_, some of the hardest things in voice coding isn't necessarily just the input. Navigating large codebases is hard, and particularly editing existing code can be extremely difficult, probably much more difficult than just inputting new code.
I have my doubt that with the demonstration shown here, that it's able to make complex editing tasks simple, but if it does - I cannot overstate how huge of a leap forward it is.
[0]: https://www.gustavwengel.dk/state-of-voice-coding-2017/ https://www.gustavwengel.dk/state-of-voice-coding-2017/
[1]: https://www.gustavwengel.dk/state-of-voice-coding-2019/ https://www.gustavwengel.dk/state-of-voice-coding-2019/
- jovial_cavalier 4y ago>Having programmed and navigated my PC via voice exclusively for about 6 months... I'm curious, why have you done this?
- FloatArtifact 4y agoI can't speak for his use case. However, people with medical conditions like RSI, stroke or anything that limits their action between keyboard and mouse. However, the average developer doesn't need those fine-grained navigation controls but can still benefit from enhanced input through voice. Some have mental disabilities who interface differently. Others are simply supplement their input as an average developer by voice as a preventative measure for repetitive strain RSI. The day the hope is develop something that every developer could see the value and leverage. In a way accessibility is for everyone. In general I see accessibility as a hierarchy that could benefit everyone. Accessibility APIs, close to real time OCR, Eye tracking, alternative inputs (eg pedal, touch pad, stylus) allowing for the broadest possible input and APIs to extract information from applications. Extraction of information from applications and input to applications allows the user to specialize for their use case. My experience as people will become experts in voice their command vernacular shortens as they carve out their niche use case. It goes beyond singular shortcuts too series of actions to get stuff done. However, what really means to happen is voice systems need access to the OS and to the application to really shine. That would empower not only navigation for those that are disabled but context-specific commands that are intuitive and abstracted like next function or parameter.
- geewee 4y agoI had very bad RSI