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

Hacker News Discussion ↗

Programmers are exploring whether stenotype and other chorded keyboards—designed to input whole words via simultaneous key presses—can be adapted for writing code. Enthusiasts point to open-source tools like Plover, custom dictionaries, and ergonomic benefits (especially for RSI), but many note that programming’s heavy use of symbols, uncommon identifiers, and IDE completions makes the learning curve steep and the productivity gains uncertain. Overall, chorded input is seen as high-effort and potentially high-reward for niche use cases such as transcription-level typing or severe strain reduction, rather than a mainstream coding upgrade.

Feasibility of Stenotype / Court-Reporter Keyboards for Coding

  • Stenotype is optimized for phonetic capture of spoken English, not symbols or arbitrary identifiers.
  • Code has case sensitivity, punctuation, brackets, and non-phonetic variable names, which don’t map naturally to steno’s phonetic chords.
  • Several commenters doubt it can ever be a general replacement for standard keyboards when programming, especially due to symbol-heavy syntax.

Existing Steno + Coding Efforts (Plover and Others)

  • Plover and similar tools translate steno chords to text in real time, like advanced autocorrect.
  • Some people do write all their code with steno, often in Emacs, using specialized symbol dictionaries, cursor-movement dictionaries, and shortcut-chord dictionaries.
  • You can always “fall back” to single-letter entry if a word or identifier lacks a chord.
  • Others tried steno for programming, found it fun but too demanding in practice: needs lots of training plus building and maintaining a large personal dictionary.

Chorded / Alternative Keyboards Beyond Steno

  • Discussion of Charachorder, Twiddler, ASETNIOP, Moonlander, Forge Keyboard, ergonomic split boards (Kinesis, Dygma, Ergodox) and QMK/QMK-steno support.
  • Custom chords can be defined for frequent code snippets or symbols, but IDE snippet/completion systems often give similar benefits with less effort.
  • Thumb clusters and small, layered ergonomic keyboards are seen as high-ROI improvements for comfort and reach.

Typing Speed vs Thinking Speed

  • Many argue typing speed is rarely the main bottleneck in programming; thinking, design, and debugging dominate.
  • Others note scenarios where they can “see” a page of code and wait on their hands, or want faster note-taking / transcription.
  • Fast, reliable touch typing is still viewed as high-ROI for reducing errors, avoiding flow breaks, and speeding everyday communication.

RSI, Comfort, and Trade-offs

  • Steno’s main appeal for programmers may be RSI reduction: fewer finger movements, more use of arm/hand-down motions.
  • Non-QWERTY layouts and ergonomic boards are favored more for comfort and longevity than raw speed.
  • Learning steno is described as “high effort, high reward,” with many concluding that for typical dev work the cost exceeds the benefit.