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.”
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:
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.
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).
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.
A devout Kool aid drinker I see.
Did you buy that Kool aid with your story points?
I hear they have a competitive exchange rate to Stanley nickels.
Which, when put to practice, means QAs become BAs, no comprehensive QA occurs, and when the code is shit because they have no actual QA support and the scope changes constantly with no firm documented requirements, the dev gets fired.
Great model for people who like to sit in meetings and complain.
Horrible model for the people who actually work.
Still working.
I stopped being able to find QA work in the early 2010s or so. Converted to BI Developer. Have not encountered a dedicated QA at any of the small assortment of jobs I have had since.
Edit: And fair, despite it being a waste of time cult mentality engineered to make developers suffer and enshitify software quality, Agile got enough Kool aid drinkers to qualify it as more than a fad.
Yes grasshopper.
I was a QA for over 15 years.
Then the “Agile” fad ripped through the industry and QA died.
A) People still get paid to do dedicated QA?
B) If you really think that, you must be a noob.
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.”