Topic
Data pipelines without silent errors
The worst data bug is the one that doesn't crash. The load “completes”, the report opens, and the number is wrong — a schema that changed in silence, a join that inflated the total, a record dropped by an INNER JOIN, money typed as a FLOAT. This is where I collect what actually breaks trust in a production pipeline and how to guard against it: data contracts, validation that fails loud instead of silent, quarantine before the report, and real reproducibility. It's the engineering side of “can we trust this number?” — written by someone who has fixed it in production, in finance and international operations.
Data Contracts in dbt: How to Stop Silent Pipeline Failures
A data contract in dbt catches a schema change before it becomes a wrong report. What it is, how to enforce model contracts, and why it stops silent failures.
Read article →The silent data failure that corrupts a report without warning
A file layout changes, a column shifts, and the report still looks fine — but the number is wrong. How silent failures happen and how to stop them.
Read article →
This is exactly what I do in A data pipeline that breaks loud and early — never in silence.
Does this sound like your problem?
A 30-minute call, no commitment. I'll tell you where the risk is and what to fix first.