Again, I responded elsewhere, but I don't think the article was about actually having ZERO bugs. It was about enforcing a strict classification system so you can implement a reasonable prioritization scheme (Critical issues and Bugs are fixed FIRST by distinguishing what are actually bugs and what are Improvements).

So it's an article on the development lifecycle and how to get consistent forward progress with some organizational improvements. It's not actually about writing software with "Zero" bugs.