191–200 of 477 posts
"he did win another typing competition using the CharaChorder to hit 267 WPM with 76% accuracy." 76% accuracy doesn't sound so great to me, no matter how fast I can type on it.
Interviewer: "I heard you were extremely quick at math" Me: "yes, as a matter of fact I am" Interviewer: "Whats 14x27" Me: "49" Interviewer: "that's not even close" me: "yeah, but it was fast" Shamelessly stolen, but yeah, 76% accuracy is only 3/4s of characters typed correctly; if that "works" you could probably just train yourself to not even type the lesser used parts of the alphabet ...
>You may soon see that coworker with the weird monolith style trackball mouse rocking this strange peripheral and claiming he’s upped his efficiency in ways you can’t possibly imagine. Since coding is 20% sitting in meetings, 50% reading code, 10% drawing on whiteboards or sticky notes, 15% drinking coffee, 4.5% fighting impostor syndrome and 0.5% actual typing, I think I am quite safe with my good 'ol QWERTY.
your missing replying on hacker news, chatting on slack, chatting on whatever othe rchat program you use, etc.
>You may soon see that coworker with the weird monolith style trackball mouse rocking this strange peripheral and claiming he’s upped his efficiency in ways you can’t possibly imagine. Since coding is 20% sitting in meetings, 50% reading code, 10% drawing on whiteboards or sticky notes, 15% drinking coffee, 4.5% fighting impostor syndrome and 0.5% actual typing, I think I am quite safe with my good 'ol QWERTY.
The "500 WPM" video is a little suspect. He types literally one memorized sentence and extrapolates a WPM from that one 10 word sentence. I'd like to see him actually type 500 meaningful words in under 60 seconds. Anyway, this is cool but basically just a modern stenography device. Steno has a learning curve problem that makes it so most people won't use it.
Like you can take a look at their quick reference guide shown in the "coder" section of their website.
I don't know how well it will work but it looks viable.
The think I'm mostly worried about is that most human fingers (not thumbs) aren't really designed (or trained) for sideways movement. Does anyone has the necessary anatomy knowledge to know if this has a increased risk to cause health issues if used long term as the main keyboard?
Back in the 90's I worked with a guy who used a Dvorak. Any fans still out there?
I use Dvorak Kinesis Advantage 2. I switched to using copy and paste with the mouse with it since Cmd+c and Cmd+v are so hard to reach.
I don't use it myself - but on macOS there is a separate layout called "Dvorak - QWERTY Command" that shifts the layout to QWERTY when the command key is held to alleviate this issue.
Earlier quoted context omitted.
i don't think there's anything to gain here that you don't already get with good autocompletion. i wonder how a trained stenographer on a chorded keyboard would compare to a trained typist with a good english language model backed autocomplete and a ui built for speed on a classic qwerty keyboard.
I'd be ok with it being "as good" as my current coding setup, at least if it improves my other typing speed. A vast majority of my correspondence these days involves me typing (as I've made , so being able to speed that up would still be cool, though I doubt it's going to be a categorical difference in my day-to-day life.
my understanding is that classic stenography is actually phonetic. so the chords match up to phonemes or phoneme like chunks which are then postprocessed to reconstruct english text.
a new approach using english language could be more data driven. a simple mapping could be one chord to one word with words sorted by frequency and easier chords assigned first. more complicated approaches involve chunking up the words into frequently used chunks and then doing the same.
code is harder, there are frequently reused strings, but they change from technology to technology. overall there is far more entropy in computing than english on a character by character level, so designing a chording scheme that is more efficient and isn't tied too much to a specific domain is actually a really hard problem, especially once you consider that the effectiveness of a given scheme is not only a function of how well it fits the problem (how often the user is actually entering things the scheme was designed for) but also how well users are able to learn the vocabulary of chords and the dexterity to execute them quickly.
Earlier quoted context omitted.
I'm typing even less these days with tools like copilot.
For some reason I don’t like any of this automation tools. I find VSCode unbearable even without copilot. Too many things happen when I type. I prefer linting and that’s about all I want to write my code peacefully. I use vim in iTerm and it’s all I ever need. Jump off to Pycharm to debug if needed.
For the remaining 95%… I’ve configured it to delay doing anything until 10000ms passes so it doesn’t get in the way
If this works like swipe typing on phones, you'll type blazingly fast, but you have to retype each word several times until the AI finally guesses the right one.
Someone capable of decent touch typing on QWERTY will hardly benefit from the additional typing speed IMHO; at least not when factoring in the time spent learning, and the inevitable decrease of typing speed on QWERTY keyboards which will be very hard to avoid when working in a team or multiple locations.