Quick tech-tools thread, because I probably won't have time to write this down fully soon. Re: Vim. A few years ago I experimented with both Vim and Emacs. I wound up going back to my previous tools. [1/N]
-
-
But! Now I'm a different / more "traditional" kind of SWE and I'm really feeling the burden of those extra keystrokes. Getting into Vim mode in an IDE is very helpful. [4/N]
Show this thread -
A few lessons: I think
@wycats was exactly right in a 2011 interview when he said that (paraphrasing) *not* diving in headfirst is an underrated way to learn Vim. You can just ease into it, learning one thing after another, without paying huge upfront productivity costs. [5/N]Show this thread -
Relatedly, Vim keybindings in a more recent IDE is, I suspect, a good happy medium for a lot of people. And, as with the point above, this is something that you might feel pressure not to do if you're learning Vim and (thus) reading lots of documentation from Vim purists. [6/N]
Show this thread -
Also, this isn't at all original to me, but it's quite striking: thinking in terms of a distinction between command and insert mode has changed, for the better, the way I think about writing (and not just writing code). [7/N]
Show this thread -
Alternatively phrased: If you're a writer, it's nice to make more explicit to yourself how much metaphysics is encoded in traditional methods of word processing. [8/N]
Show this thread -
Finally, the case of writing software (IDEs and so on) is a neat case study in technological progress. I'd love to read more about it if anyone has suggestions. [9/9]
Show this thread
End of conversation
New conversation -
-
-
@thinkingpoker like I said, baby voice.Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.