Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

On Voice Coding

dusty.phillips.codes

Post reply on HN
Print view View original

51–60 of 186 posts

Re: On Voice Coding

#51

Post by rijoja »

qixxiq wrote: post #23

It's still surprising to see Dragon Speech Recognition as the recommended (and only) choice here. Is anyone working on decent speech recognition for Mac/Linux or know good resources for that? The ideal output is a stream of what could have been said, as well as some alternatives, each with a confidence. Every alternative I've tried has not been as effective as the version of Dragon I used from 2011. I think the focus…

From my research on alternative keyboard research (http://tbf-rnd.life) I've come into contact with the author of (and managed to piss of) the author of talon. Seems like a competent solution, even though I haven't been able to dig that deep into it on account of not being a mac user (until know)...

There'd be some back and forth regarding it's suitability for coding over there. Much better support than I expected apparently...

Still as a general solution I do believe it has drawbacks, noisy environments etc.

Re: On Voice Coding

#52

Post by Filligree »

elorant wrote: post #32
dbcurtis wrote: post #29

Earlier quoted context omitted.

Well, be careful. I love trackballs, and have used them exclusively for 25+ years. But... “trackball thumb” is a thing. I had a physical therapist show me how to work out issues when I get them, but ultimately the healthiest thing for me to do is to switch between 3 different trackballs to change up the motions.

I have one with the ball at the top (logitech marble) so no problems there.

I use one of those at work, and a mouse at home. I like to think mixing up the motions helps, but honestly it's because I'm not nearly precise enough to game with a ball.

Re: On Voice Coding

#53

Post by yreg »

lbj wrote: 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.

Re: On Voice Coding

#54

Post by cjbassi »

For those on Linux, I've been working on a Talon inspired voice coding program called Osprey that uses the Google Cloud speech to text API: https://github.com/osprey-voice/osprey.

It's still very much a work in progress but it's already been working very well for me and I'm actually using it to type out this response right now.

Re: On Voice Coding

#56

Post by xur17 »

geewee wrote: post #14
ijidak wrote: post #4

FYI, I thought my programming career was over due to RSI. Now, I only type while wearing long-sleeves. And of course, I still have to take regular breaks. I no longer suffer RSI symptoms. I'm guessing because it increases blood flow to the area and perhaps the warmth helps keep ligaments and muscles flexible and loose. Simple solution, but took a while to figure out. Hopefully this helps someone reading this.

Long sleeves and fingerless gloves definitely help, especially if you're the type to always have cold hands. (I've written about my experiences with RSI as well: https://www.gustavwengel.dk/overcoming-rsi )

This helped me a ton as well. My hands are naturally cold, and most workplaces tend to keep it cooler than I find comfortable.

Re: On Voice Coding

#57

Post by lunixbochs »

rijoja wrote: post #51
qixxiq wrote: post #23

It's still surprising to see Dragon Speech Recognition as the recommended (and only) choice here. Is anyone working on decent speech recognition for Mac/Linux or know good resources for that? The ideal output is a stream of what could have been said, as well as some alternatives, each with a confidence. Every alternative I've tried has not been as effective as the version of Dragon I used from 2011. I think the focus…

From my research on alternative keyboard research ( http://tbf-rnd.life ) I've come into contact with the author of (and managed to piss of) the author of talon. Seems like a competent solution, even though I haven't been able to dig that deep into it on account of not being a mac user (until know)... There'd be some back and forth regarding it's suitability for coding over there. Much better support than I expected…

Hi, I believe you are referring to this [1]. I wasn’t feeling pissed. I was critical of your dismissive tone, as I felt your post was possibly harmful to people who may be looking for solutions. You had said something along the lines of “voice coding can’t work well because Siri doesn’t recognize code” which is a surprising conclusion from a flawed premise.

As a generalization, you seem to be coming up with reasons you _think_ voice coding won’t work well, while ignoring the fact it already does. For example, noisy environments have several very good solutions, such as using microphones designed for them, leaving the environment, or software to reduce noise like Krisp.

The biggest realistic drawback from my perspective is the fact it’s not very quick at mousing, which is why I’ve done a bunch of research on fused eye/head mousing as well.

[1] http://tbf-rnd.life/blog/2019/05/21/hello-world/#comment-25

Re: On Voice Coding

#58

Post by mwiethoff »

random3 wrote: post #28

I had my second surgery just a few months ago. I can type again, but each time I had to use my left hand for months. Initially, it feels like your brain doesn't function properly anymore (not mentioning the psychological effort you have to make in order to be focused on work when you feel your hands are falling apart). Keyboard speed is directly related to how fast you can move your hands to support your thought flow…

I’m one of the creators of Serenade—thanks for mentioning us! We totally agree about the need for higher-level layers of abstraction, and we’re working on some of the code navigation functionality you mentioned right now. If you have any other ideas or feedback, we’d love to chat more, I’m matt@serenade.ai.

Re: On Voice Coding

#59

Post by yboris »

distantaidenn wrote: post #36
ijidak wrote: post #4

FYI, I thought my programming career was over due to RSI. Now, I only type while wearing long-sleeves. And of course, I still have to take regular breaks. I no longer suffer RSI symptoms. I'm guessing because it increases blood flow to the area and perhaps the warmth helps keep ligaments and muscles flexible and loose. Simple solution, but took a while to figure out. Hopefully this helps someone reading this.

I love these simple solutions that may take years to discover but are shamefully obvious after said discovery. For the longest time, I'm talking near a decade, after working for a few hours, I'd get this unbearable neck and shoulder pain. Even after the workday it would last long until the night. I am not ashamed to say that I would be almost in tears some days. Not because of the level of pain, but because it was co…

Thank you for sharing! I recently started working from home and had the stiffest neck after a few days. I realized I needed to raise my screen to eye-level again (as I had at the office).

Re: On Voice Coding

#60

Post by lunixbochs »

lbj wrote: 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.

The Sculpt and Kensington expert trackball (big trackball, not thumb trackball), while not fixing my issues completely, did improve things for me quite a bit.

That said, barring genetic lottery, as the sibling said: enough 15 hour sessions are going to give you RSI no matter what you’re typing on. There’s no way to do that every day, and exercise, take breaks, and sleep enough. Balance is important.

Post reply on HN