So use VSCode while you teach yourself vim. More than a linter, it also delivers rich contextual guidance to help developers understand why there is an issue, assess the risk and educate them on how to fix it. It is OK if you have to use an IDE (currently I only use an IDE for java development, so I have little choice) SonarLint is a free IDE extension to find and fix coding issues in real-time, flagging issues as you code, just like a spell-checker. Managing files, buffers and workflow is half of the value of vim/neovim. Once it isn't hard anymore you will blow yourself away at how much more efficiently you edit files.Īlso vim keybindings in a mouse driven editor does not cut it. Settling on lesser editors out of laziness is exactly the attitude that results in shitty the engineering. ![]() But as you use it more, as long as your usage goes over 40% of the time, in 6 months you will understand why most of the world's too engineers use it. It will infuriate you for 6 weeks, make you cry for another 2 Start using it 20% of the time on single file edits, watch youtube videos about it and teach yourself vim gestures. If you want a real workflow that gives you ultimate performance, customization and speed you need to use a modal editor, I suggest NeoVim. All of these tools are built in a mouse-driven world, they are designed not for engineers, but office monkeys. ![]() So here is the deal man, bottom line you want to write code.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |