This is great! Especially nice to hear as I'd been all to aware of the advice to not rewrite your whole codebase once you raise some money as that's an easy way to tank the company. As a result I have probably erred to much on the type of refactoring he compares this to.

More recently I have been more aligned with the shredding approach. I think one of the reasons that it works that isn't mentioned here, is that often you only really know what's needed after finishing the first implementation and/or using it for a while.

I'm also reminded me of the Japanese practice of rebuilding a temple every 20 years: https://longnow.org/ideas/long-term-building-in-japan/

I'm confused about the title. Should it also say "shredding"? Still doesn't make sense, though..