Show HN: I built an interactive course that helps you learn Vim faster

Post by mypalmike » Sat, Jul 09, 2022, 7:01 PM UTC

azemetre wrote: post #137

mypalmike wrote: post #128

Earlier quoted context omitted.

I've been coding for nearly 40 years and I just don't see any correlation between editor usage and developer productivity. Being able to design and work with complex software systems is what makes a senior dev productive, not which keys they hit to copy and paste.

You should see how slow people are at doing the following: creating a new directory, creating several files, initializing git, and creating a new work tree. While learning vim/emacs and CLTs may not make you a better programmer, but they can absolutely make you better at understanding and using your tools effectively. One simple thing I like to do at every job is setup an ansible playbook for the team I'm working on.…

Post by [deleted] » Sat, Jul 09, 2022, 7:09 PM UTC

stevebmark wrote: post #102

Please just read Practical Vim if you’re going to double down on using Vim. All of these tutorials are the minimal basics. Vim forces you to glue together lots of inefficient commands to manipulate text. I feel frustrated seeing Vim users tout how efficient their editor is when they haven’t learned all of Vim’s nasty bells and whistles you need to actually be efficient at manipulating text. (When you press colon, do…

Post by supernovae » Sat, Jul 09, 2022, 7:13 PM UTC

mtlynch wrote: post #93

johncoltrane wrote: post #4

> Let me know what you guys think about it :) Same as the last time you posted it: learning Vim has nothing to do with muscle memory and doing it outside of Vim is pointless. Plus, the "master Vim" claim is dubious given how basic the lessons seem to be. :help user-manual is easy, built-in, and it goes way beyond this. And it's free.

It's a Show HN. OP's just sharing something they've been working on that they find interesting. No need to dump on it over and over. > Please don't post shallow dismissals, especially of other people's work. A good critical comment teaches us something. https://news.ycombinator.com/newsguidelines.html

Post by azemetre » Sat, Jul 09, 2022, 7:29 PM UTC

mypalmike wrote: post #141

azemetre wrote: post #137

Earlier quoted context omitted.

You should see how slow people are at doing the following: creating a new directory, creating several files, initializing git, and creating a new work tree. While learning vim/emacs and CLTs may not make you a better programmer, but they can absolutely make you better at understanding and using your tools effectively. One simple thing I like to do at every job is setup an ansible playbook for the team I'm working on.…

Command line tools are great. Environment setup is great. Ansible is great. I don't know why you are conflating these things with the editor one uses. *Edit: Why the downvote? Tell me what I'm missing instead.

Post by MAGZine » Sat, Jul 09, 2022, 7:32 PM UTC

immrammc wrote: post #99

Arisaka1 wrote: post #95

I once tried to migrate from VS Code to Neovim. I use TypeScript at work, and use many languages for my side projects. But the worst part was making Vim provide with things that you'd expect programming editors to have. So many options, what's best is up to opinion, integrating language servers, getting intellisense to work as you would expect, searching the project folder for file names. Then I realized that all I'm…

If you’re trying to achieve VS Code with the keyboard navigation of vim, have you given the VSCode vim plugin a try? I’ve had positive experiences mixing editors/IDEs with a vim plugin to get the best of both for my workflow.