3 ms·
A lot of the work is documenting and coordinating, in English like we're doing right here. (I wonder how much missing/outdated/lousy documentation we can blame
by abecedarius 11y ago
A lot of the work is documenting and coordinating, in English like we're doing right here. (I wonder how much missing/outdated/lousy documentation we can blame on the programmers not wanting to type.)
If you type at 60wpm instead of 110, over the course of a career I'll bet that makes plenty enough difference to be worth addressing. (I recently started going over to typeracer.com and keybr.com on breaks, on that theory. We'll see.)
- melling 11y agoIf you really want raw speed then how about using a chorded keyboard and get over 200 wpm? Here's an HN post on Plover: https://news.ycombinator.com/item?id=8510409 https://news.ycombinator.com/item?id=8510409
- abecedarius 11y agoThat's a good suggestion, and I've considered it, but it's a much bigger investment to make before it could start paying off. (Also a greater cost in interop with others at their computers, etc.) If I were 20 instead of 45 I'd check it out more closely. (Perhaps I should anyway?)
- melling 11y agoI think Plover works on any keyboard that supports n-key rollover. http://lifehacker.com/n-key-rollover-anti-ghosting-and-other-keyboard-featu-1643804346 http://lifehacker.com/n-key-rollover-anti-ghosting-and-other...
- abecedarius 11y agoI mean primarily the learning.