Convert an ADF mapping data flow into dlt and dbt and prove parity
Order or customer reporting still comes from an Azure Data Factory mapping data flow whose logic lives only on the ADF canvas, with no tests or review.
- Transformation
- Any domain
Re-engineer something you own
14 RecipesRebuild something already in production and prove the new form behaves like the old one.
Backfill a bounded date range after a logic change without a full refresh
A business rule in an incremental model was corrected, and only a known date range of published history should be restated.
- Transformation
- Any domain
Convert a full-refresh dbt model to incremental and show the runtime delta
A dbt model is correct but a full refresh is too slow or too expensive to run routinely, and gets slower as history grows.
- Transformation
- Any domain
Refactor dbt models without changing consumer output
A model has grown into one long query with logic packed inline, and nobody dares change it because dashboards and reports depend on its output.
- Transformation
- Any domain
Convert a legacy SQL script or view into a dbt model and prove parity
A report or table is still produced by a hand-run SQL script or a database view outside dbt, with no tests, lineage or review.
- Transformation
- Any domain
Replace a Fivetran or Airbyte connector with a dlt pipeline and reconcile the result
A managed connector's bill changed shape, or it broke and the vendor fix has been pending for weeks, and the team wants the load in code it owns.
- Ingestion
- Any domain
Convert a materialized view into a dbt model and preserve its required refresh semantics
Warehouse logic lives in a materialized view that nobody can test, review or trace, and the team wants it in the dbt project.
- Transformation
- Any domain
Convert a notebook transformation into a dbt model and prove parity
A table or report is still produced by running a notebook by hand, pulling warehouse data into dataframes, with no tests, lineage or review.
- Transformation
- Any domain
Convert a scalar SQL function into a dbt macro and prove equivalence
Models or views call a scalar function created directly in the warehouse, so dbt cannot see the dependency and changes to it are not reviewed or tested.
- Transformation
- Any domain
Convert a hand-written history routine into a dbt snapshot and prove history parity
A Type 2 dimension is kept by a hand-written MERGE procedure or trigger that nobody wants to maintain.
- Transformation
- Any domain
Convert a Spark ingestion notebook into a dlt pipeline and reconcile what it lands
A Spark notebook lands raw files into bronze, and the team wants that load as tested pipeline code without keeping a cluster for it.
- Ingestion
- Any domain
Convert a stored procedure into a dbt model and prove parity
A nightly load is a stored procedure nobody fully understands, and it inserts, updates, deletes or merges rows in a table people depend on.
- Transformation
- Any domain
Add a breaking data contract change as a new version beside the old one and revise its named consumers
A required change to a published relation's grain, column meaning or shape cannot keep the old interface.
- Transformation
- Any domain
Rebuild an exported visual ETL mapping as dlt and dbt and prove parity
A load into a fact or reporting table still runs from a mapping built in a visual ETL tool, and its lookups, filters, routing and insert-update-delete rules are visible only on the tool's canvas.
- Transformation
- Any domain