3 ms·

First thought: if I left bad or useless code in a commit, how many levels of verification would it need to pass to make it to production?

• kenperkins 2y ago
  my thought was that if you get an alert that a key system is flapping in production, your first thought shouldn't be to squelch the alert.
  • ethbr1 2y ago
    That's partly where I was going: performative vs effective processes. Otoh, the fact that there's a clear audit log that this happened, even if it wasn't effectively handled at the time, is quite impressive. And finding a lost tool is a toughy -- how do you avoid an infinite loop, looking for something that really did walk off the site and/or end up in a trash can? You can't prove the lack of something.
• addaon 2y ago
  For code running in a commercial jet engine, so usually DAL A or DAL B? You should be caught by the first level of verification —- can’t even get past code review, because you don’t have a requirement to tag to trace the useless code back to. If that process failed (and any can), you have the whole climb up the right side of the V. And in the end, if the code is not /so/ useless as to be removed by the compiler, the final check that all generated bytes have traceability should catch it.