Live data from Hacker News

Ask HN: Has anyone tried adapting a court reporter keyboard for writing code?

news.ycombinator.com

11–20 of 110 posts

Re: Ask HN: Has anyone tried adapting a court reporter keyboard for writing code?

#11
post #8

I can already type on a QWERTY keyboard way faster than I can think. That's one reason I haven't adopted a Dvorak habit. Most court reporters use software nowadays that renders their special stenotype skills obsolete.

It's more about comfort than speed.

Re: Ask HN: Has anyone tried adapting a court reporter keyboard for writing code?

#13
post #7
post #3

IANACR, but I would think it's not practical, in that the stenotype keyboard (the official term for the keyboard used by court reporters) is used to record the phonetic _sounds_ of what is being spoken, rather than the actual words. These phonetic codes do not resemble anything approximating the actual words they represent. Also, computer source code (whatever the language) typically contains variable names which oft…

I seem to remember reading once that what is typed by a stenographer is also only meaningful to them. And therefore must be transcribed into English later by the same stenographer. Can anyone here confirm that?

That used to be true but it's much more automatic now that the process involves a computer translating into English in real-time (it's no longer a stenographer translating from their notes by hand).

Re: Ask HN: Has anyone tried adapting a court reporter keyboard for writing code?

#16
Depends on your goal. Chording technique is superior when typing words contained in the dictionary. Meaning that typing some rarely used word required typing it multiple times to "confirm".

Writing code does not suite well for this, since coding with completion contains much more punctuation than plain text.

Instead, check out ergonomic mechanical keyboards: low-profile, split, with columnar stagger, preferrably with 36 or less keys. Uncommon keys are behind a modifier key that acts as a normal key when pressed, but as a layer when held (called modtap).

Also you can experiment with non-qwerty layouts, but IME it gives much less benefit than having a layered layout of physical keys.

More info here: https://www.reddit.com/r/ErgoMechKeyboards/

Re: Ask HN: Has anyone tried adapting a court reporter keyboard for writing code?

#17
Mentioned by others, but I like project pages or home git repositories.

https://github.com/openstenoproject/plover

https://www.openstenoproject.org/plover/

An in-browser demo, https://www.openstenoproject.org/demo/

Suggested, loved extensions, https://github.com/openstenoproject/awesome-plover

Chorded keyboard input methods, more generally, are worth looking into.

Re: Ask HN: Has anyone tried adapting a court reporter keyboard for writing code?

#19
post #10
post #8

I can already type on a QWERTY keyboard way faster than I can think. That's one reason I haven't adopted a Dvorak habit. Most court reporters use software nowadays that renders their special stenotype skills obsolete.

Dvorak is much more comfortable than qwerty, in my opinion. I never actually cared about speed, it just feels better.

This. Using QUERTY immediately feels uncomfortable when i have to use it. Learned NEO2 which has layers accessed with modifier keys. Having a numpad under your hand is one of its' many advantages.
Post reply on HN