I think defen&#x27;s point was that if a team produces truly high-quality C code, it&#x27;s similar to a couple that both abstain until marriage. Yes, it&#x27;s technically possible, but it&#x27;s rare, and it&#x27;s not something that should be the expected outcome (that is, most C code will have some problems, and most couples will have at least a little bit of regrettable sexual history before they&#x27;re married).<p>It&#x27;s as if I say: &quot;Step 1 of writing good code: Don&#x27;t make mistakes. If you make mistakes, you deserve what&#x27;s coming to you!&quot; Some mistakes are expected, and essentially inevitable; they&#x27;re the default, not the exception. Blaming the programmer might seem like the right thing to do, but there&#x27;s more practical benefit to improving the tools and teaching programmers how to handle errors, so that we can decrease the negative impact that bugs will have.