I would suggest that people new to vim not trying to learn all of vim quickly. I think they are better off learning enough just to get by at first. Just the b

I would suggest that people new to vim not trying to learn all of vim quickly. I think they are better off learning enough just to get by at first. Just the basics. Then learn a new key sequence that solves an immediate problem, understand what it's doing and why it works, and add it to their set of tools they use daily. Muscle memory, like you said. They should keep adding them as they need them, and keep using the new ones they've acquired whenever the need for it comes up. When I started learning vi, the learning curve was very steep just to get the very basics down. It wasn't until I learned a few commands out of sheer frustration that I realized how powerful it was. Diving into that was too much, though, so I started learning small bits here and there and internalizing them. That concept has worked well for me in the 25-ish years I've been using vi or (later) vim. So I would suggest maybe a curated list of problems that need to be solved and their vim solutions, with a method of searching for them when needed and a way of suggesting one of those problems/solutions every so often. Kind of like a daily/weekly helpful tip that gives them out in order of complexity. These would be things like how to swap two lines, keyword search and replace, how to insert something at the start of a set of lines, how to join lines, how to use buffers, etc. Ideally, a vim plugin could watch for the basic ways of doing more complicated things, like someone deleting the same number of characters one at a time on each line, repeatedly, and let them know about repeat counts, or seeing someone deleting characters one at a time stopping at a space and typing new text in multiple times and let them know about "ce".