|
| ▲ | weitendorf an hour ago | parent | next [-] |
| I thought this way until I tried it, and the main difference is that when I'm managing tons of agents at once or just reviewing some plan / approving next steps, or need to give quick feedback/ask a simple followup, the voice interface makes me much faster and more likely to continue because it's lower friction (and in many cases that's good, though not all) and can be hands-free. Actually, my thoughts on this matter changed so much that it inspired me to get much more into voice controls because I realized how this same problem was basically why some people sucked at remote work or weren't able to properly use tools like claude code, because it was essentially the same problem but worse (typing / messaging feeling too high-friction or raising the barrier for participation). I have a way to let Claude call me now to tell me stuff when I have a bunch of instances out doing stuff and then leave to go home. I'm trying to get that better integrated in my devloop because I think it makes managing >4 agents simultaneously much more feasible and natural for some people (I used to play Starcraft a lot so I'm used to the multitasking, but it still takes sustained willpower to be constantly "driving" or monitoring things, or to field questions), especially ones who have never served as TLs or people managers before. IMO it's a big performance roadblock for a lot of developers to be treat directing multiple agents simultaneously as some kind of high-stakes/high-cost thing. The kind of developer who would not say anything in a team meeting unless prompted or who thinks everything is stupid by default (because they are afraid of making decisions / being wrong even if only briefly) is both very common and reluctant to work this way, but also really probably needs it to be as productive as more skilled developers. |
|
| ▲ | itake 2 hours ago | parent | prev | next [-] |
| I am someone that prefers a slack message to a coworker than talking to them and I use AI. My current flow is: Google Eloquent to capture 127WPM (my typing is best case is 65wpm). This lets me get the thoughts out without thinking too much about structure or flow, the same way I would brain-dump type it. Next I use AI to compress, summarize, and restructure to create a clear coherent message for my peer to read (which is way faster for them). When communicating with AI, its the same thing, except I skip the second step since AI does a good job at understanding my ramblings. ---- It drives me crazy that some cultures only send voice messages to each other. It drives me crazy they can't be respectful of my time and use STT+AI to convert their 90 second monologue to a few written sentences. |
|
| ▲ | cicko 2 hours ago | parent | prev | next [-] |
| If you spend your life sitting in a chair, that's fine. I tend to get all kinds of ideas, questions, and research needs while I'm walking around. Typing a paragraph or two or context takes too much time and is very risky. Especially when driving. But also just walking, cooking, cleaning, etc. Sometimes it's just not practical - winter, carrying stuff... I mostly feel privileged if I can just sit at a computer and type my question and have the time to read the answer. |
|
| ▲ | QuantumNomad_ 2 hours ago | parent | prev | next [-] |
| When I was still using OpenAI, I used it among other things to translate from English to Spanish while talking to Spanish-speaking people in person. I understand a bit Spanish but I don’t speak Spanish yet, and they don’t speak English. I speak English to the AI and end with “translate to Spanish, translation only”, and then the AI says the thing I was saying in Spanish (not perfect but good enough, and also it has a slightly weird accent that might be it using English or English influenced text to speech even when speaking Spanish sentences?). |
|
| ▲ | stranded22 2 hours ago | parent | prev | next [-] |
| Accessibility. |
|
| ▲ | arcanemachiner 2 hours ago | parent | prev | next [-] |
| Much faster and better flow. Don't knock it til you've tried it. |
|
| ▲ | throawayonthe 2 hours ago | parent | prev | next [-] |
| it's very confusing. maaaybe if the stt is good and fast enough, speaking may be faster? english speakers can probably hit 150-180 wpm but seems like a hassle |
|
| ▲ | perching_aix an hour ago | parent | prev [-] |
| It's easier, faster, and more natural to talk than to type for the vast, vast majority of people. This trivial fact of life is observed every day by e.g.: - students taking notes and finding it necessary to only jot down key facts so that they can keep up, - stenographers who require special training and equipment to keep up verbatim with live speech in the courtroom, - annoying colleagues who insist on "hopping on a quick call" or arranging big, wasteful, and disruptive meetings instead of just writing down their problem / sending a message or email, - friends who insist on sending short voice messages in DMs instead of typing, because it's more "personal" that way (which to be fair it is, but not to the extent proclaimed). |