I spent a number of years doing QA ("real" QA, guiding and advising the entire lifecycle) and making sure that the software in my little corner of the world did

I spent a number of years doing QA ("real" QA, guiding and advising the entire lifecycle) and making sure that the software in my little corner of the world did work. (Often catching critical bugs after some other "QA" process had entirely missed them.) It's a thankless job. The developers I worked with directly loved me -- the best of the lot did, anyway. (My observation in turn of their abilities and professionalism.) But management had no clue (and refused to get one). And many developers outside of my exclusive little clique had to be brow-beaten into some level of compliance. Speaking generally: You say you want quality. But your actions belie this. P.S. If you're concerned about "quality", amongst other things you should read "Zen and the Art of Motorcycle Maintenance". To understand the importance of and drive for quality amongst those who really care.