4 ms·
Great. I worked for a company that didn't invest in QA, it was consistently a !@#$% mess. When you do this, the need simply shifts to the customer. I wouldn'
by mixmastamyk 11y ago
Great. I worked for a company that didn't invest in QA, it was consistently a !@#$% mess. When you do this, the need simply shifts to the customer. I wouldn't install our software until the 4th or 5th hotfix patch was available.
Certainly, I'm an advocate of a more responsible dev team sharing the quality tasks and continuous integration too. But no QA at all? Hahah... maybe if you're a web portal that no one depends on for business-critical needs.
Edit: I guess the truth hurts.
- vox_mollis 11y agoI worked for a company that didn't invest in QA Where are these magical places that do invest in QA? In nearly 20 years of professional development, I've never seen an organization in which the criteria for shipping was anything other than "works for me". I have never seen an organization in which there was either budget or managerial patience for proper QA, let alone anything other than VERY basic acceptance testing.
- hofmann 11y agoI once worked in an organization that has 1.5-2x QA then dev. I now work in a place which has 1 QA for every 8 devs -- and there are far less bugs here then the other. I think the reason is proper tooling, a culture of thorough automated testing, and ownership of code.
- mixmastamyk 11y agoOwnership and the resulting pride in workmanship makes a big difference.
- mixmastamyk 11y agoPlaces where it is important that the software works. I once worked on an enterprise product that had a QA team of 25 people.
- solomone 11y agoWhen I worked at Microsoft many years ago they had an large QA team with equal footing to Development and Product in determining what shipped and when. This was the same for every development team I was a part of there for over 9 years. It wasn't perfect, and the ship cycles were slow, but the quality bar was set higher than what I've seen outside of Microsoft.
- wehadfun 11y agohttp://www.themarysue.com/ibm-black-team/ http://www.themarysue.com/ibm-black-team/
- clock_tower 11y agoHealthcare. Many companies developing medical software require two layers of QA (programmer review and QA; then a separate QA team) before release. "Works for me" is not appropriate when the "me" in question is not a subject-matter expert, and the subject matter is potentially deadly.
- deleted 11y ago[deleted]