I put together a database of known public technical writeups with summaries of the key technical features.
What you're looking at:
What you're looking at:
Day-one notes on what it's actually like to build one:
Day-one notes on what it's actually like to build one:
I originally wrote our Quick Wins docs page as a collection of 15 things you can do in ~5 minutes to make your ZenML pipelines more robust. It's always been a sleeper hit.
I originally wrote our Quick Wins docs page as a collection of 15 things you can do in ~5 minutes to make your ZenML pipelines more robust. It's always been a sleeper hit.
😓
😓
ZenML only officially supports Python, but PyO3 compiles Rust into a native Python module. ZenML doesn't know or care that there's Rust underneath.
ZenML only officially supports Python, but PyO3 compiles Rust into a native Python module. ZenML doesn't know or care that there's Rust underneath.
The problem: law firms can't send confidential contracts to external APIs. But they still need sophisticated clause classification across 41 legal categories.
The problem: law firms can't send confidential contracts to external APIs. But they still need sophisticated clause classification across 41 legal categories.
When you're running 10,000+ DAGs and 150,000 runs per day, patterns emerge. Shopify noticed that engineers were clustering their cron schedules at "nice" times: midnight, 9am, top of the hour.
When you're running 10,000+ DAGs and 150,000 runs per day, patterns emerge. Shopify noticed that engineers were clustering their cron schedules at "nice" times: midnight, 9am, top of the hour.
We added 12 new read-only tools covering entities AI assistants actually need to understand your ML infrastructure:
→ Deployments: Discover what's running, check status, pull bounded logs
We added 12 new read-only tools covering entities AI assistants actually need to understand your ML infrastructure:
→ Deployments: Discover what's running, check status, pull bounded logs
Schedules are a good example. At first glance: cron expressions, start times, done.
Here's how ZenML's approach to schedules evolved:
Schedules are a good example. At first glance: cron expressions, start times, done.
Here's how ZenML's approach to schedules evolved:
Built a quick tool to find out—swipe right if satisfied, left if not. Rated all 1000+ books in one sitting.
Built a quick tool to find out—swipe right if satisfied, left if not. Rated all 1000+ books in one sitting.
In 2018, Twitter's Cortex team built ML Workflows on Airflow to replace the ad-hoc scripts teams were using to retrain models.
Before: "manually triggering and waiting for a series of jobs to complete."
After: scheduled retraining that ran reliably.
In 2018, Twitter's Cortex team built ML Workflows on Airflow to replace the ad-hoc scripts teams were using to retrain models.
Before: "manually triggering and waiting for a series of jobs to complete."
After: scheduled retraining that ran reliably.
I want it more for documentation tasks + other local filesystem work rather than for coding per se.
I want it more for documentation tasks + other local filesystem work rather than for coding per se.
TRMNL is a small e-ink display—pulls data via webhooks and shows it on an always-on screen. Perfect for keeping an eye on ML pipelines without constantly checking the dashboard.
github.com/zenml-io/tr...
TRMNL is a small e-ink display—pulls data via webhooks and shows it on an always-on screen. Perfect for keeping an eye on ML pipelines without constantly checking the dashboard.
github.com/zenml-io/tr...
The problem: I'm deep in implementation work, and a tangential question pops up—"wait, how does this other module handle auth?"
The problem: I'm deep in implementation work, and a tangential question pops up—"wait, how does this other module handle auth?"