• Quik@infosec.pub
        link
        fedilink
        arrow-up
        19
        ·
        4 months ago

        Seems to have become one of the fundamental rules of the Internet now, I approve 👍

      • lobut@lemmy.ca
        link
        fedilink
        arrow-up
        10
        ·
        4 months ago

        There’s something really satisfying about running a script that you know would save time. Even if the overall time is probably a negative.

        I wrote a script that would log me into our AWS EKS stuff. I typically would have to copy these 7 lines and look up which cluster version I’d need. One of my lines just pulls all the clusters and I use fzf to select the cluster I wanted. Takes away all the pain and makes me feel smug. Love it.

    • UnderpantsWeevil@lemmy.world
      link
      fedilink
      English
      arrow-up
      11
      ·
      edit-2
      4 months ago

      It’s a two minute task, but it happens randomly between the hours of “romantic dinner with my wife” and “ten minutes after the baby finally went down for a nap”.

  • Boozilla@lemmy.world
    link
    fedilink
    English
    arrow-up
    64
    ·
    4 months ago

    Automation also cuts down on mistakes.

    Or greatly amplifies them if you coded it wrong.

    • Zorg@lemmings.world
      link
      fedilink
      arrow-up
      15
      ·
      4 months ago

      Doesn’t even have to be the case. A 2min task done every (work)day, takes up a bit over 7 hours/year. After 2½ years it will be a benefit to have automated it!

      • ryathal@sh.itjust.works
        link
        fedilink
        arrow-up
        1
        ·
        4 months ago

        Only if the requirements stay the same for 2.5 years. Otherwise there’s probably another week of time trying to update the initial work, then just throwing it away and making a new solution that’s theoretically easier to update.

        • Codex@lemmy.world
          link
          fedilink
          arrow-up
          3
          ·
          4 months ago

          If changing requirements mean you need to update the script, then updating the script is part of your job. QED. I don’t see the problem with a little job security.

          • ulterno@lemmy.kde.social
            link
            fedilink
            English
            arrow-up
            2
            ·
            edit-2
            4 months ago

            Yeah, just add it to the ‘amount of work you are putting’.

            When setting up git hooks for my project, I looked at other’s OSS hooks first. That shaved off significant hours off of my Research.

  • SuperRecording@lemmy.ml
    link
    fedilink
    arrow-up
    35
    ·
    4 months ago

    Yeah, and you build skills and reusable code base that’ll be useful for automating/ simplifying future tasks 😎

    Some years of this, you get to the point where you can solve damn near everything quickly and people think you’re some magical shit-wizard

    • Passerby6497@lemmy.world
      link
      fedilink
      English
      arrow-up
      6
      ·
      4 months ago

      you get to the point where you can solve damn near everything quickly and people think you’re some magical shit-wizard

      This is basically my work life, and its almost a problem because I’m the first guy people call when they need something done.

      The perils of being competent. /s

  • Etterra@lemmy.world
    link
    fedilink
    arrow-up
    31
    ·
    4 months ago

    And if it’s a task that will need to be done thousands of times a month or even year, you should thank them for it.

    • Lifter@discuss.tchncs.de
      link
      fedilink
      arrow-up
      2
      ·
      4 months ago

      With this as a guide, it would be enough if the task needed to be done twice per day to break even after five years.

      • mipadaitu@lemmy.world
        link
        fedilink
        English
        arrow-up
        5
        ·
        4 months ago

        That’s also only assuming that one person is doing that 2 minute task. If you automate a 2 minute task for 5 people, then it’s only 1 year.

  • ShortFuse@lemmy.world
    link
    fedilink
    arrow-up
    22
    ·
    4 months ago

    I can spend 2 minutes scanning a page for a certain word every time I need to search for something.

    But I’m very happy somebody spent the time to code Ctrl+F.

    • Hobo@lemmy.world
      link
      fedilink
      arrow-up
      11
      ·
      4 months ago

      Ctrl+f code has to be some of the most efficient automation ever written. Time spent was probably about day and the time saved in work hours is probably in the trillions at this point.

    • dch82@lemmy.zipOP
      link
      fedilink
      arrow-up
      4
      ·
      4 months ago

      Any shell is the duct tape of computers.

      The best engineers can do anything with duct tape.

  • ilinamorato@lemmy.world
    link
    fedilink
    arrow-up
    17
    ·
    4 months ago

    Yes, but since it runs automatically every day and emails my team the results, I don’t have to remember to do it on my own. I don’t even have to be working that day. Taking “my ADHD memory” out of the system is always a win.

    • ShareMySims@sh.itjust.works
      link
      fedilink
      English
      arrow-up
      2
      ·
      4 months ago

      Accessibility in general seems to be a huge benefit to automation a lot of people here including op are overlooking, which is a great shame but unfortunately not surprising…

  • Destide@feddit.uk
    link
    fedilink
    English
    arrow-up
    14
    ·
    4 months ago

    A two minute task done with 0 errors and once it’s done that 1440 times it’s a net positive

  • Codex@lemmy.world
    link
    fedilink
    arrow-up
    12
    ·
    4 months ago

    Programmers after slacking off for two days to improve their factories in Shapez2 because they already automated all their tasks.

  • SlopppyEngineer@lemmy.world
    link
    fedilink
    arrow-up
    11
    ·
    4 months ago

    Non automated tasks remain in the inbox for a week, so spending 2 days automating them means they’re finished earlier.

  • repungnant_canary@lemmy.world
    link
    fedilink
    arrow-up
    9
    ·
    4 months ago

    One more advantage is that you now have the full process well documented (via code) and if you realize some change is needed you can repeat the task quickly.

    • pedz@lemmy.ca
      link
      fedilink
      arrow-up
      1
      ·
      4 months ago

      I did that years ago to make backup reports and job monitoring on old servers with uncommon operating systems at work.

      Before my script, coworkers and I had to connect to more than a dozen servers and fill reports about the status of backups and the server. It took about 20 minutes if all went well. Now we just click a button and the report is filled automatically.

      It may just be 20 minutes a day, or maybe less if you were quick, but we’re still using it and it’s been nearly a decade. It saved a lot of minutes in the end. More time for naps.

  • EnderMB@lemmy.world
    link
    fedilink
    arrow-up
    3
    ·
    4 months ago

    Sometimes I’ve gone the other way. My manager complained once that I didn’t automate a task to get business metrics, and I responded to say that it currently takes me 1 minute to pull the metrics and paste them into a spreadsheet and print a PDF. Automating this would take at least several days, for a slide that changes constantly, and where the data often requires a deep dive into why the data is how it is. What’s the point in automating something that I already need to manually look at?

    They raised it with our PM, and their response was “fair, I wish I hadn’t bothered to automate things last year”.

    If the cost would give a higher benefit, sure, automate it so that it spits out a spreadsheet every week and do the manual stuff separately - but automating something “because you can” is junior level shit. My time is valuable, let me work on stuff that actually matters.