Get running in your own environment
Bring an existing project or environment to a usable starting state, against your own platform.
1 Recipe
Cookbook
79 Recipes. Each one is a requirement-sized piece of data engineering work — a single outcome you can name, adopt, and review against acceptance conditions written down before the work starts. Recipes compose; the Cookbook is what they compose from.
Canonical definitions: 1 of 79. The rest are drafts written for this prototype. Readiness — whether the capability exists yet — is a separate question, and every Recipe answers it for itself. The worked example is Convert a full-refresh dbt model to incremental and show the runtime delta.
Written for data engineers. Finance, banking and telecom name the data you are working on, not a different reader.
Browse by job
Every Recipe sits in exactly one of these six. They are the kind of work, not the subject of it.
Re-engineer something you own
Rebuild something already in production and prove the new form behaves like the old one.
10 Recipes
Build something that is not there yet
Create a pipeline, model, or data product that does not exist yet, with its proof attached.
61 Recipes
Prove a change is safe before you ship
Establish whether an existing change is safe or equivalent without changing it further.
1 Recipe
Explain a number after you shipped
Work out why an observed number, result, or cost came out the way it did.
1 Recipe
Work across more than one platform
Deliver an outcome whose defining difficulty is that it spans more than one platform.
5 Recipes
Collections
A Collection is a view over the same Recipes, not a copy of them. The same Recipe turns up in several, and it is the same Recipe in each.
By domain
The domain whose data you are working on today. You are still the data engineer in every one of these.
Larger outcomes
Recognisable pieces of work that take more than one Recipe, assembled rather than merged.
By industry
Vertical Recipes together with the horizontal ones that vertical reaches for most.
Browse by platform
Where the work can actually run. A Recipe states its exact execution targets; these three are how you browse them.
Microsoft Fabric
Every Recipe that runs on a Fabric Lakehouse, a Fabric Warehouse, or both. Which of the two a Recipe needs is stated on the Recipe, because it decides whether the work can run where you are.
78 Recipes · Lakehouse and Warehouse inside
MotherDuck
Recipes that execute against MotherDuck, including the ones built locally on DuckDB first and run there afterwards.
73 Recipes
DuckDB
Recipes you can run on a local DuckDB file, at no cost and in no queue. The shortest way to see what the work feels like before it touches a shared platform.
73 Recipes