• katy ✨@lemmy.blahaj.zone
    link
    fedilink
    arrow-up
    89
    arrow-down
    3
    ·
    7 months ago

    i remember writing .bat files and pretending they were really fancy update scripts when i was like ten they did nothing but it was still fun :)

    • Ms. ArmoredThirteen@lemmy.ml
      link
      fedilink
      arrow-up
      59
      ·
      7 months ago

      Like half of my job is writing .bat files to automate stuff locally and not tell my boss that all I do anymore is double click the right things in the right order…

      • viking@infosec.pub
        link
        fedilink
        arrow-up
        25
        arrow-down
        1
        ·
        7 months ago

        You can put in a timeout command at the end, and then call the next .bat file.

        For example “TIMEOUT /T 60” waits for 60 seconds before resuming, or you can override it by pressing any key.

        So if you know how long the wait time between scripts is, just write a master.bat and call them in order, with adequate waiting time in between.

        • SpaceCadet@feddit.nl
          link
          fedilink
          arrow-up
          4
          ·
          7 months ago

          Or just use the @CALL command to call them in order without having to guesstimate how long they run.

        • Ms. ArmoredThirteen@lemmy.ml
          link
          fedilink
          arrow-up
          3
          ·
          7 months ago

          Okay so the dumb part is a lot of this is me abstracting away our complex build system. I’ve basically bubble-gummed a dedicated build system in top of it for only the tasks I do. At a certain point if I start adding configurations or timing I might as well just wrap it in gradle or something. But the system that I’m calling is already their attempt at simplifying another build system that’s underneath it that was written by the old guard using arcane sorcery. The whole thing is a mess

      • CatTrickery@lemmy.blahaj.zone
        link
        fedilink
        arrow-up
        11
        ·
        7 months ago

        I had a job like that and powershell was a godsend. I let it slip when I accidentally set the multiplier for the delay randomiser too low and it did a months work in a morning. I ended up writing a guide for the others there when I left but sadly everyone but me had computers that supported newer versions of Windows where the scripts ended up broken. They asked me to come back and update it the Monday after I left. I asked if they would pay me to do it. They said no. Then I said no.

        • Ms. ArmoredThirteen@lemmy.ml
          link
          fedilink
          arrow-up
          2
          ·
          7 months ago

          This is part of why I still have manual kickoffs for mine. Never need to worry about work getting done while I’m away or getting done suspiciously fast. Also they should have paid you lol, the dingdongs. Would cost a lot more just in work lost having someone else spend time deciphering and fixing it. They could always get someone else up to speed with the system after it is fixed by you so there’s little or no down time