“Consistent starting pay results in consistent staffing and better customer service while also creating new opportunities for associates to gain new skills from experience across the store and lay the groundwork for their career regardless of where they start,”
Ok miss PR person. Please explain your rationale cause that shit makes no sense.
I worked somewhere that was killing off their QA department and in a company wide meeting explained it by saying
“when you go to a store a pick up a part, you expect it to have gone through QA”
Lots of head scratching that day.
They still don’t QA their products. They just ship them and let the customers complain if something is wrong.
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.
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
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.
Reminds me when we had three companies merging at the same time and the bosses brought everyone in to tell the grunts and sales people that no one will be losing jobs. I ask, “You know when you move in with someone and you have to get rid of a set of dishes. Do you think you need three sets of dishes?” Yeah, so there were tons of lay offs.
Why even lie about it. Anyone smart enough to be worth something at the company is also smart enough to know better. You’ll lose everyone you can’t afford to lose.
probably went something like this: someone at a low paying store complained about the store 4 miles down the road paying more. so they’re addressing that ‘issue’.
“Consistent starting pay results in consistent staffing and better customer service while also creating new opportunities for associates to gain new skills from experience across the store and lay the groundwork for their career regardless of where they start,”
Ok miss PR person. Please explain your rationale cause that shit makes no sense.
I worked somewhere that was killing off their QA department and in a company wide meeting explained it by saying “when you go to a store a pick up a part, you expect it to have gone through QA” Lots of head scratching that day. They still don’t QA their products. They just ship them and let the customers complain if something is wrong.
I work in software dev. My old job laid off our entire QA team at once and presented it as an opportunity to learn doing testing as a developer.
twice the work, half the pay per job. woohoo!
Exactly. So glad I left there.
Bugs are cheaper to just deal with as they pop up….until they aren’t.
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.
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
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.
Reminds me when we had three companies merging at the same time and the bosses brought everyone in to tell the grunts and sales people that no one will be losing jobs. I ask, “You know when you move in with someone and you have to get rid of a set of dishes. Do you think you need three sets of dishes?” Yeah, so there were tons of lay offs.
Why even lie about it. Anyone smart enough to be worth something at the company is also smart enough to know better. You’ll lose everyone you can’t afford to lose.
probably went something like this: someone at a low paying store complained about the store 4 miles down the road paying more. so they’re addressing that ‘issue’.