I think they built the NPU with whatever models they needed to run on the iPhone in mind vs trying to build a general purpose chip, and then got lucky it was also useful for LLMs.
(Like “I want to do object detection for cutting people into stickers on device without blowing a hole in the battery, make me a chip for that”.)
It forces you to pay at least $20 in tokens per user even for people who use less (they probably have stats on how many people use just autocomplete, which doesn’t count against the quota. or have a seat and don’t use the service at all).
You can get at least at baseline vague stats but from what I have seen it is more account than user focused, i.e. 'X number of users used %feature%' and/or '%model% was X percent of requests per day'.
That said it's worth noting, I don't see how anything they expose will reliably help orgs plan costing from what AFAIK is in fact a big shift for billing/costing planning.
> It forces you to pay at least $20
For better or worse that's public pricing, i.e. if you are coming in also negotiating VS for devs, windows/office licenses for the rest of the business and stuff like Azure Devops... a lot of their stuff gets cheaper if your company's IT procurement group is vaguely competent at negotiating. Not even talking bigcorp here I'm talking 500-1000 employee range.
Of course, very small orgs will suffer, but it does tie in with the theme over the last two weeks; anyone with a personal account is basically subsidizing the credits for the business accounts during the transition period.
Isn’t that an “API product”? I read this assuming the whole point of renegotiation was to let OpenAI sell raw inference via bedrock, but that still seems to be blocked except for selling to the US Government.
AWS actually has a thingy on some services called “deletion protection” to prevent automation from accidentally wiping resources the user didn’t want it to (you set the bit, and then you need to make a separate api request to flip the bit back before continuing).
I think it’s designed for things like Terraform or CloudFormation where you might not realize the state machine decided your database needed to be replaced until it’s too late.
And then, someone added IAM so you could actually restrict your credentials from deleting your database.
First mistake is to use root credentials anyway for Terraform/automated API.
Second mistake is to not have any kind of deletion protection enabled on criticsl resources.
Third mistake is to ignore the 3-2-1 rule for backups. Where is your logically decoupled backup you could restore?
I am really sorry for their losss, but I do have close to zero empathy if you do not even try to understand the products you're using and just blindly trust the provider with all your critical data without any form of assessment.
GCP Cloud SQL has the same deletion protection feature, but it also has a feature where if you delete the database, it doesn't delete backups for a certain period of days. If someone is reading this and uses Cloud SQL, I highly suggest you go make sure that check box is checked.
If we take that literally, then just remove all destructive API endpoints. Because then, it they no real purpose, you cannot automate the removal of anything.
I think some other suggestions are saner (cool-down period, more fine-grain permissions, delete protection for certain high-value volumes). I don't think "don't allow destructive actions over the API" is the right boundary.
A human representing the company should be physically present in the provider's office to perform such an action or what? Otherwise you would just grant your agent a way to impersonate a human.
The developer seats are read-only, so they rely on designer seats existing to actually create files to inspect for development (and I’d guess PMs are using figma because designers are using figma).
If designers still want Figma then the other people are along for the ride (unless the idea is the designers are being replaced with a PM+Claude.)
As a PM in a startup, it took me a while to convince my boss I’m not a designer. It’s so easy nowadays to get a Figma file with an established design system and produce new features.
There are Figma plugins that let you extract a static HTML website into a Figma file. Copying that over Figma Make and prompting for a while can make pretty good prototypes that need very little adjustment back in Figma.
However, I believe that being able to do something doesn’t mean you should do it. Prompting back and forth can easily introduce a lot of cognitive load on top of all sorts of other daily task.
I feel the modern human in the loop is similar to the factory processing line workflow where just almost anyone can learn how to use a tool and produce output.
Huh - I know Apple’s first PowerBook 100 had an ad with Shaq on a plane, and then later one with Yao Ming… I guess Apple really wanted to crack the “I’m working on a plane damn it” market?
Not only that, but due to their pattern of putting letters after the version number the current version is Oracle AI Database "26ai".
I skimmed the video and the presenters said "Oracle AI Database 26ai" multiple times without even a glint of self awareness on their face. They must've picked the only people on the team that could say that without laughing.
reply