I work in software engineering/development. There’s a guy on my team who manually copy/pastes every Linux command he runs, into a fucking text file. He does this so he has a record of which commands he ran. As a result, he has a 12,000 line text file, full of garbage. With few exceptions, Linux stores every command you run, chronologically, with a configurable limit. He knows this, but insists on saving all of them to a Fucking. Text. File.
Watching him work makes me want to rip my eyeballs out.
With all the time you save by not copying your commands into a file for your reference, maybe you can invent a machine that will give your superior mental capacity to everyone else.
Hmm, I sometimes do this, when tackling a particular problem, along with some notes. It is often nonlinear and branching.
I use it to construct a problem-solving script in the end. And it’s markdown file.
I do the same, kind of but I paste them in word and format them nicely, based on my mood. Today I made a very nice initial of my npm publish command, it looks really nice.
I work in software engineering/development. There’s a guy on my team who manually copy/pastes every Linux command he runs, into a fucking text file. He does this so he has a record of which commands he ran. As a result, he has a 12,000 line text file, full of garbage. With few exceptions, Linux stores every command you run, chronologically, with a configurable limit. He knows this, but insists on saving all of them to a Fucking. Text. File.
Watching him work makes me want to rip my eyeballs out.
This one here is for your co-worker only! Not for you, not for anyone else, just for him:
https://github.com/atuinsh/atuin
With all the time you save by not copying your commands into a file for your reference, maybe you can invent a machine that will give your superior mental capacity to everyone else.
This was not meant to be a gloating post. I’m simply explaining someone’s terrible and infuriating workflow.
I’m slowly learning not to look into any of my coworkers’ workflows
Sometimes I get tasked to help him fix his problems. I usually just end up checking out his branch and fixing it myself.
Wow.
Maybe you can show him
history > out.txtand blow his mind?Good lord, you can even ctrl-r to search your command history so even searchability is not a reason to copy into a text file.
I’ve shown him reverse history search several times. But he just won’t use it.
This makes me want to rip my eyeballs just thinking about it. Jesus.
I’m imagining when they type, it is at a speed of approximately 100 words per week.
Yeah. He’s a pretty old guy and has the single-finger old man typing style.
history | grep <word> and ! would blow his mind.
CTRL + r is even better
Hmm, I sometimes do this, when tackling a particular problem, along with some notes. It is often nonlinear and branching. I use it to construct a problem-solving script in the end. And it’s markdown file.
Are we OK? ;)
Sounds like you’re taking a structured approach to problem solving. Not wasting time capturing information that’s already there.
We cool.
I do the same, kind of but I paste them in word and format them nicely, based on my mood. Today I made a very nice initial of my npm publish command, it looks really nice.
Employer doesn’t know what he does, he does less work in the same amount of time.