I&#x27;m sorry, I hate to be a pain, but it&#x27;s a pet peeve of mine. They weren&#x27;t &quot;glitches&quot;. They were defects.<p>Glitches are errors that happen outside of the design parameters of the system. For example, when you touch the antennae on an AM radio and you hear a pop or buzz from your own electrical field in the radio.<p>Defects are errors that occur within the design parameters. So a train that can&#x27;t handle some snow on the tracks, or a national health insurance enrollment site that falls over after only a few users show up, those are defects.<p>Bugs are a type of insect. Using the word &quot;bug&quot; to describe a defect implies that the &quot;bug&quot; showed up, an external factor that got in and gummed up the works or something. But that doesn&#x27;t happen in software. The defects were always there.<p>I think it&#x27;s important to use the terminology correctly and make a habit of using it correctly because I think it puts the emphasis on the fact that we create the defects, and the defects were always there, they didn&#x27;t just develop, they just had to be found. That&#x27;s also why I don&#x27;t like the term &quot;software maintenance&quot;. When you have to take a site down for several hours every 3 months for &quot;routine database maintenance&quot;, that&#x27;s a defect in design, not just &quot;changing the oil&quot;.<p>It was our fault. Calling them &quot;bugs&quot; or &quot;glitches&quot; or &quot;maintenance issues&quot; diminishes that.