How to Make the Architectural Case for Dagster ↗
Using the Orchestration Maturity Model to compare job-centric scheduling with platforms that represent data assets and their dependencies.
Conceptual Layer
I help European platform teams implement Dagster, migrate job-centric pipelines to assets, and operate Dagster on Kubernetes. My current work focuses on the orchestration practices needed to keep analytics, AI, and agentic workloads supplied with observable data. I also created the Orchestration Maturity Model, a framework for assessing how a platform represents and operates its data.
Work with me on DagsterLatest Articles
The Data Orchestration Maturity Model: A Field Guide
A reference guide for assessing whether your orchestration platform manages scheduled jobs, data assets, or a shared data product.
The Ceiling of Job-Centric Data Platforms
A job scheduler can report that code ran. Data teams eventually need to know whether the data is ready, correct, and safe to rebuild.
From the Blog
The LLM Loop: A Mental Model for Better AI Work
A practical loop for improving LLM work by changing the instructions, context, model, or next iteration after each answer.
Stay in the loop
New writing on orchestration, data platforms, and the Orchestration Maturity Model, delivered to your inbox.
Subscribe on Substack