Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Build muscle memory with your favorite editor

shortcutfoo.com

Post reply on HN
Print view View original

21–30 of 122 posts

Re: Build muscle memory with your favorite editor

#21

Post by dchuk »

vadman wrote: post #10

I have to enable way too much stuff in NoScript to proceed when I actually click on an editor button. Giving permissions just to shortcutfoo is not enough. NoScript also shows airbrake.io, stripe.com, olark.com. I don't know what any of those are, so I'm not enabling them. So I cannot use your website, as cool as the premise sounds :/

In order:

1) exception tracking api 2) payment processing api 3) live, on-page chat tool

noscript is cool and all, but those 3 above listed items are perfectly fine to permanently enable on all sites

Re: Build muscle memory with your favorite editor

#23

Post by czzarr »

jlebar wrote: post #13

I wonder if this actually teaches you the right kind of muscle memory. I have no difficulty with hjkl for navigating in Vim, but I had trouble associating those keys with the string "move one character". Mapping from the description of the command to the key is not the kind of muscle memory I use all day.

even though the project looks good, this is spot on.

Re: Build muscle memory with your favorite editor

#24

Post by dlikhten »

danso wrote: post #8

This is neat, but one thing it misses is the "reward." Not a gamification award, but the visual feedback from hitting a keyboard shortcut and seeing it actually happen, which helps reinforce the connection from muscle-action to program-action. Another important component is seeing the scenario. Seeing the words "Duplicate line" doesn't hit the same neurons as seeing the situation in the text-editor that toggles my br…

False. Why gamify, I actually found this incredibly useful all in itself.

Re: Build muscle memory with your favorite editor

#25

Post by jlongster »

jlebar wrote: post #13

I wonder if this actually teaches you the right kind of muscle memory. I have no difficulty with hjkl for navigating in Vim, but I had trouble associating those keys with the string "move one character". Mapping from the description of the command to the key is not the kind of muscle memory I use all day.

Agreed, this is the strangest way to learn an editor. The whole point of pressing a command is to see what it actually does. Connecting that action to your muscle movements is what you want.

Re: Build muscle memory with your favorite editor

#26

Post by jbigelow76 »

mej10 wrote: post #15
danso wrote: post #8

This is neat, but one thing it misses is the "reward." Not a gamification award, but the visual feedback from hitting a keyboard shortcut and seeing it actually happen, which helps reinforce the connection from muscle-action to program-action. Another important component is seeing the scenario. Seeing the words "Duplicate line" doesn't hit the same neurons as seeing the situation in the text-editor that toggles my br…

If it had "seeing the scenario", I would've immediately bought it and would have been willing to pay at least $15.

I agree that the visual correlation to the shortcuts is important. It's a very nicely designed and implemented idea, but I think I would need that visual component to warrant paying for it (the visual component would also justify a higher price for me as well.)

Re: Build muscle memory with your favorite editor

#29

Post by sophacles »

Cool site, but a minor annoyance, is that some editors, like vim, have multiple ways of accomplishing a task. For instance move to line 4 can be done with 4G or 4gg, but only accepts 4G, which is frustrating as I've already internalized 4gg :) I'm sure there are others.

Re: Build muscle memory with your favorite editor

#30

Post by [deleted] »

dlikhten wrote: post #24
danso wrote: post #8

This is neat, but one thing it misses is the "reward." Not a gamification award, but the visual feedback from hitting a keyboard shortcut and seeing it actually happen, which helps reinforce the connection from muscle-action to program-action. Another important component is seeing the scenario. Seeing the words "Duplicate line" doesn't hit the same neurons as seeing the situation in the text-editor that toggles my br…

False. Why gamify, I actually found this incredibly useful all in itself.

[deleted]
Post reply on HN