Use vim to look cool! don't!

Search for a command to run...

Partially agreed on touch typing.. but does not agree on feeling defeated and going back to vs code 😌.. am not a touch typer.. but I managed to enjoy the developers experience using vim.. and managed to uplift my productivity… But I know if I could touch type I could do better..
Thanks for the feedback, and I highly recommend picking up touch typing, it's never too late..
Remember my post about switching to VSCode? Well, plot twist: the very next day after publishing it, I switched to WebStorm. And guess what? I've been on JetBrains IDEs ever since. I know, I know. Another "why I switched editors" post. But hear me ou...

I had been doing some basic interpreter work in Go and wanted to redo it in another language to solidify my understanding. Naturally, I chose Odin, it’s another great language, with a Go-like, easy-to-approach syntax and no unnecessary complexity. I ...

Why Emacs Keybindings? I've always preferred Emacs-style editing, especially the way it handles cursor movement and text manipulation. Even though I have switched to using VSCode for most of my development work, I often found myself missing the intui...

In my previous post about building C/C++ projects with CMake, I shared a simple CMakeLists.txt setup for compiling a basic project. Today, I’ll dive into a specific need that many developers encounter: linking libraries directly from project folders ...

Some time ago, I wrote a post about using Vim to look cool and why that’s not a good idea. Now, funny enough, here I am—having switched to VSCode after years of hopping between Vim and Emacs. This isn’t one of those "Vim sucks, I'm going back to VSCo...

A YouTube video I watch recently suggested to learn vim motions because "you look badass" when you use them. I've also seen many more videos where people say things like "I'm going back to vscode because:, vim sucks, emacs sucks, I don't want to look cool, I want to get productive, etc". All these videos has one common theme: they tried vim to look cool! and they'd rather do work than look cool. If you are learning vim because you want to look cool that's a recipe to disappointment.
I believe everyone should use tools they like/enjoy the most, also which make them productive the most. A code editor/ide is just a tool, but a very important one for a developer. Because it's the main tool you use to read/write/modify code. So whichever you pick you need to learn how to use it efficiently to browse through a code base or edit efficiently.
Whether you use vscode, vim, neovim, emacs you should learn how to use it. I get it, it's so much easier to get up and running with vscode because you don't have to write a lot of manual configuration files.
I have seen people exclusively using the sidebar file tree to open each file in vscode, that's a very inefficient way to use vscode. You should learn how to use the fuzzy file finder that's already pre configured for you. Just hit `C+p` then start searching for what you want.
Also there are many more editing features of vscode like multiple lines, duplicate lines, etc, you should learn these features an start adding those as a part of your daily routine.
If you cannot touch type on whatever keyboard layout you use forget about trying vim, looking cool., first learn to touch type. If you really want to look cool touch typing can help you do that and get more productive at the same time. Typing is something that you have to do dispite whatever editor/ide you use. So it's not like learning how to use a different text editor and spending hours, days learning how to use it and end up not switching.
And especially you want to really get in to any keyboard driven text editor like vim or emacs and you cannot yet touch type, then you should first master touch typing. Trying to use a keyboard-driven text editor without being able to touch type is like getting a real sports car as a 2-year-old. You'll learn all the fancy features but feel defeated when try to use them, because you are not good at the keyboard. Then you can do another "vim sucks going back to vscode" YouTube video.