• @NegativeLookBehind
    link
    303 months ago

    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.

    • @daddy32
      link
      143 months ago

      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? ;)

      • @NegativeLookBehind
        link
        173 months ago

        Sounds like you’re taking a structured approach to problem solving. Not wasting time capturing information that’s already there.

        We cool.

    • @zeppo
      link
      English
      43 months ago

      history | grep <word> and ! would blow his mind.

    • @agent_flounder
      link
      English
      43 months ago

      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.

      • @NegativeLookBehind
        link
        33 months ago

        Yeah. He’s a pretty old guy and has the single-finger old man typing style.

    • TipRing
      link
      43 months ago

      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.

      • @NegativeLookBehind
        link
        43 months ago

        I’ve shown him reverse history search several times. But he just won’t use it.

    • @BigMikeInAustin
      link
      English
      23 months ago

      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.

      • @NegativeLookBehind
        link
        43 months ago

        This was not meant to be a gloating post. I’m simply explaining someone’s terrible and infuriating workflow.

        • @Feathercrown
          link
          English
          13 months ago

          I’m slowly learning not to look into any of my coworkers’ workflows

          • @NegativeLookBehind
            link
            33 months ago

            Sometimes I get tasked to help him fix his problems. I usually just end up checking out his branch and fixing it myself.

            • @Feathercrown
              link
              English
              13 months ago

              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

    • @Nahdahar
      link
      23 months ago

      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.

    • @bitchkat
      link
      13 months ago

      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.