The article seems to repeatedly confuse product quality with code quality, as if they're interchangeable. They're not, and that confusion pretty much undermines the entire argument.
Product quality is an emergent property of code quality.
Code base is an emergent property of a product (that can have no code at all in practice). I'd even argue that the less code a product needs, the better — with no code being the ideal.