How Pattern uses Metaflow to enable DS to own end-to-end deployments without chaos

Metaflow is powerful and highly unopinionated. Which is cool, but it left us with many decisions we needed to make about what our standard project structure and workflow would look like, so we didn't have chaos after making it available to DS. We landed on a DS monorepo with strict controls over which git branches can write to which Snowflake tables. We're also using a "micro-templating" tool out of AWS called projen to keep the projects within the monorepo looking similar. We've already bumped into our first real-world challenges to our design assumptions, but overall, it seems to be holding up well. I'll be showing how we've set it up, and I'd love input from other Metaflow users on improvements they think we could make.