morinted · HackerTrans

6 tahun yang laludiscuss

This is an important topic of development for Open Steno. Machine shorthand has existed in many languages and is used in many countries.

However, not all of them are "computer" or "realtime" compatible, which roughly means that you wouldn't be able to distinguish in your writing between homophones like "their" and "there" and "they're."

Here's a list of some of the languages that have been developed or ported to Plover: https://github.com/openstenoproject/plover/wiki/Chorded-Syst...

There is a Plover plugin to switch on-the-fly between different steno systems.

There is also a plugin to switch between enabled dictionaries on-the-fly.

Finally, there is the idea of bilingual dictionaries, but I haven't seen it implemented well yet.

There's also the problem of some languages having drastically different layouts.

So far, the most multilingual and successful stenographer I've seen is Stanley Sakai. Here's him writing in a Spanish theory that he developed: https://www.youtube.com/watch?v=eGZ43TID9jU&t=90s

I also know that there are bilingual stenographers in Canada who write both English and French, but I haven't seen it in action yet.

In summary, I think that multilingual stenography is critical for the adoption of steno, but it's currently not easily accessible or widely used.

morinted

6 tahun yang laludiscuss

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!

morinted

6 tahun yang laludiscuss

Agreed that composition time is largely made up of thinking, however once you've decided what you want to write, you still need to write it.

The other thing that I sometimes end up doing with stenography is just a stream-of-consciousness-style writing where I then have to edit it down.

morinted

6 tahun yang laludiscuss

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"

morinted

6 tahun yang laludiscuss

I'm the author of Art of Chording—I program full-time with steno in JavaScript (working mainly with React.)

I'd love ideas on how to demonstrate coding in steno. I struggle with it sometimes because the slowest part about coding is not the input rate… it's the brain. I guess if people are looking to code "quicker"… it's not the rate of input that one would want to explore. I will say that writing comments became a lot easier when the words started to just flow onto the screen.

Here are my existing videos:

Unscripted: https://www.youtube.com/watch?v=711T2simRyI

Scripted: https://www.youtube.com/watch?v=RBBiri3CD6w

Looking forward to any suggestions on how to improve or even just the big open questions you'd want answered on this subject.

morinted

6 tahun yang laludiscuss

The word "escape" might be written "ES KAIP". I brief it as "SKPAIP".

For the keyboard shortcut, I use "FEFK" which is default in the Plover dictionary.

morinted

7 tahun yang laludiscuss

SHOEBOX | Ottawa, ON, Canada | ONSITE | Full-time

We're a technology-first health care company bringing democratic access to clinically validated hearing testing in the form of an iPad app. We support individuals all the up to large companies with a hearing conservation program. We're quickly growing and looking to support existing products as well as need keen people to lead new efforts.

- Intermediate-to-senior Java developer

- React JavaScript developer of all levels

- Senior iOS developer

- Product owner

Check us out online: https://www.shoebox.md/careers/

I'm a React JavaScript developer on the team. Feel free to reach out to me if you have any questions: [email protected]

morinted

9 tahun yang laludiscuss

Unhelpful catch-all responses that don't display a shred of effort or care are the bane of my customer support experiences. Nothing hurts my opinion of a company like being brushed off like a bug.