|
|
|
|
|
|
by morinted
2136 days 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! |
|
|
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.