I use emacs with evil and been using it for over a decade now. However, I use VSCode for web development and Rider for game development as the integrations are superior with vim extensions for those IDEs. What you are looking for is a set of principles that make theses editors better. You can take baby steps towards it and 1 - 2 weeks is very limited time if you want to change your editing style (It's like learning a new language).
1. Modal editing (VIM / Evil): Install vim extension pack[1][2][3] for VSCode. This should give a good starter pack.
2. Practice:
- Disable the arrow keys using keymapping in VSCode or with a keyboard customization (s/w or h/w).
- Disconnect the mouse
- Practice long writing / code editing sessions where your productivity doesn't matter. You are learning.
- Start with simple navigation (hjkl, go to line)
- Use numeric prefixes
- Begin using text manipulation commands (yi" or di> for example)
- Use normal mode keys for window navigation (spc + w + h for example)
Once you get comfortable with this you should already see a decent leap in comfort/experience and almost zero mouse usage.
3. Next install emacs with a configuration repository[4]. Most of your practice in VSCode vim should apply almost directly.
4. With emacs, you have a vast operating surface. You can choose to use it just as your editor or you can use it as an operating system: email, calendering, note taking, calculations, twitter, rss, text based browser, file manager, http request playground etc. Org mode is essential emacs experience. You can add the rest of them very slowly
This is good advice. The "Zaiste Programming" [1] is a nice intro to Doom Emacs.
I'd say using Vim Keybindings in VSCode, being able to use Vim when on some remote machine and using Doom Emacs with its included packages is a good approach for improving without investing too much time.
1. Modal editing (VIM / Evil): Install vim extension pack[1][2][3] for VSCode. This should give a good starter pack.
2. Practice:
3. Next install emacs with a configuration repository[4]. Most of your practice in VSCode vim should apply almost directly.4. With emacs, you have a vast operating surface. You can choose to use it just as your editor or you can use it as an operating system: email, calendering, note taking, calculations, twitter, rss, text based browser, file manager, http request playground etc. Org mode is essential emacs experience. You can add the rest of them very slowly
[1]: vscodevim.vim: https://marketplace.visualstudio.com/items?itemName=vscodevi...
[2]: vspacecode.vspacecode: https://marketplace.visualstudio.com/items?itemName=VSpaceCo...
[3]: vspacecode.whichkey: https://marketplace.visualstudio.com/items?itemName=VSpaceCo...
[4]: doom emacs: https://github.com/doomemacs/doomemacs