- Joined
- Jul 15, 2023
- Messages
- 981
What are you basing this opinion on? A few quick searches on LinkedIn results in thousands of open QA positions.Software QA is largely a thing of the past. Now it's a rush to release to meet sales/marketing deadlines, and have users do the final testing, even for "stable" releases and not just "public betas," which have contributed to the lowering of standards, and expectations (thanks, Google!).
The problem is poor release planning, rigid methodologies that adhere to near-religious levels of procedural dogma, developers who cut corners, and management that fails to set priorities and that over scopes. Deadlines are not inherently a problem, they just appear that way when poorly executing teams fumble across them.
Generally if this happens it’s due to at least one of four reasons:As a user, one can try to file bug reports, but to see them dismissed, or ignored in the tracker doesn't encourage keeping up the effort for all but the most dedicated (or annoyed with a particular bug).
1. No reproducible workflow
2. Specific to that user and not others
3. Impossible to safely fix
4. Other more important bugs are prioritized higher
Woah, how did you get this impression? There are thousands of new pieces of software coming out constantly.Most software is mature, so a lot of new features aren't essential, making security the biggest reason to update (outside of a manfuacturer's push for new revenue generation though mandatory updates). Many users don't, but the risk/reward ratio still usually works in their favor, as long as aren't part of a targeted group, or engage in riskier behavior.