I build data-powered systems, from cloud foundations to workflow apps and AI tools people can actually use.
Data architecture roots
AWS + Azure + GCP
AI workflows with guardrails
Shipped personal products
What I Build
I like the full path: finding the messy operational problem, designing the data foundation, and shipping the app, automation, or AI workflow that makes it useful.
Data Platforms
Lakehouses, pipelines, semantic layers, governed workspaces, and the critical plumbing that keeps decisions trustworthy.
Operational Apps
Workflow tools, dashboards, map-based evaluation platforms, and SaaS-style products that turn process into usable software.
AI-Assisted Systems
Agents, summarizers, research workflows, and automation wrapped in permissions, source checks, logs, and human review.
Field Notes
Writing about the patterns, tradeoffs, and practical lessons behind data-powered systems.
Agents Don't Just Make the Runners Faster. They Shorten the Track.
Most data work doesn't fail because one runner was too slow — it fails because the track is too long. Agents change the shape of the race by shortening the distance between code, deployment, infrastructure, logs, databases, and the BI layer. The shift matters most in data engineering, where Fabric is finally making the messy middle agent-operable.
Read field note →
The New Control Room: The Evolution of the Data Team
Data engineering used to mean keeping the plumbing running. Agentic coding environments are changing that — giving data teams a new control room that operates across code, cloud, data, and interfaces, and shifting the role from pipeline maintainer to general contractor.
Read field note →
The Warehouse Is a Museum. Agents Need the Live City.
We built the data warehouse like a museum — curated, organized, and full of artifacts from the live systems that actually run the business. That worked for analytics. But agents are not archivists. They are operators. And operators need to work in the live city, not a copy of it.
Read field note →
Rethinking the Modern Data Stack
As data engineering matured, factories became the default. Assembly lines brought reliability when tools were weak, storage was expensive, and mistakes were costly. But the constraints changed, and the architecture didn’t. Today, we still build stacks by habit—pre-aggregating, orchestrating, and industrializing work before we understand it. In this post, I argue for an anti-stack mindset: start with workshops, use strong tools at query time, delay pipelines until they’re earned, and treat factories as an optimization—not a prerequisite. The goal of modern data engineering isn’t to keep the line running. It’s to deliver insights.
Read field note →
From Soloist to Symphony: The Case for Data Engineering
As organizations grow, they transform from solo musicians into full orchestras — and that's when the real challenge begins. Data doesn't stop being collected; it stops being aligned. Systems drift, meanings diverge, and interpretation fragments. Data engineering exists not to make the orchestra louder, but to keep it playing the same piece, in the same key, at the same tempo. In this post, I explore how coordination becomes essential at scale, why AI amplifies (but doesn't replace) this need, and how the discipline of data engineering becomes foundational leverage in the AI era.
Read field note →
About Me
I'm a builder with deep data architecture roots. My work sits where cloud platforms, data products, operational workflows, and AI-assisted tools meet, with a bias toward systems that are clear, durable, and genuinely useful.
Learn moreWant to See the Work Behind It?
The work page has the public-safe version of the production systems and flagship personal builds behind this positioning.