Path: csiph.com!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail From: rbowman Newsgroups: comp.os.linux.misc Subject: Re: Crowdstrike fiasco Date: 20 Jul 2024 18:42:21 GMT Lines: 11 Message-ID: References: <14650d94-4742-6c3f-9c73-33e7468106c5@example.net> <3HSmO.57759$xYQc.40648@fx12.iad> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Trace: individual.net e7OsbJrQXo5Ub6/povPWGQXfnmz+U6pPocHzmK+2c4gi6lcYFe Cancel-Lock: sha1:9kSEctOU5iuJ9Z2QaA8+FC2+KCs= sha256:CuR0CzhoTuoyBdzZcWbRzRIJIwS32XsUrikXf3icdjk= User-Agent: Pan/0.149 (Bellevue; 4c157ba) Xref: csiph.com comp.os.linux.misc:57068 On Sat, 20 Jul 2024 17:43:27 GMT, Charlie Gibbs wrote: > That explains the definition of "Quality Control" that I once heard: > keeping quality under control so it doesn't rise too high and increase > costs. Stated honestly a large part of my college statistics course involved determining how many widgets you need to test to insure only N% of the output is defective, where N is determined by the cost of repairing/ replacing the defective widgets balanced against the QA costs.