• 0 Posts
  • 120 Comments
Joined 1 year ago
cake
Cake day: July 10th, 2023

help-circle



  • My first breaking point was the millionth time I was in the printer aisle before open on a Saturday with a manager laying into me for a half hour about how to “squeeze the last of the juice” out of people, and they dropped the “tell them you are an un-comissioned salesperson so you have no reason to take advantage of them, it disarms them, makes them trust you, you can load anything into their cart after you make them believe that” and I had a moment of clarity, and instead of going “Uh huh. Yes sir” I thought “No. I am an un-comissioned salesperson so I have no reason to take advantage of them. End of sentence.”

    Genuinely, Best Buy is one of the worst companies on planet earth.


  • Yup.

    I was 17, I was about to graduate high school so it was part time. I was the most reliable department associate, but one of the “weaker” salesmen.

    The department was spotless when I was there and the phone always got answered, and I made sure to bag 3 or 4 big sales a week, but I wasn’t out to bleed every poor soul who walked into the department dry. I was more about good service and finding the right solution for each person.

    So I got an average of 32 hours a week, well over all the other people in the department, but I was definitely on my way out, and that raging hemorrhoid of a waste of air reaming me out over helping an 80 year old woman who literally showed me her social security check, but assured me she had friends she could get to invite her over for dinner if the computer was too expensive pushed me out.

    Its not even like if they fired me I would have gotten unemployment. It was just a petty move from a coward with a micro-peen who couldn’t handle a 17 year old telling them they were a 45 year old failure at life working in a Best Buy for just over minimum wage taking advantage of nice elderly ladies.


  • Yup.

    I was in the computer sales department.

    We were flat out told what the lies were, and how to make them more convincing.

    The service contracts were non-refundable, so it didn’t matter.

    When a manager caught me helping a retiree get a cheap setup to email her grandkids instead of getting them on a line of credit for a top of the line gaming pc, they didn’t even fire me. They just stopped scheduling me hours and told me to keep coming in to get my schedule.

    Picked up a blank schedule for 5 weeks before I stopped going in and I’m sure they filed no call no show paperwork when I didn’t show up for my 1 hour 3 weeks later.

    Fuck best buy.


  • Ya.

    I worked there when they launched a membership thing, and it was points to gift cards that got printed on receipt paper in hopes the barcode on the carbon paper would fade before you tried to scan it, not any actual price reduction.

    Kind of like how there was all that fine print in the 200 dollar service plan that made it sound like you got more, but it was always just the manufacturer warantee, so if your device qualified for manufacturer warentee, geek squad would give you the cheap out fix, and get the preemo replacements and put them into stock. If the manufacturer warantee didn’t cover it, you were fucked.


  • Melkath@kbin.socialtoProgrammer Humor@lemmy.mlCheckmate
    link
    fedilink
    arrow-up
    35
    arrow-down
    2
    ·
    6 months ago

    The real joke was the pain that every developer feels when the end user gives such useful and actionable feed back as “It broke. Fix. Unga bunga.”

    “It works on my machine” is trying to be polite when, after hours and hours of trying to teach a person how to report a bug with necessary information, all they ever get is “It broke. Fix. Unga bunga.”










  • Melkath@kbin.socialtoProgrammer Humor@lemmy.mlUsers
    link
    fedilink
    arrow-up
    2
    arrow-down
    2
    ·
    edit-2
    6 months ago

    Thank you for your TED talk defining enshitification.

    Middle management bloat.

    Edit: Bonus points for

    Developers knowing how to write secure code helps, so they should theoretically also be capable of QA themselves to a degree.

    Which is straight up just saying “why don’t the devs just do it themselves? I’m busy with meetings to whine back and forth with other middle management.”


  • Melkath@kbin.socialtoProgrammer Humor@lemmy.mlUsers
    link
    fedilink
    arrow-up
    2
    arrow-down
    2
    ·
    6 months ago

    That’s a fair point.

    When I departed QA myself, it was in the onset of automation.

    In return, when the QA jobs disappeared, I learned basic scripting and started automating BI processes.

    So, I would say:

    1. I should hope modern QA departments (as I am told they exist) are automated and share both their tests and their results with devs in an efficient manner.

    2. I don’t think QA departments really exist today in a substantive way, and if they do, it isnt in as cooperative of a fashion as described in 1.

    I still have observed a world where QA went bye bye. Planning? Drafting a Scope of Work? Doing a proper analysis of the solution you are seeking, fleshing it out, and setting a comprehensive list of firm requirements that define delivery of said solution? Offering the resources to test the deliverable against the well documented and established requirements to give the all clear before the solution is delivered?

    Doesn’t exist anymore, and modern “QA” is being the lemming who sits in meetings as listens to the management, then schedules meetings to sit and complain at the Dev about how they aren’t “hitting the mark” (Because it was about 4 feet directly in front of them when they published, and is now at 5 erratically placed spaces behind them).


  • Melkath@kbin.socialtoProgrammer Humor@lemmy.mlUsers
    link
    fedilink
    arrow-up
    2
    arrow-down
    2
    ·
    edit-2
    6 months ago

    I guess I’m just being a snob here.

    I worked for an actual QA department that produced actual documentation and ran actual full scale QA cycles.

    In the past 15 years, I have seen that practice all but fully disappear and be replaced by people who click at things until they find 1 thing, have a verbal meeting vaguely describing it, and repeat 2 to 3 times a day.

    IMO, that isn’t QA. It’s being lazy, illiterate, and whiny while making the dev do ALL of the actual work.