I agree in principle for most products, no QA, no testing. Why? * Everyone should do QA and implement their features own UI/UX, by following the pattern the ap

I agree in principle for most products, no QA, no testing. Why? * Everyone should do QA and implement their features own UI/UX, by following the pattern the application and framework sets tuned by an actual designer * An environment where production issues and bugs are prioritized above everything else should be created and fostered * To paraphrase Rich Hickey's analogy on the matter: writing tests is like driving around relying on the guard rails to keep you in the lines. That is (my interpretation): * If your code is this fragile to constantly require testing you've chosen poor abstractions.