3 ms·
My muscular memory of Vim is so strong, I’d wager I could code even faster and more powerfully with a proper brain interface.
by xwdv 5y ago
My muscular memory of Vim is so strong, I’d wager I could code even faster and more powerfully with a proper brain interface.
- nine_k 5y agoThis always puzzles me a but. Is it the typing speed that limits the amount and quality of code one can write in a day? To me, it's mostly finding out things about the subject area, finding the right APIs, code search. Of course, when typing is fast enough so that you never break your flow, it is important.
- Treegarden 5y agoThe whole point of vim is normal mode, not insert mode. Insert mode is just typing, but normal mode is code or file navigation. Its not about typing speed but deliberate action and precision - with vim you need only a couple of keystrokes. In this context speed refers not to typing code but to doing what you mentioned quicker (at least for code search, jump to definition, go back in cursor history) but there is vimium for the web which helps with research. My hands are slowly failing me and vim is a god send.
- czrnb 5y agoI think that in order to not break your flow, you should be able to translate your thoughts (the answer you found) to code or text as fast as possible. Typing slowly when you know what you want to write can be frustrating for one (lowering your motivation), but most importantly is too trivial a task to prevent you from thinking at the same time (and thus parasitic thoughts can break your flow). A HCI that can help you write your code as you think of it (and maybe log the thought process for future reference !) would be awesome on that front.
- Cthulhu_ 5y agoI doubt so; I think that editing text via the brain would take a lot of focus to think the right things at the right time. In practice I think your brain would go one direction and the interpreter would type that, so then you'd think "no wait go back I was just distracted by a squirrel" and the whole document is deleted. Or something.