So, here's the thing.
If this, someone would say, embarrassing level of availability came as a result of "90% of our code is written by agents, and we (mostly) don't review the code they generate", it's fine as long as the demand for your product is so disproportionately strong, that this level of (un)availability doesn't affect that demand to a level where customers would consider someone else instead of you.
1/n
But if you use the same approach to building software, and you don't have the same privilege of demand for your product as Anthropic does, then availability becomes utterly important as a perception of value for what your customers are paying for your product.
2/n
Availability that comes as a result of particular way of developing software needs to be put in a broader context, and your business is, I'd say, very likely far from the same position as those telling you to do the same thing they have the luxury of doing.
In short: the tipping point of the effects of poor service availability for most businesses out there is likely far earlier than for Anthropic, and trying to address it just-in-time is likely too little, too late.
n/n
Dragan Stepanović