[brightball]

If you do any amount of work via command line or SSH, you need to be competent with one of them. I've been using vim for 18 years now and I'd consider myself a barely competent vim user at this point.

I know enough to use it, but not enough to like it.

For virtually all work where I don't have to use a terminal editor, I use Sublime/Textmate or one of the language specific Jetbrains IntelliJ derivatives. The "jump-to-declaration" functionality of Jetbrains is so smooth and so good that I actually have a hard time not having it available now.

Truly useful things get committed to muscle memory almost immediately.

[falsedan]

  > If you do any amount of work via command line or SSH,
  > you need to be competent with one of them.

The one you need to be competent with is vi: it's part of the Single UNIS specification, so practically all random hosts you ever SSH to will have /bin/vi. This comes in handy when you're paged at 3am by a host you've never seen before, and you want to change some code quickly so you can get back to sleep. Being familiar with basic vi will save you time and potentially making an error scp'ing files from your dev host (which has your editor set up just the right way).