General posts

Lessons for Today’s Leaders: Don’t Wait for the Cracks

Five lessons from building and breaking data infrastructure at scale: spot the slow drift before it becomes a crisis, revisit build-vs-buy honestly as the business grows, put the right people on the right problems, design for change not stability, and treat data movement as a strategic investment not just plumbing.

When Your Data Infrastructure Can’t Keep Up With Your Business

Co-founder and CTO of a 150k-transaction/day insurance marketplace shares how building data infrastructure in-house seemed smart until schema changes, broken pipelines, and misallocated engineering talent quietly consumed the business.

When "Good Enough" ETL Becomes a Strategic Blind Spot

Most data leaders don’t see the moment their infrastructure turns into a cost center. This piece examines the hidden economics of “good enough” ETL, including where the real spend hides, how it compounds over time, and how an adaptive data movement layer can reverse the burn rate without a disruptive overhaul.

The Core Principles of DataDevOps: From Workflows to Governance

Your data pipelines weren't designed for the challenges you're facing now, and they're definitely not ready for what's coming next. In this post, EASL co-founder John Derham walks through the six principles that separate fragile data infrastructure from systems built to scale: from thinking in workflows instead of connectors to embedding governance that enables speed.

DataDevOps Is Inevitable. The Question is When.

The moment your data needs to support live operations instead of just retrospective analysis, a lot of assumptions stop holding. EASL co-founder John Derham describes what starts breaking down in data environments at that inflection point, why AI makes those weaknesses impossible to ignore, and how the organizations handling it best are fundamentally rethinking who's responsible for data infrastructure.

From Maintenance to Momentum: A Practical Path to Adaptable Infrastructure

The appeal of a big modernization project makes sense—fix everything at once. The problem is that "at once" usually means six to 18 months, and your team still has to keep everything running in the meantime. The path to adaptable infrastructure starts much smaller, with one problematic data flow and a framework for compounding wins. Here's how to restore momentum without stopping the business.

You Gotta Get Your Data Right