• @[email protected]
    link
    fedilink
    121 year ago

    My kid got a job at some place and was browsing through an update script for a customer. There were a bunch of random-seeming sleep and printf statements. He couldn’t make sense of it, so asked one of the more senior techs what was the deal. It was as you said. They had updated software/hardware at a customer’s site and the backups were going so quick that the customer was getting pissed because “There is NO way this is doing in 10 seconds what should take several minutes.” OK, the customer gets what they want. A judicious sprinkling of delays and meaningless messages. The 10 second update now takes a little over 4 minutes and the customer was happy again.

    • @derpo
      link
      51 year ago

      Oops we fixed it

    • kamen
      link
      English
      21 year ago

      the customer was getting pissed because “There is NO way this is doing in 10 seconds what should take several minutes.”

      Shouldn’t they have access to the backup location as well so that they can verify that it’s fine?

      • @[email protected]
        link
        fedilink
        English
        11 year ago

        They the customer? I think you’re overly optimistic about people. They the company my kid works for? Yeah, they have remote access to everything.

      • KairuByte
        link
        English
        1
        edit-2
        1 year ago

        While the customer may have access, you’re all but guaranteed they aren’t ever going to verify it. Most backups aren’t meant to be verified on external systems, and testing the backup would generally require actually restoring it somewhere.

        That said, some systems do have external tools to verify backups, but it’s not universal.

      • @IDatedSuccubi
        link
        English
        11 year ago

        Forcing the client to manually verify the integrity of backups each time is a bad user experiemce

        I know it sounds weird, but they would probably do it every time