Technical Debt
23 posts filed under Technical Debt.
Semantic Layer Pitfalls - Invisible Technical Debt
You bought a semantic layer to end the "which number is right" argument. Eighteen months later you have 200 metrics and the same argument, …
Read →Fitness Functions: Testing Your Architecture Like Code
You test your code. You test your data. But who tests your architecture? Here's how fitness functions change that.
Read →The 306K Per Million Lines: What Technical Debt Actually Costs
Nobody budgets for technical debt. But it budgets itself - in slow changes, frequent bugs, and engineers who quit.
Read →The Team That Automated Themselves Out of Firefighting
A data team spent 60% of their week doing the same manual tasks - and nobody questioned it for two years.
Read →The Acquisition Disaster - When Technical Debt Tanks a Deal
Due diligence found 15 "temporary" integrations from 2019 still running in production. The acquisition deal died that afternoon.
Read →Data Architecture Review - What's Actually Involved
A data architecture review uncovers hidden risks before they become expensive problems. Here's what mine covers and why most teams need one …
Read →Technical Debt Cost Calculation
Slow pipelines are a symptom. The disease is poor architectural decisions nobody revisited.
Read →Technical Debt Productivity Loss
Every data engineer on your team loses 2 days per week to technical debt. That's time they can't spend building.
Read →Platform Review: 3-Month ROI for a Series B Startup
Every growing startup hits the same three data problems. Not similar. Identical.
Read →We Shipped Fast. We Paid Slowly
The problem isn't shipping fast. It's not being able to fix fast.
Read →