I’ve worked with some pretty rotten software, but management software is easily the most user unfriendly, so my vote goes to HPSM.

    • AMDIsOurLord@lemmy.ml
      0·
      8 months ago

      National Instruments

      Ah I see, a fellow tortured soul who had to endure MultiSim I presume?

      For people who’re not in the loop, if you haven’t used MultiSim you categorically do not know what UX nightmares are made of

    • bitwolf@lemmy.one
      0·
      8 months ago

      Is JIRA better or worse than Azure DevOps?

      We’re being moved over to JIRA and I’m worried because I hear so much shit about Atlassian

      • DeltaWhy@lemmy.worldEnglish
        0·
        8 months ago

        One of the big problems with JIRA is it’s extremely configurable, so your experience depends entirely on how your admins have set it up. If your company is the type to micromanage, JIRA gives them a lot of tools to do that, which I think is why it gets so much hate from devs. I find it tolerable in my current job but it’s definitely designed for managers and not for developers.

        • jj4211@lemmy.world
          0·
          8 months ago

          Jira gets double whammy:

          • If you use it, it’s cool, you can call yourself ‘Agile’ and tell anyone who accuses you otherwise so.
          • You can still apply all the draconian process and difficulty you love from not being Agile
        • commandar@lemmy.world
          0·
          8 months ago

          This is basically every major enterprise ticketing system. They’re typically extremely customizable over-featured behemoths so that they can check all the buzzword boxes for the people that make purchasing decisions but will never actually use the system.

          "It’s a fully integrated Agile ITIL DevOps CMDB that empowers your users while providing generative KPIs to guide business decisions!”

          Then, on top of that, ownership of it is generally dropped on a team that is completely incapable of properly managing it from both a technical ability and sheer manpower availability standpoint. So each install ends up becoming an overly complex, confusing, terribly performing mess.

          I think I’ve seen one reasonably well managed install in the couple decades I’ve been doing this, a couple of more that were mildly jank but usable, and then everything else has been a pit of despair largely driven by the above.

      • toddestan@lemmy.world
        0·
        8 months ago

        We actually moved from JIRA to Azure DevOps. Part of it was that Atlassian dropped the server version of JIRA and we weren’t too keen on moving to the crappier cloud version.

        I’d say it’s different. Some things JIRA does better, some things Azure DevOps does better. You eliminate some pain points, and end up with some new ones.

      • Potatos_are_not_friends@lemmy.world
        0·
        8 months ago

        Honestly I never had a problem with JIRA.

        Over all the project management tools I’ve used in my decade of work, Atlassian’s suite was the most organized for my needs.

        The most annoying part is reporting, which I hear a lot of complaints about. But that’s not my job, and the reports I need are easy to export the data and build a custom UI to organize it.

    • Muun@lemmy.worldEnglish
      0·
      8 months ago

      You mean Emerson now! :P

      I’m a CLA who spent 9 years developing LabVIEW applications for control systems. NI always annoyed me with their terrible decision-making and inability to catch up with modern times in the software world. (Their merge tool is so bad, it’s next to impossible to have a multi-developer project)