Fabric Data Factory Notes: designing pipelines for failure, not the happy path
I focused on making delivery decisions auditable and repeatable—documenting intent, success criteria, and rollback paths to reduce tribal knowledge.
26 articles
I focused on making delivery decisions auditable and repeatable—documenting intent, success criteria, and rollback paths to reduce tribal knowledge.
I worked on smoothing the handoff between data engineering and AI teams—standardizing feature contracts, embedding validation, and adding lightweight…
I turned implicit processes into explicit operating rules—defining owners, acceptance tests, and lightweight runbooks so teams can move confidently and…
I focused on making delivery decisions auditable and repeatable—documenting intent, success criteria, and rollback paths to reduce tribal knowledge.
I spent the day reducing cognitive overhead for engineers and analysts—introducing clearer table contracts, simpler failure modes, and concise runbooks that…
I spent the day reducing cognitive overhead for engineers and analysts—introducing clearer table contracts, simpler failure modes, and concise runbooks that…
I worked on smoothing the handoff between data engineering and AI teams—standardizing feature contracts, embedding validation, and adding lightweight…
Someone asked me last week if I miss being a principal engineer. I had to think about it longer than I expected.
Here's what it is, how it works, and a pattern that's running in production. Traditional analytics is batch-oriented. Data lands in storage, gets processed…
Seven years ago, a senior engineer reviewed my code and said nothing about the code. I've thought about that review almost every week since.
A unified platform for building, deploying, and managing AI applications and agents at enterprise scale.
In 2024, the community consensus was "RAG first, fine-tune never." In 2026, it's more nuanced.
My son Andriel is nine. Last weekend he was building a LEGO set and got stuck. I watched him work through it for twenty minutes without knowing he was…
When I tell clients "everything in Fabric uses Delta Lake format," the room divides. Data engineers nod. Everyone else says "what?"
When you send the same prompt prefix repeatedly—system instructions, context documents, examples—the model recomputes them every time. Prompt caching stores…
Workflow: Predefined steps. AI handles specific tasks within a fixed pipeline. Deterministic flow.
It worked, but managing five services with five billing models and five sets of credentials was painful.
Production AI needs real evaluation. Here's how I approach it. You test with 5 prompts. They look good. Ship it.
I've built data pipelines for 8 years. Every production deployment humbled me. Here's what the tutorials don't teach.
Last Tuesday I worked 10 hours. Got almost nothing done. Checked my calendar: 6 meetings scattered throughout the day. None longer than 30 minutes. Plenty…
This works for demos. It fails in production. Chunking matters more than you think. Random 500-token chunks lose context. A sentence about "the system"…
For an app with 100 users. Push to main. App deploys. Done. Don't add any of this on day one.
Three years ago, I was a cloud/data engineer. AI was "something other people do." Now it's a core part of my work.
I'm tired of clever code. I want boring, maintainable code. Early career: "Look at this elegant one-liner!"
Traditional testing assumes deterministic behavior. AI systems are probabilistic. Same input, different output.
o1's reasoning capabilities open up new possibilities for tackling complex problems that were previously difficult for AI to handle reliably.