5 ms·

I read through some of the site. From what I can tell, this would using stenography works best for typing actual words. I wonder how hard it would be to confi

by oa335 6y ago

I read through some of the site. From what I can tell, this would using stenography works best for typing actual words. I wonder how hard it would be to configure the stenography software to be able to output strings that I actually type as a programmer, given that a nontrivial amount of them are made up on the spot.

overgard 6y ago
There's some examples in the article, but it seems like the gist is you assign a chord to various symbols. Like a curly brace { might use a modified chord for the word "brace"
- hn_throwaway_99 6y ago
  But that seems to defeat the purpose if typing a single character maps to a chord. I really don't understand how chording could be used to make programming faster given how you have things like someLongVariableName, and especially since good editors already provide excellent support for things like templates.
  - morinted 6y ago
    I still leverage templates and autocomplete from my IDE while using a steno machine. My thoughts on going down to one-symbol-per-chord: - Due to the small steno layout, you don't need to stretch your hands to far symbols on the keyboard. - You're not limited to what's on the keyboard. Symbols like ÷ and © and any emoji are now first-class citizens. - There are cases where you get multiple symbols per chord. For example, calling a function `()` is one chord. Writing an arrow like `=>` is also one chord. Overall, I'd say that coding speed doesn't really change as typing fast is not what makes coding fast. There are some real advantages that I find difficult to quantify, though. I switch between stenography and typing for both coding and writing depending on whether I'm at my desk and I find it hard to express clearly why coding in stenography feels natural and nice. I suppose: there's a certain fluidity when you break things down into semantic words rather than simply symbols. Hope that helps!
    - john2095 6y ago
      How do you do the arrow keys and navigate the page? When coding I seem to expend most of my keystrokes just moving around the page. I take it you just setup some short chords for each arrow key, pgup/pgdn, ctrl, alt... etc. It is hard enough getting around a desktop with just keyboard shortcuts as it is!? I expect I would waste an inordinate amount of time fiddling with my dictionary trying to optimize keystrokes for the OS and apps that I spend the most time in.

by oa335 6y ago

overgard 6y ago

There's some examples in the article, but it seems like the gist is you assign a chord to various symbols. Like a curly brace { might use a modified chord for the word "brace"

hn_throwaway_99 6y ago
But that seems to defeat the purpose if typing a single character maps to a chord. I really don't understand how chording could be used to make programming faster given how you have things like someLongVariableName, and especially since good editors already provide excellent support for things like templates.
- morinted 6y ago
  I still leverage templates and autocomplete from my IDE while using a steno machine. My thoughts on going down to one-symbol-per-chord: - Due to the small steno layout, you don't need to stretch your hands to far symbols on the keyboard. - You're not limited to what's on the keyboard. Symbols like ÷ and © and any emoji are now first-class citizens. - There are cases where you get multiple symbols per chord. For example, calling a function `()` is one chord. Writing an arrow like `=>` is also one chord. Overall, I'd say that coding speed doesn't really change as typing fast is not what makes coding fast. There are some real advantages that I find difficult to quantify, though. I switch between stenography and typing for both coding and writing depending on whether I'm at my desk and I find it hard to express clearly why coding in stenography feels natural and nice. I suppose: there's a certain fluidity when you break things down into semantic words rather than simply symbols. Hope that helps!
  - john2095 6y ago
    How do you do the arrow keys and navigate the page? When coding I seem to expend most of my keystrokes just moving around the page. I take it you just setup some short chords for each arrow key, pgup/pgdn, ctrl, alt... etc. It is hard enough getting around a desktop with just keyboard shortcuts as it is!? I expect I would waste an inordinate amount of time fiddling with my dictionary trying to optimize keystrokes for the OS and apps that I spend the most time in.