121–130 of 477 posts
Earlier quoted context omitted.
You type a lot more than 0.5% of the time.
Yes, but typing speed is still not too important.
Back in the 90's I worked with a guy who used a Dvorak. Any fans still out there?
Yup! I learned Dvorak probably in 1999 or early 2000s (and I have a coworker who also still uses Dvorak). The kind of people (like me) who got into Dvorak at that time would today probably learn something like Colemak DH, although there are many alternatives available nowadays and a big (discord) scene of folks optimizing and designing both their keyboards and the layouts they use on them. I expect Dvorak will die wi…
The caveat to my perspective is that I don't care where hotkeys are. I minimize mouse use, and with both hands on the keyboard it just doesn't matter very much. I've used emacs and vim with both layouts. My faded recollection with respect to emacs is that it was equivocal, and Dvorak is actually a bit better for vim.
Earlier quoted context omitted.
The accuracy measurement is flawed, because the firmware of the device is deleting chorded letters and retyping the chorded word, which artificially reduces accuracy
If it's happening at the firmware level why wouldn't it just resolve the word internally and output only the completed word to the PC?
Has anyone tried this with coding? It looks like this is very focused towards writing English, which is fine, but as someone who spends a good chunk of my day around code editors, a keyboard that is crap for code editing is a non-starter. However, if it's good for that, I will probably be buying one.
> chorded typing allows the users to input several letters at the same time and have a computer program generate a predicted word. Instead of typing h e l l o, a chorded typer mashes h, e, l, and o to produce the word. It sounds like it relies heavily on autocomplete, which means it's unlikely to be useful for coding instead of just English text.
>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.
You type a lot more than 0.5% of the time.
I'm fairly obsessed with alternative HIDs. I bought the Tap Strap 2 but never broke past the initial learning curve. I'm going to buy a CharaChorder now. I'm also a musician, so I'm really interested to see what types of functionality I could map, given the additional interface dimensions. However, I'll need to test the input lag, typically anything > 20ms is rather noticeable for live music; if they have esports as…
I type ~80WPM with 90%+ accuracy, but I don't find that typing speed is my blocker, rather the speed of a coherent thought I’m on typeracer.com with an average typing speed of 154 WPM with 99% accuracy. I don’t find my thoughts to be limiting for typing purposes.
I just did the practice twice. Once at 100wpm (keyboard twister kind of text). Once at 130wpm (easy sentences). So much variation just from the practice text alone. This is also on a macbook pro keyboard literally on my lap - which I fucking hate and find horrible to type on and mess up on all the time. (I think it is also dysfunctional/semi-broken)
I don't think I could ever hit 150wpm. I just don't see how it's possible with a normal keyboard - at least for me. Never seen anyone do it sustained either. Must be some Speed of thought is mostly the issue for me too though even at 130wpm. If I am saying things faster than that - whatever I am saying is probably not worth reading outside of a chat conversation.
Earlier quoted context omitted.
QWERTY has a steep learning curve as well, it’s just that it’s so ubiquitous that most people don’t question or remember the work that was put into.
> has a steep learning curve just to make the pedantic point, learning curves show skill improvement plotted against time spent/experience, and therefore a steep learning curve means you learn quickly. A shallow learning curve is the difficult one. /pedantry https://en.wikipedia.org/wiki/Learning_curve
> An activity that it is easy to learn the basics of, but difficulty to gain proficiency in, may be described as having "a steep learning curve".
That matches QWERTY exactly.
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.
I don’t think my problem is being able to get the words from my brain into the computer fast enough. My typical HID use case is composing meaningful written communication, a process which is unfortunately much slower than 500wpm.