Hypothetically: perhaps they are trying to curtail users spiraling during episodes of frustration or worse, impacting their own mental health, presentation, and product affinity.

Sounds like Anthropic is again over-reaching and making spurious assumptions in how it interprets the variety of ways its customers interact with their products...

No, they're just avoiding bad press.

Kinda like how if I break some plates at a restaurant I have to pay for it, but if Tony Soprano breaks them the restaurant pays him.

Protection is a heck of a business model, if you can get away with it.

I landed a massive database upgrade on a payroll system years ago, end-to-end standardization, cleanup, and improvement with a seamless rollout.

Our back clapping was interrupted by an angry customer phone call. One of our customers had gotten access to our internal schema and had a massive reporting setup in Access solving most of his needs.

I ended up converting his reports using some internal tools we had. Customers will grab anything to give them.

[The caliber and depth of his reports were such I wish we would have bought them instead of making me spend months building out our own reports.]

> [The caliber and depth of his reports were such I wish we would have bought them instead of making me spend months building out our own reports.]

Learning from customers is some of the best learning you can do. :)

I had one customer that managed to figure out which stored procs were tied to which reports we were using. Then he would deliberately break it in weird subtle ways them and call tech support 'just to see how we would react'.

Having built a hobo version of something similar (serving a minimal subset of the Kafka API on top of CosmoDB): there’s also the hybrid scenario where the cheap serverless streams are used for scalability and broadcast while a low-latency core is maintained on sharply reduced compute resources. An 80/20 approach that saves a lot and, in our case, reduced cluster (mis)management risks at the same time.

In our case BLOB and large document transfers were handled in parallel, merging them together through object storage is a highly appealing package. Great work!

Like how Tony Soprano sold sandwiches and ‘protection’ at the same time. Two income streams are better than one.

Blowing something up so hard it almost gets into space is a feat of engineering, even if all it does is rain debris from ahigh.

I believe it’s checkbox-filling in the acquisition process for enterprise contracts, like a lot of other half-baked capabilities in their flagship products.

It doesn’t matter how they work, it matters you can tell leadership “yes, they have that too” to maintain existing contracts and vendor relationships.

You’re precisely right. In corporate purchases many times it’s not the best product that is bought but instead the one that can answer yes to the most questions.

Speculation, but: if tech over hired during COVID our section of the market could be experiencing a corrective slowdown while others are booming in aggregate.

I think we can all agree No True LATAM company would have 10,000 employees.

Or, in parallel, the research showing LLMs intelligence will operate on an S-curve, eventually hitting a long valuation deflating plateau, is dead on the money and The Big Guys are trying to delay that inevitability for as many quarters as possible…

My hypothesis is that to date they've been increasing benchmark scores via scaling up, but now that low hanging fruit is basically picked.

Doesn’t seem to be the case as the price per token is not increasing…

These takes are fully fueled by cope. What is this plateau you are talking about? Any user of agentic coding tools sure isn't experiencing anything close to a plateau.

The pace of change is accelerating! If this is an S curve, we are still near the bottom…