• Zorg@lemmings.world
    link
    fedilink
    arrow-up
    14
    ·
    2 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!

    • Xanis@lemmy.world
      link
      fedilink
      arrow-up
      6
      ·
      2 months ago

      The benefit of automating is really measured in hair loss and extra time to grab another coffee.

    • ryathal@sh.itjust.works
      link
      fedilink
      arrow-up
      1
      ·
      2 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
        ·
        2 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
          2 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.