undefined | Better HN

0 pointswarrenm4y ago0 comments

Sure they do: `cp file1 file2`

Vs properly enunciating "Kah-Pee f-i-l-e-1 to f-i-l-e-2"

0 comments

5 comments · 2 top-level

6gvONxR4sf7o4y ago· 2 in thread

When I did hands-free coding, I named my variables things that I could say as words. So you'd be saying 'copy file-num-one file-num-two' or something, rather than spelling it out letter by letter. I actually ended up naming things more verbose names because I didn't have to type it all out. So it might be:

enunciating: 'copy snake-geary-street-financial-report snake-divisadero-street-financial-report'

versus typing: 'cp gearyStreetFinancialReport divisaderoStreetFinancialReport'

If you're trying to exactly replicate something designed (and named) for text input, you're absolutely right, but I thought we were talking about hypothetical designed-for-voice systems.

warrenmOP4y ago

tab completion handles goofy and long file names quite handily ... and lot faster than speaking

6gvONxR4sf7o4y ago

Tab completion relies on a limited context. If you're trying to type gearyStreetFinancialReport and the two names in context are gearyStreetFinancialReport and unrelated, you're right, but if there's a very large number of choices, it benefits you less. And new names aren't going to be in context, so even in the best case of my example, you're going to end up typing:

'cp g-[TAB] divisaderoStreetFinancialReport'

I'd expect that to be an advantage of voice stuff; that you can go fast in new kinds of large scope contexts, maybe even whole-machine context. A system designed from the ground up could exploit that in interesting ways.

1 more reply

falcolas4y ago· 1 in thread

I timed myself. 2.18 seconds to say it. Less time than it takes to type it.

warrenmOP4y ago

you must type slow ... because I can type it in under half the time you claim it took you to speak it

j / k navigate · click thread line to collapse

0 comments

5 comments · 2 top-level

6gvONxR4sf7o4y ago· 2 in thread

When I did hands-free coding, I named my variables things that I could say as words. So you'd be saying 'copy file-num-one file-num-two' or something, rather than spelling it out letter by letter. I actually ended up naming things more verbose names because I didn't have to type it all out. So it might be:

enunciating: 'copy snake-geary-street-financial-report snake-divisadero-street-financial-report'

versus typing: 'cp gearyStreetFinancialReport divisaderoStreetFinancialReport'

If you're trying to exactly replicate something designed (and named) for text input, you're absolutely right, but I thought we were talking about hypothetical designed-for-voice systems.

warrenmOP4y ago

tab completion handles goofy and long file names quite handily ... and lot faster than speaking

6gvONxR4sf7o4y ago

Tab completion relies on a limited context. If you're trying to type gearyStreetFinancialReport and the two names in context are gearyStreetFinancialReport and unrelated, you're right, but if there's a very large number of choices, it benefits you less. And new names aren't going to be in context, so even in the best case of my example, you're going to end up typing:

'cp g-[TAB] divisaderoStreetFinancialReport'

I'd expect that to be an advantage of voice stuff; that you can go fast in new kinds of large scope contexts, maybe even whole-machine context. A system designed from the ground up could exploit that in interesting ways.

1 more reply

falcolas4y ago· 1 in thread

I timed myself. 2.18 seconds to say it. Less time than it takes to type it.

warrenmOP4y ago

you must type slow ... because I can type it in under half the time you claim it took you to speak it

j / k navigate · click thread line to collapse