Re:The Zero-Bug Policy in Software Development
by samhatoum on Monday May 09, 2016 @04:01PM
(#11662668)
It's not just about critical bugs though. Those are "stop what you're doing and get on it". ANY bug that is not critical gets worked on next no matter what. So it's about all bugs getting priority over other work.
It's akin to an immune system. When a bug is found, it's attacked until it's dead.
I really appreciate this feedback. As there are a few people that the phrase is rubbing up the wrong way, I'll meditate on it a little and see what I come up with.
Re:The Zero-Bug Policy in Software Development
by kazinator on Monday May 09, 2016 @04:20PM
(#11662811)
I understand; but it's hard for some convenient phrase to cover every aspect of the process. So in the end there has to be some understanding that it's the name of some process that has more aspects than just the literal meaning. (Just like "Zero Bugs").
Another way to approach this is from the angle of: no customer is left to dangle in a situation where they aren't getting value from the product, where they are faced with an issue for which there is no feasible workaround, or some security breach. What's a glib phrase which quite precisely conveys the idea that try to prevent this situation at all costs, and get them out of it ASAP if it happens?