• JCreazy@midwest.social
    link
    fedilink
    English
    arrow-up
    48
    ·
    6 months ago

    It seems like I’m constantly finding bugs in businesses’ apps. Do they not have people test them?

    • jol@discuss.tchncs.de
      link
      fedilink
      arrow-up
      64
      arrow-down
      1
      ·
      6 months ago

      They do, and they have a backlog of hundreds of issues to fix and they must prioritise then. If fixing a bug doesn’t make money, it’s not priority.

      • Lost_My_Mind@lemmy.world
        link
        fedilink
        arrow-up
        13
        ·
        6 months ago

        I hate how they’ll spend 4 years squashing all the bugs…and then they cancel the software, and release a new buggy version.

        • KillingTimeItself@lemmy.dbzer0.com
          link
          fedilink
          English
          arrow-up
          5
          ·
          6 months ago

          i will never forgive the emby team for creating the single most idiotic (although rather funny) transcoding system.

          It has a resolution selection, along with a bitrate selection, so you would think it forces transcoding.

          It turns out the resolution is actually just a suggestion, and the bitrate is what it targets, if it doesn’t meet the bitrate, it will transcode, and if you get lucky, it might transcode to the specified resolution.

      • bitchkat@lemmy.world
        link
        fedilink
        English
        arrow-up
        1
        ·
        6 months ago

        I am steadfast that I will occasionally take some time and kill off some low hanging fruit. For me, its kind of like a break and lets me clear my head on the bigger issues.

        • jol@discuss.tchncs.de
          link
          fedilink
          arrow-up
          2
          ·
          5 months ago

          Even then, there are bugs that need multiple people (design, engineering, content, QA, etc) and are not something that can be fixed on a whim.

            • jol@discuss.tchncs.de
              link
              fedilink
              arrow-up
              1
              ·
              5 months ago

              The problem is that what users consider low hanging fruit is often not, and what is low hanging fruit for devs, is invisible stuff that users don’t notice. The intersection is the tastiest low hanging fruit, but as such it’s also rare and easily picked by anyone.

              • bitchkat@lemmy.world
                link
                fedilink
                English
                arrow-up
                1
                ·
                5 months ago

                I never said that users were involved in this. This is just grabbing some bugs off the queue that are simple to fix but have been deprioritized by project manager.

                But they do make the customer happy because they are the one that submitted the bug.

    • vithigar@lemmy.ca
      link
      fedilink
      arrow-up
      36
      ·
      6 months ago

      As someone in the dev team for a “business app”, we probably know about most or all of them, but they’re just not important enough for anyone in management to prioritize them as part of a sprint. It’s also possible no one has given us reproducible steps to make them happen, so we just straight up don’t know what to fix. Usually the former though.

      • Socsa
        link
        fedilink
        arrow-up
        3
        ·
        6 months ago

        The struggle is real. “We could spend an entire sprint chasing down debt which impacts 10% of users, or we could add another feature which will generate 10% additional revenue.”

        Management will always choose number 2. Code maintenance is like dead money until something really breaks. The best you can do is quietly have engineers fix low hanging fruit as part of feature sprints, but that requires engineers who give enough fucks to do some extra work.

    • mrkite@programming.dev
      link
      fedilink
      arrow-up
      16
      ·
      6 months ago

      I would fix that bug but the complete rewrite that management has had me working on for the past two years will make it obsolete anyway.

    • Andrenikous@lemm.ee
      link
      fedilink
      English
      arrow-up
      4
      ·
      6 months ago

      Sometimes. Other times they layoff the QAs and anyone else whose job is about quality.

    • douglasg14b@lemmy.world
      link
      fedilink
      arrow-up
      2
      ·
      5 months ago

      They usually do yes however it’s all about prioritization.

      You may have hundreds or thousands or open requests and issues.

      With tens of thousands of closed issues that were either not reproducible, not actually problems, or largely indecipherable.

      There’s usually a feature roadmap which is where most of the development money and time is spent. If it’s an older business application then certain bugs might easily take weeks to find, fix, test, validate, go through user acceptance, A/B test, and then deploy. But fixing is expensive work, so if the bug isn’t severe it’s usually deprioritized next to higher priority work.