MostlyAmiable

Yup, I just checked in multiple workspaces and I was unable to connect in all of them.

> I read documentation on my leisure time.

There are dozens of us!

What was your method for drawing/generating the SM diagram?

The other commenter was actually just mixing it up with the broken windows fallacy[0]. Funnily enough, it's a common enough confusion that both of the pages reference each other at the top of the page.

>This article is about the economic parable. For the criminological theory, see Broken windows theory.

[0] https://en.wikipedia.org/wiki/Parable_of_the_broken_window

War risk insurance absolutely exists.

> Insurance industry sources said that war risk premiums had stayed firm on Monday at between 0.05% to 0.1% of the value of a ship, from around 0.03% estimated last week before the attacks.

https://www.reuters.com/world/middle-east/war-risk-insurance...

Apparently it was plagiarized from here: https://medium.com/@mbianchidev/2023-devops-is-terrible-ec88...

Do you have any favorite episodes you'd recommend starting with?

Wow, wasn't expecting that quick of a turnaround.

No worries, on the whole the documentation is top notch.

The link in the docs to the CloudFormation template source is broken: https://docs.metaflow.org/metaflow-on-aws/deploy-to-aws#clou... Instead of /Netflix/metaflow-tools/aws it should probably be /Netflix/metaflow-tools/tree/master/aws

My main issues are that if you're using the serving functionality, the containers it builds take a long time to start because the environment/dependencies are loaded at runtime instead of being baked into the image. Also, it doesn't have the ability to use a db or remote file store to save experiment info, so you need to use EBS volumes or something for persistence.