News for hackers. Stuff that matters.
Re:Yahoo’s Engineers Move to Coding Without a QA Team by mixmastamyk on Friday December 11, 2015 @03:37PM (#10719801)
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.

Re:Yahoo’s Engineers Move to Coding Without a QA Team by vox_mollis on Friday December 11, 2015 @03:49PM (#10719897)
I 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.

Re:Yahoo’s Engineers Move to Coding Without a QA Team by hofmann on Friday December 11, 2015 @06:02PM (#10720753)
I 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.

Re:Yahoo’s Engineers Move to Coding Without a QA Team by mixmastamyk on Saturday December 12, 2015 @12:19AM (#10721881)
Ownership and the resulting pride in workmanship makes a big difference.
Re:Yahoo’s Engineers Move to Coding Without a QA Team by wehadfun on Friday December 11, 2015 @05:17PM (#10720503)
Re:Yahoo’s Engineers Move to Coding Without a QA Team by solomone on Friday December 11, 2015 @04:53PM (#10720358)
When 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.
Re:Yahoo’s Engineers Move to Coding Without a QA Team by clock_tower on Friday December 11, 2015 @06:28PM (#10720888)
Healthcare. 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.
Re:Yahoo’s Engineers Move to Coding Without a QA Team by mixmastamyk on Friday December 11, 2015 @04:44PM (#10720276)
Places where it is important that the software works.

I once worked on an enterprise product that had a QA team of 25 people.