Recent submissions

Comment · 6 years ago
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.

Comment · 6 years 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!

Comment · 6 years ago
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.

Comment · 6 years ago
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"
Comment · 6 years ago
Comment · 6 years ago
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.

Comment · 7 years ago
Comment · 8 years ago
Just to provide a differing opinion, my daily office is the place that I feel most productive. When I'm home, I'm never in work mode because I never (99.9%) work from home.

I like being around lots of people and having face-to-face conversations to work through problems.

Comment · 8 years ago
Comment · 8 years ago
The first thing that came to mind was a new brand of patent troll companies that seek to invalidate a smaller company's patent by "proving" it invalid.
Comment · 8 years ago
There are lots of open source discussion systems, and lots of transparent ones. For whatever reason, the closed and opinionated Hacker News reached the popularity that it did. I don't mind it.

Something about the mystery and the relatively tight moderation has kept HN from becoming too off topic and silly. Do you think Hacker News has somehow avoided Eternal September?

Comment · 8 years ago
"I hate what I don't understand"
Comment · 8 years ago
The commenter you replied to was being very sarcastic.
Comment · 8 years ago
The post is titled "why you should be using a private search engine" and yet there's only a paragraph at the end that's subtitled:

    Why You Should Use Private Search Engines?
Here's the entirety of that section:

    The truth is, people know that search engines are
    tracking them. Most websites have privacy policies
    which clearly state that they use cookies and other
    means of tracking users. Any in many cases, when we
    are asked to give apps, websites, or products
    permission to track us, we blindly agree. This may
    seem acceptable at first, but it’s problematic if that
    same tracker is following you two years later, when
    you’ve forgotten about it.

    Your search engine should be optimized for searching
    the internet, not tracking you once you’ve left. Your
    Google information can be used against you in legal
    cases, even in civil cases like divorces.
So if I understand correctly:

1. You might forget about trackers you've accepted.

2. Your search history can be used against you in the court of law.

They couldn't come up with anything better for this ad?

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton