This is how I've learned! I'm about 8 years in with vim, but I'm no vim-journeyman; I just learned enough to get started. Movement, find-and-replace, splits. Th

This is how I've learned! I'm about 8 years in with vim, but I'm no vim-journeyman; I just learned enough to get started. Movement, find-and-replace, splits. The basics. And every time I wonder if there's a better way to do whatever I'm doing, I look it up, and - lo and behold - I learn some cool new feature that I can organically introduce into my workflow. Learning vim in this way has been immensely satisfying. I look at time spent in vim as an investment in my career as a software developer. For as long as I'm in this industry, I'm going to need to edit text. vim can do just about anything and everything; will run on any architecture, past, present, or (it's safe to assume) future; and has allowed me to reduce the amount of time that I spend doing repetitive editing tasks.