Plover: Thought to Text at 240 WPM

I personally like ibm tts slightly more than Google although it is more expensive. I think Google, but definitely other startups also allow you to train the model to be closer to your voice. Since you might have many recordings of yourself before this, could be cool. Comment if you can't find it and I can look It's none of my business how long term it is, but if it is long term look into stenography, especially open source opensteno and plover. Old talk but [this video] It's what court reporters use to transcribe at the speed of text but for you it could mean giving text into a tts software at the speed of normal talking. I've only tried it briefly but if you take the time to learn it, you can comfortably get to normal speech speeds with no hang fatigue. It's one of the reasons opensteno is so nice bc it also has cheap steno keyboards which are normally thousands and locked behind industry. Comment if you want more links! I can add when I'm by my computer

programming at the speed of thought; vim at 240 wpm [this video] I wonder any of the Pycon 2013 participants try to learn plover and what their experiences were, perhaps they even read this topic on HN? I'm already very proficient at dvorak typing (with the regular vim bindings), so I'm not sure if the 30% speed increase would justify taking 3 to 6 months of learning this, it'd be cool for substituting your speech with a text to speech engine, and with openeeg recognition one step closer to cyborghood. It's also nice to just have the skill to transcribe human speech real time and being able to apply for jobs in politics, justice or television. For example, here's an interview with the dutch transcriber in Dutch parliament: [link] I wonder if the steno chording could be optimized significantly by rearranging the keys and layout in a similar way as dvorak did with qwerty. Perhaps T9/autoexpand with Linux can be just as fast, but it cannot be used blind, can it? [link] [link]

> I imagine writers have it even worse than programmers. Well, I dunno about that. One of the major projects I'm currently working with, has over 130K lines of Clojure (tests excluded), and that is not too big of a project. I'm too lazy to figure out the proper way to count "words" in that project `wc` shows over 5M. In comparison - "War and Peace" [technically] is ten times smaller. Programmers do type a lot. Possibly, way more than writers have to. And that's just code. Have you ever thought about how much typing happens outside of coding? When reviewing PRs, replying to emails, etc. That is why every single programmer must invest into choosing the right keyboard; learning how to maintain a proper posture; maybe learn non-traditional ways to input text - Vim and Emacs keybindings; try Stenographic input¹; Speech recognition², etc. Because when they don't - sooner or later they end up having problems: back and neck pain, headaches, RSI, hemorrhoids. --- ¹ [this video] ² [link]

It honestly surprises me that the evolution of ergonomic keyboards has been so slow. Sure, we have plenty of split keyboards now, but we don't have any commercially available DataHand-like designs [1]. Watch someone type with a DataHand you'll see that they barely need to move their fingers at all [2]! The best similarly ergonomic designs we have at the moment are a gaming keypad [3] and some DYI projects [4]. [1] [link] [2] [link] [3] [link] [4] [link] see also [link] ---- On another note, does anybody know how good steno keyboards tend to be for RSI issues in the long run? I've practiced some steno with a regular keyboard (thanks to plover [5] and Typey Type [6]), but I'd need an actual steno keyboard to continue since I don't have N-key rollover on my current keyboard. The Georgi [7] seems like a good option and I'd imagine that it would be pretty good for ergonomics since it's a split design and also rather small. The only problem is that I'd have to learn steno which will likely take quite some time. Here's a demo of someone writing code with a steno keyboard (54 keystrokes needed vs 143 if you were using QWERTY) [8]. [5] [link] [6] [link] [7] [link] [8] [this video]