Ask Lemmy
A Fediverse community for open-ended, thought provoking questions
Please don't post about US Politics. If you need to do this, try [email protected]
Rules: (interactive)
1) Be nice and; have fun
Doxxing, trolling, sealioning, racism, and toxicity are not welcomed in AskLemmy. Remember what your mother said: if you can't say something nice, don't say anything at all. In addition, the site-wide Lemmy.world terms of service also apply here. Please familiarize yourself with them
2) All posts must end with a '?'
This is sort of like Jeopardy. Please phrase all post titles in the form of a proper question ending with ?
3) No spam
Please do not flood the community with nonsense. Actual suspected spammers will be banned on site. No astroturfing.
4) NSFW is okay, within reason
Just remember to tag posts with either a content warning or a [NSFW] tag. Overtly sexual posts are not allowed, please direct them to either [email protected] or [email protected].
NSFW comments should be restricted to posts tagged [NSFW].
5) This is not a support community.
It is not a place for 'how do I?', type questions.
If you have any questions regarding the site itself or would like to report a community, please direct them to Lemmy.world Support or email [email protected]. For other questions check our partnered communities list, or use the search function.
Reminder: The terms of service apply here too.
Partnered Communities:
Logo design credit goes to: tubbadu
view the rest of the comments
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.
I had a coworker who is actually quite competent and intelligent. We're still really good friends. But I think he only less than 10 keystrokes in vi: up, down, left, right arrows. x (delete char), i (insert mode) and whatever key sequence he used to save and exit. I use :wq! but he may be a ZZ type of person.
history | grep and ! would blow his mind.
CTRL + r is even better
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.
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.
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.
Employer doesn’t know what he does, he does less work in the same amount of time.
Wow.
Maybe you can show him
history > out.txtand blow his mind?This one here is for your co-worker only! Not for you, not for anyone else, just for him:
https://github.com/atuinsh/atuin
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.
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.
I saw someone, instead of opening a folder in VS Code, have a separate Explorer window that they'd navigate through and then right click --> Open in VS Code whichever file they wanted to edit