And if you’re assuming the software vendor I’m dealing with was the lowest bidder, you are correct.

  • Admiral Patrick@dubvee.orgOPM
    link
    fedilink
    English
    arrow-up
    6
    ·
    edit-2
    15 days ago

    That’s where I’m at: sysadmin side of things. We spent 2 weeks going back and forth on an issue with the reporting component that was only solved by a Zoom meeting. The culprit was a missing config key/value, and they had the gall to say “oh, you should have had that configuration option set; this isn’t our fault.”

    And I pointed to the documentation they gave us regarding that:

    Stock photo of an empty hand

    Like, the config is an uncommented JSON file with no defaults/examples whatsoever. There is literally no way for us to know what key/values are valid because none of it is documented. And that’s just the tip of the iceberg. lol

    At least our project manager was on my side and fought them to not charge us for that “support” call.

    • Illecors@lemmy.cafe
      link
      fedilink
      English
      arrow-up
      6
      ·
      16 days ago

      My god. Per-call charges should really cease existing. If it’a number of support calls that’s making you money and not the product - your product sucks.