Personal Finance
Yesterday
589
Biden wants to raise capital gains tax to 40%
Tech Industry
2d
7954
What happens when most of your team is Indian?
World Conflicts
Yesterday
561
Why I Find Free Palestine Inspiring
2024 Presidential Election
Yesterday
195
Canceling debt isn’t inflationary or costing tax payers
World Conflicts
3h
220
Peaceful Protest Hasn’t Worked and Has Been Met With Aggression.
It isn’t totally obsolete and will never be but I think the high paying test jobs are of the past.
I wouldn’t say obsolete. For enterprise software they are an asset that increase velocity. Are they necessary? Absolutely not.
take one side bro
Just because all qa can be laid off tomorrow doesn’t mean they are “obsolete”
Manual QA is obsolete. And as someone else said it’s pretty much obsolete for New as well in non-mission-critical environments.
It’s not obsolete, but it’s evolved into being mostly automated. Good DevOps practices should implement it into the pipeline now
SOMEONE is going to do testing. Either employees will do it or customers will do it. the big question is: is it cheaper to hire QA or cheaper to replace customers?
Yup. All our qa is gone, for the most part, and dev has taken on the roll. The bugs are wild and everywhere. We also started scuttling releases for basic shit that would have been caught early. But, profit. 🤷
You can just read the blog - "Getting Rid of you QA team was bad actually" - https://davidkcaudill.medium.com/maybe-getting-rid-of-your-qa-team-was-bad-actually-52c408bd048b TLDR; - Some MBA decided to fire all QAs and put that into SWEs. SWE just automates the QA testing and call it done.
Which means you have a bunch of people you label "SWE" doing exactly the same stuff that the people previously labelled "QA" were doing. So sure, QA is "obsolete" if you just change people's job titles! Brilliant!
lol
For New, yes it is
What does “New” mean? I’m probably missing some kind of inside joke here.
His company name