4 ms·
I'd argue that it has nothing to do with how fast I can type or edit code. It has to do with how fast I can express ideas. Just like I've learned to express id
by snprbob86 14y ago
I'd argue that it has nothing to do with how fast I can type or edit code. It has to do with how fast I can express ideas.
Just like I've learned to express ideas in various programming languages, I've learned to express ideas in Vim. Those ideas are within the domain of text manipulations. Even if I spent the same overall amount of time manipulating text (I don't) the process of getting from point A to point B is smoother and costs me less mental energy. That energy savings translates into better code.
One thing to note here is that, just as with any other notation, there is a learning curve. You must learn the essential complexities of the problem domain, as well as the accidental complexities of the notation. That learning requires deep understanding of fundamentals, memorization of idiosyncrasies, and practice, practice, practice. This is true in mathematics, spoken languages, written languages, programming languages, sheet music, and all the rest!
- ulyssesgrant 14y agoI don't think the two ideas you are talking about are mutually exclusive. I type and edit code faster in vim, and I'm able to accomplish tasks and put down my thoughts faster as well. One lets me accomplish the other, and vice versa.
- snprbob86 14y agoYou're right. Hence why I wrote: > Even if I spent the same overall amount of time manipulating text (I don't) I'm just saying that faster code editing is a side effect of -- or the aggregate view of -- smoother thinking and faster thought expression.