I'm now using this strategy whenever I want to change something like a common command or key binding--essentially anything that is a habit I don't have to think about.
Another thing to note is that it really helps if you come up with the alias or new key combination yourself. I find it takes almost no effort to memorize a key binding I choose myself as opposed to remembering a new one that comes with the tool itself.
" disable arrow keys
nnoremap <Up> <nop>
nnoremap <Down> <nop>
nnoremap <Left> <nop>
nnoremap <Right> <nop>A bunch of people I know do use the arrow keys to move around, and it's quite a loss. You don't gain that much just by being on the home row, of course, but there is some gain. However, the real win comes when you start using higher-level movement commands and moving by word/line/paragraph/expression/whatever. People used to the arrow keys will not be able to take advantage of these nice commands nearly as easily.
Aliases are not expanded when the shell is not interactive,
unless the expand_aliases shell option is set using shopt (see
the description of shopt under SHELL BUILTIN COMMANDS below).
One trick I've learned, if you want to make sure you get the benefit of this sort of approach, is to ensure that the new alias is not just possible, but mandatory. If you map "git commit" to something, you should make it no longer possible to type "git commit" instead of your new alias, and doing so should pop up the correction. This can also be used to move keys around; turn your Caps Lock into a Control key, you'll never use it, but if you unmap the left Control key at the same time, you'll find you've adjusted in about 5 uncomfortable minutes. It's fast enough to be worth experimenting with.