3 ms·
It may be that muscle memory in editors is created like this: 1. Identify a problem 2. Think what I need to do to fix it 3. Decide what keys I need to pr
by SoftwareMaven 14y ago
It may be that muscle memory in editors is created like this:
1. Identify a problem
2. Think what I need to do to fix it
3. Decide what keys I need to press
4. Direct fingers to press keys
And that gets shortened eventually to:
1. Identify a problem
2. Direct fingers to press keys
If that is the case, then this might be a really good first step towards that process. I would certainly not look to me for that initial feedback.
Perhaps if I could try more complex things (that I don't have current muscle memory for), I would find it incredibly useful.
Either way, getting better at using your tools is always a good thing.
- commandar 14y agoThat's actually a very good description of my experience learning vim so far. It starts off being a very conscious set of actions when first learning a new command -- e.g., "I want to change the word under the cursor... cw" -- before becoming something that happens subconsciously as I become more familiar with a set of commands. Where this site at least appears to work well is that once I started to understand vim commands as verbs and nouns, I started seeing actions as sentences. The drills here seem to reinforce that sentence structure type approach. I can see it being less useful for somebody that is familiar enough with their editor thatt it's already become a mostly subconscious process. While I'm comfortable using vim for the most part, I'm very far from a high level of proficiency with it.