Thoughts
I think I finally kind of get the philosophy behind "move fast and break things." I think in order to do it well you have to have
"zero-friction bug-fixes."
I guess what I'm imaging is a tangentially related idea that I'm going to call "zero friction bug fixes, low friction development." And the idea goes, "how do we ship software with less bugs?" Well, a lot of people do test-driven development or they push for better CI testing or integration testing or use a strictly typed language. But those things add friction to the development process, and they're not perfect. You're still going to have bugs. So at think at some point you have to optimize for fixing things. This is the fail-fast model. Just swallow your pride and fix the issue as quickly as possible.
I'm coming to terms with the fact that it's impossible to make perfect software. Your users, as an arbitrary-complex analog conglomerate, have a set of needs and desires that are impossible to meet.