I agree that this method might work for statsheet.com, at least in its current incarnation, but it's a bit of a special case. Just because you can rely on spot-checking and only reacting to critical errors when you're strapped for resources doesn't mean it's a good model.

It's like writing a post talking about how you've eaten beans and rice for the past four months. Maybe you needed to do it that way to keep your company afloat, but that doesn't mean that the post constitutes advice.

When bootstrapping a startup a lot of exceptional circumstances occur. Not having resources to test a massive web of pages and data is one of them. The last paragraph of the post makes this clear.