To get to
> new FoobarGenerator().Create(new FoobarOptions { foo = 3 });
, the keystrokes would be more like
< new Fo<tab><enter>
> new FoobarGenerator()
< .Cr<tab><enter>
> new FoobarGenerator().Create(
< new<tab><enter>
> new FoobarGenerator().Create(new FoobarOptions
< { f<tab><enter>
> new FoobarGenerator().Create(new FoobarOptions { foo =
< 3 } );
> new FoobarGenerator().Create(new FoobarOptions { foo = 3 });
Or any of the big 3 Java IDEs.
Although this was not a great experience on my already slow two core macbook.
The results were pretty amazing though.
Worst case, it’s nice to get one’s job done faster to make time for other things.
You can always take your hands off the keyboard periodically if you want to write less.
For vim to become worth your time to learn to use effectively, you have to have a purpose to use it quite a lot. But it takes quite a lot of time, and causes quite a lot of errors in the mean time. Eventually, you are left with a skill and a tool that are a pleasure to use, but you literally must spend time actively learning how to use it. You cannot just pick it up, because you need to first memorize key combinations and the behavior of various modes. Then, you need to actually practice them.
And this proposed solution is even worse, because it suffers not only from the "vim effect", but from the "vim config effect", where you not only need to memorize, and practice, but actively configure your custom solution, which can take tons of time; is subject to loss/deletion; and is not universally available.
And god help me, what about programming? I honestly do not want to even think about multi-layered completions wreaking their havoc on everything I write, and the only alternative is different completions for different types of environments--even more cognitive load.
This seeks efficiency as represented by speed, but ignores efficiency as represented by ubiquity, generality, and low cognitive load.
If I want to get from point A to point B as quickly as possible, it is more efficient to run. If I want to get from point A to point B with the minimum energy expenditure, it is more efficient to walk. To be truly efficient, you need smart, balanced goals.
Everything you wrote about considering tradeoffs is sound, but is being misapplied because you’re overestimating the difficulty and underestimating the benefit due to placing too low a value on words.
Personally, the best tool for typing productivity I ever have used is a keyboard with no letters on the key caps. It also means I'm the only person in my immediate circle that can use my computer at all. My wife literally can't use my PC.
If you want to spend your time that way, that's cool with me. I like vim. Such things have their place. Personally, I suspect this doesn't solve any problems I have.
I do concede this doesn’t solve any problems of yours as you don’t value what you do with your keyboard very much.
Efficiency for me is not the same as efficiency for you. Deal with it.
I'll also add that something like vim is specialized and very useful. It is easier to use vim in a mouseless environment, which is sometimes a necessity. I use it fairly well, and it has paid dividends on the time invested. I can appreciate the value of a good tool.
But typing speed is not the same as efficiency because standards are efficient in their own way. I'm sure you'll say "oh, you don't value words and have nothing important to say", but that's a ridiculous argument. It is simply that, in my opinion, this type of thing is not worth the overhead it creates, much like extremely customized vim configs. Time is invested in the pursuit of efficiency, and it is never returned. One day the config ceases to function correctly, or your friend/coworker/family member tries to use the keyboard and can't use it effectively, so it gets disabled.
Nano probably works too but I'm not nearly as proficient in it, so... vim!
I only learned to type at about 20-30 words per minute, still faster than many now but slow the measure of typists, and that's easily fast enough to keep up with my thoughts.
They can certainly type faster than the average 50-year old, but they can't touch type (or only partially).
It's odd that in the day and age of a lot of computer related work we don't teach touch-typing in schools anymore.
However, some do benefit from the increased speed, some increase the speed of their thinking to match their potential output. Others benefit from the reduced delay between thinking and writing or editing a thought, analogous in software to working with a fast compile time or a dynamic repl.
But the sustained part matters there. Personally, my desire to write long-form text is extremely bursty.
If I'm making notes during a discussion, I might not write anything for a considerable time. However, when an important point is made, I want to record it as quickly and passively as possible, so I can stay connected to whatever else is being said.
If I'm thinking deeply about something, again I might not write anything for a long time. Then if the idea I've been searching for all week clicks, I might make a lot of notes over the next couple of minutes, while the line of reasoning is completely clear in my mind.
I type English text at a comparable speed to a professional secretary, but a way of recording important thoughts even faster when I encounter them would be valuable to me. The same goes for concepts that aren't plain English, too, such as code, mathematics or some sort of diagram.
Over 98% of the prose was written by voice, and because of the headset's wireless range, I was able to wander around the house while thinking about what to say, with dragon happily riding down what I said and easily letting me correct when it made mistakes. I got very good at saying "full stop new paragraph" or, "select line, quote that, go back" to quote lines of dialogue. I expected to have to learn a million commands by rote memorization, but it seems like it became second nature within a day or two for first draft noveling purposes, I have no doubt that medical or legal uses have more advanced commands, but for writing a 50,000 plus word draft it was fine.
If you don't want to pay $300 for nuance dragon, I got scarily good results from trying out Microsoft office online word dictation via office 365 about 2 months ago via a $60 bluetooth headset for wfh.
I won't rely on the latter service myself because it is not offline speech recognition, and can be taken away at the flip of a switch, but for trying out if speech recognition is worth it for you to pay $200 on eBay or $300 in the store for dragon, it is certainly a useful feature to get off the ground.
(I argue a lot with Alexa because she keeps getting stuff wrong even when I enunciate slowly. It is very annoying.)
The good news is, dragon appears to to learn which of the two word variations you use more often and begins to weight its word recognition towards those cases instead.
If your REPL loop[1] gets faster by increasing your typing speed, can you get more of your ideas out there whether you're a blogger, author or coder?
[1] read-eval-print-loop^2
I'm really not convinced Dvorak intrinsically speeds up typing
Very neat stuff.
Additionally, beyond Dvorak, is there a better way to increase typing speed than spending what must be hours and hours building a bespoke solution for each one of your machines? And what is the cost of the inevitable tsunami of errors you make in the learning process? Are these neural pathways more valuable than say, learning a new language or practicing a different skill?