Making the shell history more useful by using shell variables (danielrotter.at) en
The shell history is cluttered with useless commands if stuff like tokens are included. Shell variables allow to exclude such content from the history.
The shell history is cluttered with useless commands if stuff like tokens are included. Shell variables allow to exclude such content from the history.
Sometimes you want a command to be automatically executed as soon as a certain file changes. There is a small tool called entr, which helps with that.
Creating objects is a very basic task. Although this seems like a simple problem, it can be improved by using patterns like builder and factory.
Quite often I want to execute the same command for multiple files. It is quite easy to achieve that using the fish shell, once you get the hang of it.
I was refactoring a feature and wanted to know which options were used for a certain attribute in a XML file. I decided to level up my CLI skills for that.