451–460 of 477 posts
Earlier quoted context omitted.
Yes, but typing speed is still not too important.
There is some threshold where it absolutely impacts productivity. If you haven't seen this in action, you're lucky, I've ran into more than one Engineer who is otherwise very smart but somehow never learned to type.
Earlier quoted context omitted.
It's a nightmare if you're writing in two different languages at the same time, eg. French sentence with English words in it. I often have to disable one or the other and live with most words being red underlined, because autocorrects are just not great at guessing what language I'm using. BTW, if anyone from Alexa, Apple or Google is reading this, please have someone work on this. It's been 10 years since I've been…
I'm using Google's keyboard on Android in dual language mode, it works pretty decent.
Also amusing is that autocorrect, even while in English mode, suggests the bear emoji when I type "ours" or the cat when I type "chat".
Earlier quoted context omitted.
So is it autocorrecting helo to hello? Predictive tweaks aren't good in a keyboard, you want everything to be intentional, or you'll lose time and patience correcting things. Spellcheck should be post hoc imho.
I tested that by turning off Apple's autocorrect on my Mac. It turns out I'm a less accurate typist than I thought. Now, I'm happy to let autocorrect put right all "teh" mistakes I make. It's annoying when I want to type something unusual, but that happens less often than I make mistakes, so the balance is in autocorrect's favour.
Earlier quoted context omitted.
>since private computer chatting essentially died out News to me
Might depend on friends. I meant at a computer with keyboard, not on a phone.
...and from my understanding WhatsApp is very common in Europe, which can also be used from the web.
Earlier quoted context omitted.
playing the devil's advocate, typing speed is important for these reasons: 1. It allows for minimal disruption to thinking process, close to 90% of the time even when coding is not actively typing, but when typing is subconscious and fast it removes the potential of where it interrupts the thinking process. 2. While this has no bearing on individual case (It would be Bayesian, some people consider that to be heretic)…
Autocomplete makes programming very different from normal typing. I don't need to type fast, I use my keyboard to trigger lists of options that I pick from. Modern programming is a contemplative interaction with the IDE/language server, normal typing should only come into play when you write comments.
Earlier quoted context omitted.
The learning curve for stenography is much higher. With a keyboard, the buttons do exactly what they say and that only. With a stenography machine, every possible combination of buttons does a different thing. When typing the word "Unprepared" on a keyboard, you just have to look at the buttons and find each of the ones with those labels, and hit them in sequence. To type the word "Unprepared" on a steno machine, you…
Keyboards that use multiplexed row/column electrical matrix will not allow you to detect more than two keys in any box pattern simultaneously. So pressing more than two keys on that virtual steno keyboard is impossible on a regular keyboard (for many key combinations).
Obviously if you're gonna use it as you daily driver, you'd want to get a NKRO keyboard, but the "hold one key and tap the rest" trick works for the web demo.
Earlier quoted context omitted.
In addition to the other reply, if they did that the test would be so far from real world typing to be meaningless and nothing but an inconsequential curiosity. Only in tests is there an option to check against what is expected. In the real world you could at most apply some dictionary and grammar checks, and we know those can go either way. Those tools don't know what you actually wanted to write after all, and stil…
Even if you type without making corrections, you still need to go back and make corrections, so you need an estimate for the time spent on corrections. Forcing corrections midstream is a decent approximation.
1. used a fuzzy autocorrect of the same kind mobile OSes and word processors have (not correcting to the known text, but instead only doing what such logic usually does — only attempting to correct words if they're not recognized as words; and only moving them to the lowest-Levenstein-distance match.)
2. treated words that are correct after autocorrection as being "correct", with no ding to accuracy.
Since accuracy is about how much extra time and effort the human typist has to spend to get the text correct, and since text that can be auto-corrected requires zero human time and effort to correct, it shouldn't really be considered incorrect.
Or, to put that another way: if I'm typing really fast on my phone's keyboard, and all the right words are ending up on the screen, what does it matter if I'm hitting the right keys with my thumbs? It's the WPM and accuracy of the cybernetic system composed of me + the auto-correct that matters.
In that sense, you can sort of think of an auto-correct as actually being a very similar thing to a stenographic keyboard (at least, in the hands of a person who knows how to take advantage of it): it's really a system to enable accelerated typing, by allowing you to key in the letters of a word out-of-order or simultaneously and have the word come out in-order.
Earlier quoted context omitted.
Ah yeah, that's fair. I could defend that as cost/benefit analysis, but I'm with you - let's push the limits and worry about utility evaluation later! (I literally have a chording keyboard on my desk right now, so I'm quite serious when I say I want to push the limits:])
What hardware/software are you using? I’ve looked into it a few times, but the cost benefit hasn’t been there for me for doing the research without knowing anything about it yet. Do you code with it as well, or is it primarily chat/browsing/etc?
Earlier quoted context omitted.
Autocomplete makes programming very different from normal typing. I don't need to type fast, I use my keyboard to trigger lists of options that I pick from. Modern programming is a contemplative interaction with the IDE/language server, normal typing should only come into play when you write comments.
Autocomplete is just a very small subset of modal editing paradigm, the entire editing process, both typing and key shortcuts (i.e. picking options) should be treated as the same.