Also related: bash_history is your best productivity tool;
https://martinheinz.dev/blog/110I have a weird story about that.
When I was a junior sysadmin I worked for a company providing a SaaS solution for e-commerce.
The environment I worked in was bare-metal (as was the style at the time), with a 2 tier network architecture, lots of internal tooling (mostly in Perl fwiw) and highly complex interactions between components (cache items recorded in MySQL, centralised job control through a pair of activeMQ servers that had a postgres proof of record etc).
During this time, I fancied myself the growing expert, and thus I created the most gnarly one-liners you could imagine. But they did everything. I annotated them with a “function parameter” comment at the end
$ if []; then x; fi ## FUNCTIONDOES: THING
then I would control+R constantly from the bastion host to do my daily work. I had managed to automate a huge amount of common requests this way.
The existing team was disgruntled and started leaving, eventually making me the most senior in the team.
Of course, I also left.
I kept good contact with the team that onboarded as I was leaving, and one day while drinking I was told (off-handedly but in no uncertain terms) that I was the author of “the bash_history”.
After enquiring to what they meant, they indicated that after I resigned, someone found my bash_history file (because I had been onboarding them and they had seen my workflow) and it had been immortalised by:
A) Being copied to everyones profile and placed in /etc/skel
B) being chattr +i (immutable)
I was honoured. and horrified.
I have a weird story about that.
When I was a junior sysadmin I worked for a company providing a SaaS solution for e-commerce.
The environment I worked in was bare-metal (as was the style at the time), with a 2 tier network architecture, lots of internal tooling (mostly in Perl fwiw) and highly complex interactions between components (cache items recorded in MySQL, centralised job control through a pair of activeMQ servers that had a postgres proof of record etc).
During this time, I fancied myself the growing expert, and thus I created the most gnarly one-liners you could imagine. But they did everything. I annotated them with a “function parameter” comment at the end
then I would control+R constantly from the bastion host to do my daily work. I had managed to automate a huge amount of common requests this way.The existing team was disgruntled and started leaving, eventually making me the most senior in the team.
Of course, I also left.
I kept good contact with the team that onboarded as I was leaving, and one day while drinking I was told (off-handedly but in no uncertain terms) that I was the author of “the bash_history”.
After enquiring to what they meant, they indicated that after I resigned, someone found my bash_history file (because I had been onboarding them and they had seen my workflow) and it had been immortalised by:
A) Being copied to everyones profile and placed in /etc/skel
B) being chattr +i (immutable)
I was honoured. and horrified.