No More QA: Yahoo's Tech Leaders Say Engineers Are Better Off Coding With No Net (ieee.org)
Tekla Perry writes: A year ago Yahoo eliminated its test and quality assurance team, as part of project Warp Drive, its move to continuous delivery of code. The shift wasn't easy, Yahoo tech execs say, and required some "tough parenting." But the result has been fewer errors because "when you have humans everywhere, checking this, checking that, they add so much human error into the chain that, when you take them out, even if you fail sometimes, overall you are doing better." And the pain wasn't as great as expected. Yahoo's chief architect and SVP of science and technology discuss the transition.
I can give a counter-idea: in my first job, I didn't have QA. It was up to me to make sure my own code was quality enough before releasing it, and that aspect terrified me enough that I did learn to write quality code (which basically means you are testing your own code thoroughly, doing your own QA).
Now, at the time I was working with programmers who were much more skilled than I was, and I learned from them. Yahoo is a much larger company, with a programmers of a more varied skill-set. It is not rational to just assume what happened at my first company would happen at Yahoo, but it did work for me.
"First they came for the slanderers and i said nothing."