According to the author, shipping code that erases your hard drive when you click "Quit" is not a defect (because it does so consistently), and fixing those kinds of bugs can be postponed. I didn't find his argument very convincing, though. The first time your customer clicks quit and has their drive erased, you will have an ex-customer.
This is a good point. There will always be bugs that need to be cherry picked for critical status. Managing criticals and blockers is also important in the development feedback cycle.
