4 ms·
if I saw this sort of stuff in my codebase... Your codebase should be optimized for reading. Your aliases file should be optimized for very, very frequent typi
by mechanical_fish 15y ago
if I saw this sort of stuff in my codebase...
Your codebase should be optimized for reading. Your aliases file should be optimized for very, very frequent typing.
These are different goals, so naturally the solutions look different.
- 5teev 15y agoTyping on the command line is not like typing in a code file: it's perhaps the least forgiving environment for typos, and tiny mistakes can have huge consequences. A good typist can re-type the correct text after the command finishes--maybe a moment too late. A good coder takes pains to avoid the mistake in the first place.
- mechanical_fish 15y agotiny mistakes can have huge consequences Yes, that's why we are not discussing the creation of easily typed aliases for "rm -rf". That would be bad. Instead we are discussing aliases for a bunch of fairly innocent Git commands, most of which are reversible in case of catastrophic accident. I admit that I do have a four-character abbreviation for "git reset --hard". Maybe that will burn me one day, though I rarely pile up so many uncommitted changes that I have much at risk. Or maybe I'll make that shortcut a little longer.
- nevinera 15y agoIt won't burn you, the commits are still around until you get garbage collected.
- feralmoan 15y agoI don't understand why these examples even need to be optimised, just keep a pinkie finger hovered over tab and leverage bash's autocomplete :|