evil_aaronm writes "I work for a large international company producing systems for health care, specifically medical diagnostics. This is a product upon which lives depend: our systems can cause great joy when people learn that they do not have "dreaded disease", or death, if our results are incorrect and treatment is delayed. I greatly enjoy working on this product, but I can't stand my manager: our definitions of "quality" are vastly different. The code we produce could supply more than a year's worth of Daily WTF fodder. Every time I try to improve our code, I'm shot down because this manager can't handle abstract concepts, among other things. An example, with no embellishing, and one of many: instead of writing a loop to process, say, 10 files the exact same way, he wants to cut-and-paste 10 blocks with the name of the file changed in each block. My equivalent loop was rejected: too complex. Partly because of this, after two-plus years, I'm changing departments and will no longer have to work with him, for which I'm grateful. My question is: How do I — or do I at all — warn management or, more importantly to me, our customers, that this product is a festering pile of shit that's waiting for the smallest provocation to cause said shit to spew all over? I almost believe upper management doesn't want to know: Head in Sand syndrome. That doesn't mitigate my responsibility to make it known to -someone- that this product is a large defect waiting to happen. Changing groups also doesn't relieve my sense of concern that someone could very well die because I did nothing to fix this."