Automated Data Contract Enforcement and CI/CD Quality GatesHow we stopped 30+ pipelines a quarter from breaking, by catching bad schema changes before they ever ship The Problem, in Plain English In one sentence: a team upstream changes something in their daAug 29 · 14 min readdata-engineering-sailesh.hashnode.dev
Why Sales Sometimes "Lose" a Customer and How We Fix ItThe Problem, in Plain Terms Imagine a sale comes in before we know anything about the customer who made it. That happens more often than you'd think a purchase gets recorded instantly, but the customeAug 29 · 4 min readdata-engineering-sailesh.hashnode.dev
The Late File Problem: A Safe Backfill Runbook for Recurring EDI DelaysYour EDI vendor sends a file 2 days late. Now what? Re-running the whole month is slow, risky, and can create duplicate records. This post walks through a repeatable, low-risk backfill pattern built oAug 29 · 12 min readdata-engineering-sailesh.hashnode.dev
Fixing the Past Without Breaking the Present: How Enterprises Backfill Historical DataA plain English look at a real problem every large company eventually hits and how to solve it safely. Table of Contents The Problem in One Sentence Why You Can't Just "Start Over" Five SituationsAug 6 · 10 min readdata-engineering-sailesh.hashnode.dev
Deduplication and Late-Arriving Data HandlingHow we stopped rewriting the entire lake every night and started scoping dedup work to exactly the partitions that changed Domain: Data Engineering Stack: Azure Databricks, Delta Lake (MERGE + Z-OrdeAug 4 · 11 min readdata-engineering-sailesh.hashnode.dev
