Start all of your commands with a comma

I didn't like the idea. I prefer the alternative approach: _I_ decide the order of dirs in the PATH env. If I introduce an executable with a name, that overrides a system one - I probably do that intentionally. If I introduce an alias (like `grep='grep --binary-files=without-match --ignore-case --color=auto`) that matches the name of a system binary - I probably do that intentionally. And if I EVER need to call grep without my alias - I just prefix it with…

I do something a bit special... Instead of naming my script foobarnator (and hence risking that another foobarnator may exist in the future and may clash with my script), I name my script foobarnatorToBeAliased.sh. Then in my list of aliases I alias foobarnator to foobarnatorToBeAliased.sh. The alias itself looks a bit weird in that to pass arguments to an aliased command you need to use a function (in Bash at least AFACIT) but it all works fine. As aliases aren't…

When I read the headline I thought this was going to be a terrible idea but I quite like it, especially the bit about using tab to list all your tooling. Anecdotally I haven’t had many namespaces collisions recently. I’ve also let myself go a bit after going into management. My tech skills are 10 years too old. Any tips from someone else on where they started to be hip again?

This is clever given what we have, but it seems like the wrong solution to the problem. I already have a PATH order. What would be nice is if typing say `sc` gave me the first `sc` program, but typing `,sc` gave me the one after that. This would generalize, so if I were stuck with cough several pythons I could call them with `python`, `,python`, `,,python` and so forth. This would be a shell-level patch but surely not an…