Question: steno for programmers
Opened this issue · 3 comments
Hey,
I came across Art of Chording and I've been really interested in the subject. I have one lingering question though: as a programmer, I was wondering how one would enter things such as identifer names with different forms of casing (eg snake_case
, lowerCamelCase
, special characters, etc). And also I don't know how familiar you are with vim or other modal editors, but I was also wondering if in your experience it affects coding speed positively?
I'd be so grateful if you could reply summarily to these questions, I've been hesitant to order a steno keyboard for those reasons :/ If I may add, I might be interested in contributing through patreon or otherwise for a section on programming in Art of Chording.
Thanks!
I'm a beginner, but I have found a few resources:
- There are modes which you can assign to a stroke
- Plover supports full unicode
- People have contributed various steno dictionaries, including ones for Vim and terminal commands
- Typey type includes community lessons related to various programming languages such as Ruby
- @morinted who wrote this book is a programmer and there is a video of him walking through how he uses steno for programming fizzbuzz
- Mirabai Knight, who started Plover, also has a demo of her transcribing some of Plover's python source code
- The discord channel is pretty active and I'm sure everyone would be happy to answer any other questions you have
Those are excellent resources, thank you @ant-i-c-s
A late chapter on using stenography for programming is definitely in my plans, but I still need to get through the basics before that.
I just answered some questions on the hacker news thread, but I'll copy them here:
There are modes, like caps lock, but for snake case, camel case, and other things.
You can also do a stroke-by-stroke basis. For example, I have strokes for prefix "is" and "on" followed by a capital. So
A*UN SMIT
would be "onSubmit". You could also fall back to forcing an attached, uppercase word. So:ON KPA* SMIT
And thoughts on whether stenography is even useful for coding
Great, thanks, that answers my questions :) Can't wait for that chapter then.