{"componentChunkName":"component---src-templates-blog-post-jsx","path":"/content/posts/vim-is-not-a-monster","webpackCompilationHash":"0fb77888eafce0e19778","result":{"data":{"markdownRemark":{"frontmatter":{"title":"Vim is not a monster."},"html":"

\n \n \n \n \n

\n
\n

The first time I heard about Vim I didn’t even know what it was. I started to\nsearch about that and asking around … and in general people avoid to use that.\nSome say it is time consuming learning vim, others don’t want to suffer,\nothers say that you can really make your workflow more efficient, but in\ngeneral, people don’t want to go into it.

\n
\n

Why I Choose Vim

\n

The rumours about the “end” of the Atom made me start thinking that I should\nstart using VS code, but I wanted to try something different. In the company\nwhere I work, there’s a lot of people using Vim, and that made me more curious\nabout learning it. Two weeks ago, I had the opportunity to have a vim session\nwith a Vim enthusiast, but before starting, he asked me if I really, really\nwanted to do it. He warned me that I would face a reasonable level of\nfrustration … but that didn’t keep me from doing it.

\n

Vim was not completely strange for me. Before this session, I already knew some\nbasics that I learned by using Vimtutor. To practice what I learned on vim tutor\nand while using Atom, I installed a vim plugin to start using some commands. The\nexperience was surprisingly nice. Without a dramatic change in my workflow, I\ncould try it, but soon I saw a problem with that.

\n

By using a vim plugin, I never got out of my comfort zone, and I could always\nstill use the code editor as I used it before. Sometimes I found it confusing to\nhave two ways to use the editor (the atom way or the vim way), and as a matter\nof laziness, I opted to keep using my regular shortcuts. But, if I wanted to\njump into Vim, the better way to do it is used it and configure it.

\n

That was the turning point, and since then, I’m forcing myself to use Vim\nexclusively. I know that it will slow down my workflow for a while, but I\nbelieve that soon, I will know enough to use Vim to my advantage.

\n

Pain points and findings

\n

After I made this decision, and because I’m a frontend developer, I started\nlooking for a vim setup that fulfilled my frontend needs, and I found one.\nVictorVoid.

\n

At that time, I thought this was awesome, and I started using it. After that vim\nsession, my friend advised me to uninstall that ready setup, and start with the\nessential plugins. I had so many plugins installed that I didn’t know what their\nfunctions were. I only knew that everything was working. I also realize that the\nfewer plugins I have, the better, and some commands are personal. Along with\ntime, I will create my commands if I feel like it. It has been almost a month\nsince I started using Vim. I’m still struggling and I probably will for a while,\nbut I see some improvements already. Besides that, I’m improving my skills on\nthe terminal, and I started collecting information to “create” my .dotfiles and\ngit-scripts.

\n

Some tips to learn vim

\n

Use post-its to learn the commands, and put them on the bottom of your screen.\nRemove them once you have these commands in your memory and you don’t need to\nlook at the post-its anymore, Simple!!

\n

In fact, this is useful for other things too, like memorizing git scripts.

\n

→ I found a cool tutorial from Thoughtbot

\n

→\nYoutube channel with nice screencasts

"}},"pageContext":{"isCreatedByStatefulCreatePages":false,"pathSlug":"/content/posts/vim-is-not-a-monster","previous":{"frontmatter":{"path":"/content/posts/from-chemical-to-frontend"}},"next":{"frontmatter":{"path":"/content/posts/tnds-challenge-week"}}}}}