Automation be like - eviltoast
  • 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.