Vim is a powerful text editor that improves coding speed & efficiency through its shortcut-based Vim language. While learning Vim can be challenging, it is a valuable skill that can enhance your career as a computer professional.
I’ve switched to vim on a whim few months ago, and it still is a pretty fun and satisfying experience. I couldn’t get LazyVim to properly work on our Unity project, since the LSP can’t handle the hundreds of projects it generates, but IdeaVim in Rider works pretty much the same, as far as the movements are considered.
However, the important thing is that I said fun and satisfying, not faster and efficient. I still make mistakes, I have to look into a keybind reference sheet every time I want to do something I’m sure has to have a special keybind but I’ve forgotten which one it is, but once you do that it feels good.
Slowly but surely learning new stuff, getting the hang of some motions you use often, not having to reach for your mouse, all of that feels good. It’s still no way near the speed or efficiency of me just clicking the damn mouse, instead of fumbling around with VIM modes, undoing random actions because I missed one important key and now half of my text is gone, or just remembering that your clipboards get overridden by almost any action unless you do it differently.
So, if you want to get efficient and quicker in your programming, I highly recommend checking the keybind section of your IDE, and learning the few important keybinds it has, such as jump to next function/next parameter, search symbols, and the like. That will make you more efficient.
If, on the other hand, you want your editing to be a skill you can slowly continue mastering, eventually (after years of use) min-maxing, but always having some cool new things to learn that will feel good, them vim is pretty nice for that.
Just don’t expect it will make you faster or more efficient.
Just don’t expect it will make you faster or more efficient.
It will, but it requires you spend a lot of time dealing with being slow and wanting to give up and reach for the mouse.
I swapped keyboard layouts (to a 52 key split layout) and it took me around 2-3 weeks of typing slow, hitting the wrong keys, and keeping several printed sheets (for all of the keyboard layers) on my desk in order to learn the layout. It was frustrating and it would have been a lot easier to just grab a standard keyboard but, in the end, it was worth it.
Learning vimkeys/application hotkeys does take a while and it is much easier to avoid it for any given task. Just grab the mouse and avoid the frustration of having to try to remember the hotkey (or, even worse, look it up). But if you can avoid that and force yourself through the uncomfortable frustration. You’ll find that the time investment is worth it.
I’m in a similar boat. The difference for me is that I can definitely tell times where I’m faster. But there are still times where I fumble around. I know that eventually, I’ll be way faster using vim motions than I ever was without them.
When I first started actually trying to use it to do work, it felt pretty bad. But once I got over the hump it felt better.
I think I’m at the point where I’m at least as fast as I used to be, if not slightly faster.
I’ve switched to vim on a whim few months ago, and it still is a pretty fun and satisfying experience. I couldn’t get LazyVim to properly work on our Unity project, since the LSP can’t handle the hundreds of projects it generates, but IdeaVim in Rider works pretty much the same, as far as the movements are considered.
However, the important thing is that I said fun and satisfying, not faster and efficient. I still make mistakes, I have to look into a keybind reference sheet every time I want to do something I’m sure has to have a special keybind but I’ve forgotten which one it is, but once you do that it feels good.
Slowly but surely learning new stuff, getting the hang of some motions you use often, not having to reach for your mouse, all of that feels good. It’s still no way near the speed or efficiency of me just clicking the damn mouse, instead of fumbling around with VIM modes, undoing random actions because I missed one important key and now half of my text is gone, or just remembering that your clipboards get overridden by almost any action unless you do it differently.
So, if you want to get efficient and quicker in your programming, I highly recommend checking the keybind section of your IDE, and learning the few important keybinds it has, such as jump to next function/next parameter, search symbols, and the like. That will make you more efficient.
If, on the other hand, you want your editing to be a skill you can slowly continue mastering, eventually (after years of use) min-maxing, but always having some cool new things to learn that will feel good, them vim is pretty nice for that.
Just don’t expect it will make you faster or more efficient.
It will, but it requires you spend a lot of time dealing with being slow and wanting to give up and reach for the mouse.
I swapped keyboard layouts (to a 52 key split layout) and it took me around 2-3 weeks of typing slow, hitting the wrong keys, and keeping several printed sheets (for all of the keyboard layers) on my desk in order to learn the layout. It was frustrating and it would have been a lot easier to just grab a standard keyboard but, in the end, it was worth it.
Learning vimkeys/application hotkeys does take a while and it is much easier to avoid it for any given task. Just grab the mouse and avoid the frustration of having to try to remember the hotkey (or, even worse, look it up). But if you can avoid that and force yourself through the uncomfortable frustration. You’ll find that the time investment is worth it.
I’m in a similar boat. The difference for me is that I can definitely tell times where I’m faster. But there are still times where I fumble around. I know that eventually, I’ll be way faster using vim motions than I ever was without them.
When I first started actually trying to use it to do work, it felt pretty bad. But once I got over the hump it felt better.
I think I’m at the point where I’m at least as fast as I used to be, if not slightly faster.