DEV Community


Discussion on: Vim won't make you a more productive developer

drhyde profile image
David Cantrell

Fiddling to make it work well for a new requirement isn't something that should take a significant amount of your time, so I don't worry about it. I've kept my vim config under version control for the last several years, and so I can tell you how often I've mucked about with it. Three times, in the last six years.

So I've spent less time mucking about with my editor config, which is at least a little bit productive, than I have on utterly unproductive stuff like configuring my machine to use the corporate-VPN-of-the-week (I'm up to three this year so far and that's without changing jobs) or on explaining our unchanged deployment process to product managers (about once a month).

But I would never try to push anyone to use vim. I don't care what editor anyone uses. If they want to use Sublime, or emacs, or Komodo, or ed (or even ED) that's fine by me, provided that their code works, meets our coding standards, and passes code review.

Forem Open with the Forem app