The retailer says the change will create consistency in starting hourly pay across individual stores.

The retailer says the change will create consistency in starting hourly pay across individual stores.

  • @GregoryTheGreat
    9•10 months ago

    Bugs are cheaper to just deal with as they pop up….until they aren’t.

    • @[email protected]
      5•10 months ago

      I’ve seen this happen too. It’s sort of a double edged sword - devs need to take testing seriously and have coverage metrics. However, this doesn’t negate the need for QA particularly in software that has a human experience associated with it. Writing code and having it work correctly doesn’t mean that the user experience itself will be correct. For whatever reason, executives don’t understand this and software gets shipped with more bugs than ever because there’s little to no QA.

      • @[email protected]
        1•10 months ago

        Yeah. We wrote unit tests and integration tests, but we needed ui tests, which none of us were strong in at the time. One bug I remember fondly, it was possible to abuse debounce basically to submit bad info by switching an input after hitting submit. This happened more than you would expect. Took us forever to figure it out till we were able to get a UI tester from another team to figure it out. The human element is super useful in testing

    • @[email protected]
      4•10 months ago

      Not for my old app that had to be audited 6 times a year lol. Any data defect had to be explained in a one page summary. Now imagine you regularly have ~30k concurrent users. The wrong bug means tons of paperwork that brings us all out of development mode to write and support.