title: Testing by flipping bits makes no sense?
body: <p>When reading <a href="http://perspectives.mvdirona.com/2012/02/26/ObservationsOnErrorsCorrectionsTrustOfDependentSystems.aspx" rel="nofollow">this</a> it said</p>
  
  <blockquote>
    <p>Remember that all hardware, all firmware, and all software have faults
    and introduce errors. Don’t trust anyone or anything. Have test
    systems that bit flips and corrupts and ensure the production system
    can operate through these faults – at scale, rare events are amazingly
    common.</p>
  </blockquote>
  
  <p>I don't understand. Is it possible to run any type of software if you flip bits? pointers will be incorrect and if you read for an address on a switch case (or even function call) you can start executing in no mans land. Heck, the stack could be overwritten. If your stack is gone how could you possibly recover. You can't, you have to terminate and restart again. Terminate+restart is hardly recover.</p>
  
  <p>How do you 'test' a production system but forcing a part to terminate? Is this actually saying if the system is multiple CPU/systems unplug a system and see if it non unplugged system corrupts or crashes? Otherwise i don't understand what this is suppose to mean.</p>