karmeliet

It's exactly the same pricing (East US):

https://azure.microsoft.com/en-us/pricing/details/cognitive-...

https://openai.com/pricing

I really like the Ohropax wax or silicon earplugs. They don't penetrate your ear canal as much as the foam plugs, but still provide a good enough 23 db noise reduction. They definitely make my tinnitus more noticeable, but I'm kind of used to it anyway at this point.

Then you are a "bad operator" according to Escoffier:)

  "I should thus resemble those bad operators who, having neglected their mise en place, are obliged to make it in the course of other work, and thereby not only run the risk of making it badly, but also of losing valuable time which might be used to better advantage.
  Elementary preparations consist of those things whereof one is constantly in need, which may be prepared in advance, and which are kept available for use at a moment's notice."

A modern guide to cookery, A. Escoffier 1907

Mise en place is a useful mental model for everyday activities, but I don't think the author gave a good example in the post.

I don't think intensity or difficulty is the key differentiator between preparation and the actual work. To me, it's mainly about separating tedious and repetitive tasks from the ones that require attention and creativity.

Prep work means that you perform something that you have done many-many times before and it feels automatic. Prep can be also harder and more intense in many ways than the actual work itself.

Every time when an app throws me a “Are you sure you want to do xyz?” dialog.

To be fair, to achieve the best multi-threaded performance in Azure the Dv2/Dsv2 version provides real cores and not threads.

They've got breached yesterday.

https://cybernews.com/news/anonymous-leaks-database-of-the-r...

Actually, you can do that already in M365 with Double Key Encryption [1]. The obvious trade-off though is that none of the cloud services will be able to work with your data. For example you won't be able to search or open the document inside the browser which basically renders your SaaS environment (partially) just a plain cloud storage.

DKE should not be confused with any other BYOK service, where you only manage the key, but host it on Azure so MS still has access to you private key.

I think there could be middle ground where customers could select a set of metadata that they are willing to share with the cloud provider or even better, select only the sensitive parts of the document that must be encrypted with their own key.

[1] https://docs.microsoft.com/en-us/microsoft-365/compliance/do...