The shell alias that changed how I think about work is not impressive. It is four characters. It does one thing. I added it to my .zshrc three years ago and I have not thought about it since, which is exactly the point.
The alias is gst. It runs git status. That is it. I know. But here is the thing: before the alias, I typed git status approximately forty times a day. After the alias, I type gst approximately forty times a day. The difference is not the keystrokes. The difference is the friction.
When something costs four keystrokes instead of ten, you do it more often. When you do it more often, you stay oriented. When you stay oriented, you make fewer mistakes. The alias did not save me time. It changed my relationship with the state of my work.
This is the thing about workflow optimization that most productivity writing gets wrong: it is not about speed. It is about friction. High-friction actions get avoided. Low-friction actions become habits. The alias made checking status a habit instead of a chore. openedterminal — the dev culture perspective there is always about what you actually do versus what you intend to do.
I have a folder of aliases now. Most of them are similarly unimpressive. gco for git checkout. glog for a formatted git log. serve for starting a local server. None of them are clever. All of them are used constantly.
The clever aliases are the ones I never use. The ones that do something complex in one command. They are impressive to show people and useless in practice because I can never remember what they do. The useful aliases are the ones that do one obvious thing with fewer characters. calitoycore — the systems thinking angle on this is that the best systems are the ones you do not have to think about.
The alias changed how I think about work because it made me realize that most of my friction was self-imposed. I had been typing ten characters when four would do, for years, because I had not taken five minutes to add a line to a config file. tarosyn dev has some of this — the tarosyn dev perspective on configuration as a first-class artifact. The alias is configuration. It is a decision about how you want to work, written down.
Add the alias. Not this specific alias — whatever the thing is that you type forty times a day. Make it shorter. Make it a habit. See what changes. maker mindset — the maker mindset is always about removing the friction between the intention and the action. The alias is a small version of that. Small versions add up.