Live data from Hacker News

On Voice Coding

dusty.phillips.codes

131–140 of 186 posts

Re: On Voice Coding

#131
post #2

“I type fast enough that I have never had much use for snippets in my text editor. Perhaps if I’d used them more effectively, I would not have developed the RSI symptoms that I have!" Often we have discussions about advanced code completion on HN. Many developers feel they don’t need it, or that it gets in their way, for example. Reading stories like this convinces me even more that our editors (tools) need to be sma…

I am relatively sure that you could tell that my keyboard is primarily used for coding C# in Visual Studio just by looking at which keys are the most worn and which carry a significant layer of dust on them.

The keys that complete an Intellisense selection (space, period, semi-colon, Enter) are nearly ground down to nubs, and the open-paren and open-bracket keys are worn smooth, while the corresponding close keys indicate near complete disuse. Similarly for F5 (Start Debugger) and F10 (Step Over) compared to the rest of the F-keys.

Re: On Voice Coding

#132

This post starts out talking about expecting to spend around $1,000. There are at least two cross-platform projects where the biggest expense is a microphone instead of software. 1. My project, Talon. Windows/Linux/Mac support, and a first party local speech recognition engine that is pretty good and getting better. It’s free, but the engine is in a private beta (which is $15/mo to support development, optional if th…

Actual links to the projects would be useful. ;)

Re: On Voice Coding

#133

This post starts out talking about expecting to spend around $1,000. There are at least two cross-platform projects where the biggest expense is a microphone instead of software. 1. My project, Talon. Windows/Linux/Mac support, and a first party local speech recognition engine that is pretty good and getting better. It’s free, but the engine is in a private beta (which is $15/mo to support development, optional if th…

Actual links to the projects would be useful. ;)

1. https://talonvoice.com/ 2. https://serenade.ai/beta

Re: On Voice Coding

#134

This post starts out talking about expecting to spend around $1,000. There are at least two cross-platform projects where the biggest expense is a microphone instead of software. 1. My project, Talon. Windows/Linux/Mac support, and a first party local speech recognition engine that is pretty good and getting better. It’s free, but the engine is in a private beta (which is $15/mo to support development, optional if th…

Here's a video outlining Talon's [1] UX: https://youtu.be/ddFI63dgpaI

[1]: https://talonvoice.com/

Re: On Voice Coding

#135
post #61

Earlier quoted context omitted.

I would like to apologise for that. You really made me think and know that I've become a mac user I have the opportunity to try your solution out. The blog post was intended in a rather light tone. My intention was to add the more in depth analysis in the book. Now that I am a mac user I finally have the chance to take a look at your solution. I do think that I have a lot to learn and do not think that the areas of r…

Funny timing on switching to Mac, as Talon now has a triple platform beta. If you’re looking to get an accurate (pun intended) read on things, make sure to try the beta wav2letter engine or try Talon with Dragon. Apple’s MacOS speech engine was never as accurate or comfortable to use, and as of Catalina it might be more accurate but it’s broken for Talon’s use case anyway :(

Also, regardless whether you would be trying to tie in a custom chorded keyboard, plug in voice recognition or control your computer with a single muscle there would be a certain overlap in integration with computer software. That'd be the rationelle for creating a repository / loose collection of interoperable solutions so that when you have e.g. a great voice recognition platform you could have it working with N platforms straight away. Instead of having all the new interface attempts having to write all of this boilerplate from scratch. Let's say interface for eclipse, ubuntu, windows, chrome, ...

Along with benchmarks for testing the performance and in a more or less sciency fashion compare them to each other. An overlap would also exist in other areas such as word prediction and probably many more.

Re: On Voice Coding

#136
post #9

How well would this work in an open office setting, especially if several people are using it?

There are really good mics at background rejection, if you’re worried about external voices filtering in. 1. Cheapest is probably a USB dynamic mic of some kind. 2. Next is a Stenomask at around $250 3. A lot of folks swear by the DPA d:fine cardioid, which is $800-1300 including an interface. There’s also cardioid shirt worn lavalier I’m interested in trying sometime, which is the same interface but the mic is $150…

I am also thinking in a more general sense of keyboard usage. Walking for example would reduce precision, noisy areas such as car and in industry etc...

Re: On Voice Coding

#137
post #9

How well would this work in an open office setting, especially if several people are using it?

I suspect this setup would not be ideal as background noise getting worse would be annoying for all concerned and even more challenging than an open plan office already is, and your colleagues might not appreciate this unless you're already surrounded by people talking all day (e.g. support or sales teams on calls). That aside, in terms of worrying about your mic picking up other people's voices and the voice dictati…

Very interesting. But what about people who simply just rather use their fingers? Would you not rather type than speak if possible?

Re: On Voice Coding

#138

Earlier quoted context omitted.

juke would work and not break any other phonemes.

Thanks for the suggestion! There are several rules and considerations in play. For testing juke, I’d take a look at any words in the alphabet that could conflict with it on either side: > air bat cap drum each fine gust harp sit jury crunch look made near odd pit quench red sun trap urge vest whale plex yank zip I see: cap, each, gust, crunch, quench I’d say “juke cap juke each juke gust ....” out loud to test it. I’…

How about 'jilt'?

Re: On Voice Coding

#139
post #53
post #49

Just a quick shout out to Microsoft (no affiliation) - Their Sculpt keyboard has taken all the discomfort out of 15hour coding sessions. If you're a professional developer, get one.

I'd recommend avoiding 15-hour coding sessions over using an ergonomic keyboard.

Probably better. But when the motivation grabs me, I cant stop.

Re: On Voice Coding

#140
post #135

Earlier quoted context omitted.

Funny timing on switching to Mac, as Talon now has a triple platform beta. If you’re looking to get an accurate (pun intended) read on things, make sure to try the beta wav2letter engine or try Talon with Dragon. Apple’s MacOS speech engine was never as accurate or comfortable to use, and as of Catalina it might be more accurate but it’s broken for Talon’s use case anyway :(

Also, regardless whether you would be trying to tie in a custom chorded keyboard, plug in voice recognition or control your computer with a single muscle there would be a certain overlap in integration with computer software. That'd be the rationelle for creating a repository / loose collection of interoperable solutions so that when you have e.g. a great voice recognition platform you could have it working with N pl…

Talon isn’t a fundamentally just a voice control framework. It’s a general platform for bolting on accessibility tooling, because as you’ve said a lot of the requirements are related.
Post reply on HN