Unsaid in that article is the implicit assumption that the product is webcrap. Not industrial controls, or code within a device that ships to the customer, or the internals of a database, router, or operating system. Implications of this include:
* Errors are mostly harmless, unless they occur too frequently.
* Failures that can be handled by having the end user retry something are generally OK.
* Changes are very frequent and are made for marketing reasons.
Hence the emphasis on moving fast and breaking things. The cost of the breakage does not fall on the implementing organization.
* Errors are mostly harmless, unless they occur too frequently.
* Failures that can be handled by having the end user retry something are generally OK.
* Changes are very frequent and are made for marketing reasons.
Hence the emphasis on moving fast and breaking things. The cost of the breakage does not fall on the implementing organization.