Notities over data-architectuur.
Korte essays over architectuur, kosten, aanwerven en AI: één cartoon, één idee, bijna elke dag van de week. Geen tutorials, geen lijstjes.
Data Product Canvas Update For AI Consumers
Your newest data consumers don't file tickets. They're AI agents, and they break differently.
The Temporary Pipe That Stayed
A "temporary" sync script ran for 18 months. It was quietly eating 20% of the compute bill.
Lezen →Phoenix Project Lessons For DE
The Phoenix Project is 13 years old. Data teams still run their backlogs the way it warns against.
Lezen →Team Complexity Post-MVP
By 20 engineers, most data teams have one person every change waits on. The backlog put them there.
Lezen →Too Deep Into Snowflake" Is an Architecture Smell
You can measure architecture health by the price of an exit. For one stack I reviewed, it was 18 months.
Lezen →Brooks Law In Data Hires
A scaleup added 3 data engineers to catch up. Delivery got slower for 2 months.
Lezen →Data Reliability Over AI Speed
A plain statistical baseline caught model drift before any human would have. It took an afternoon to build.
Lezen →Pipeline Replay Decision Tree
Most pipelines are designed for the happy path. The first real outage makes recovery the only thing that matters.
Lezen →Fractional For Stack Survival
A fintech founder asked me to sanity-check their data stack three weeks before a raise. It wouldn't have survived the investor's technical …
Lezen →75% Belgian SMEs On AI Daily
Three in four Belgian SMEs now use AI daily or weekly. Most are running it on data they wouldn't trust for a board report.
Lezen →Lakehouse Convergence Risks
The lakehouse pitch is one platform for raw files and clean tables. The trap is inheriting the data lake's oldest habit: land everything, …
Lezen →Databricks DBU Trap For ETL
Your Databricks bill is mostly DBUs. A lot of those DBUs run ETL that never needed Spark in the first place.
Lezen →Hero DE Burnout Cycle
Praising the engineer who fixes everything at 2am rewards the exact dependency that eventually takes the platform down with them.
Lezen →Premature Real-Time Tax
Streaming has a cost nobody puts in the business case: the weekly tax of running it after the demo works.
Lezen →Fractional Architect Series B Audit
Investor technical due diligence has one real question: will this stack survive the growth the round is funding?
Lezen →Wrong DE Hire Cost Matrix
A wrong data engineering hire runs you about three salaries by the time you count the ramp, the re-hire, and the work that stalled in …
Lezen →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, …
Lezen →FinOps Maturity For Data Teams
Most data teams know their monthly cloud bill. Far fewer can tell you which euro produced value and which one was pure waste.
Lezen →Leadership Bottleneck In Stacks
The 2026 data tooling is the best it's ever been. The bottleneck in most teams I see is still a leader who can't say, in two sentences, what …
Lezen →Deterministic vs Non-Deterministic AI
Run your AI feature twice on the same input. If a different answer would be a problem, you've found a deterministic requirement.
Lezen →Privacy By Design In Pipelines
Most teams collect everything "just in case," then try to add privacy when an audit looms. By then it's in 40 tables.
Lezen →The Fragile Organic Platform Fix
An e-commerce client's reporting ran on a spreadsheet one person updated by hand every morning. It broke every quarter, always at month-end.
Lezen →Stack Overflow On DE Shortage
The best data engineers move for ownership and a manager who can describe the strategy. A 10% bump alone rarely does it.
Lezen →Your AI Initiative Is Blocked by Context, Not Tokens
The team bought more tokens. The agent still gave confident, wrong answers. The bottleneck was never compute.
Lezen →FinOps Isn't a Dashboard. It's Architecture.
Nobody chose to keep 7 years of event logs. The default did. You've paid for it every month since.
Lezen →The Agent That Can Say I Don't Know
The cheapest AI safety feature in 2026: "I don't have current data."
Lezen →The Lift-and-Shift Lie
The cloud migration finished in March. By July the bill was 3x and nothing was faster.
Lezen →Ownership Vacuum After First Hire
The junior left in March. In May, marketing's dashboard broke and nobody knew who to call.
Lezen →Idempotency In Orchestration Failures
Your pipeline failed at 3am. The on-call engineer is now paid to clean up duplicates.
Lezen →Hard Credit Caps On Cloud DWH Spend
Resource Monitors are uncomfortable on purpose. That's why they save money.
Lezen →DORA Metrics For Data Pipelines
The DORA metrics work for data teams. Most data teams aren't measuring them.
Lezen →Conway's Law Pipeline Silos
Two teams sitting in different Slack channels build two pipelines that compute the same metric.
Lezen →NIS2 Reporting For Data Incidents
NIS2, DORA, and GDPR each want an incident report. Send the same one.
Lezen →The Batch Window That Ate A Weekend
The six-hour batch was eating one engineer's weekend every two weeks. Nobody had measured it.
Lezen →The Hiring Gap For Senior DEs
87% of tech leaders rate senior data engineer hiring as difficult. Most of them are bidding against AI startups.
Lezen →Westrum Culture In Data Teams
If your post-mortems start with "who shipped that," your org culture is the bug.
Lezen →AI Act Data Traceability Checklist
The AI Act compliance deadline is August 2026. Your SME doesn't need Atlan to make it.
Lezen →Contract-First Data For Cross-Team Handoffs
Most cross-team data fights are caused by an undocumented assumption upstream.
Lezen →Orchestration Tool Audit For Small Data Teams
Two-engineer data teams keep picking Airflow because it's "industry standard." Six months in, half the DAGs are commented out.
Lezen →Semantic Layer Is A Consistency Tool, Not A Speed Tool
A semantic layer is a consistency tool. Most teams buy it for speed and end up disappointed.
Lezen →Software Modernization Is Not Architectural Modernization
Software modernization and architectural modernization are different problems with different fixes.
Lezen →Brent Is Your Data Engineer (Phoenix Project applied)
Every data team has a Brent. The person every ticket eventually routes through.
Lezen →The Day Our Pipeline Became a Person's Full-Time Job
The day I realized our pipeline had become a person's full-time job.
Lezen →FinOps for Data Audit Checklist (8 Cost Levers)
Your cloud data bill grew 40% last year. Your revenue didn't.
Lezen →The Data Product Canvas (One-Page Definition)
An empty "consumers" field is the signal to deprecate the asset. Most teams ignore it.
Lezen →Blameless Post-Mortem Template for Data Incidents
Your data incident post-mortems end with "be more careful." That's not a fix.
Lezen →Data Platform Maturity Model (5 Stages)
Your data platform is at stage 2. You're copying stage 5 patterns. That's why it's breaking.
Lezen →When You Actually Need a Semantic Layer
Most teams buy a semantic layer the way they buy a data warehouse. Tool first, problem retrofitted.
Lezen →Data mesh is an org design pattern. Here are the 5 things you need before you st
Data mesh is an org design pattern. Here are the 5 things you need before you start.
Lezen →Everyone says "people, process, technology." Then they start by picking Snowflak
Everyone says "people, process, technology." Then they start by picking Snowflake.
Lezen →You have 47 data quality issues. You can fix 5 this quarter. Here's how to pick
You have 47 data quality issues. You can fix 5 this quarter. Here's how to pick the right 5.
Lezen →Your data platform has 6 vital signs. Most teams only check 2 of them.
Your data platform has 6 vital signs. Most teams only check 2 of them.
Lezen →Hybrid work changed how your data team collaborates. Nobody adjusted the archite
Hybrid work changed how your data team collaborates. Nobody adjusted the architecture decisions for it.
Lezen →Consolidating from 15 tools to 7 in 2026. Three drivers, none of them innovation
Consolidating from 15 tools to 7 in 2026. Three drivers, none of them innovation.
Lezen →Most data catalogs go stale within a quarter. The teams that prevent it do one t
Most data catalogs go stale within a quarter. The teams that prevent it do one thing before procurement.
Lezen →Choosing between 3 data platforms? Stop comparing demos. Here's the radar chart
Choosing between 3 data platforms? Stop comparing demos. Here's the radar chart that makes it objective.
Lezen →Your data platform has 15 incidents per month. Is that normal or a crisis? Here'
Your data platform has 15 incidents per month. Is that normal or a crisis? Here's the benchmark.
Lezen →This company piloted Data Mesh with 2 domains in 6 months. Here's what worked (a
This company piloted Data Mesh with 2 domains in 6 months. Here's what worked (and what didn't).
Lezen →Your data testing pyramid is upside down. Here's how to flip it.
Your data testing pyramid is upside down. Here's how to flip it.
Lezen →Your architecture decision has been stuck for 8 weeks. DACI resolves it in 3. He
Your architecture decision has been stuck for 8 weeks. DACI resolves it in 3. Here's how.
Lezen →AI is writing data quality tests now. That's not replacing you-it's multiplying
AI is generating data quality tests now. Not replacing you. Multiplying what you can realistically cover.
Lezen →The Dashboard That Took 3 Months: A Process Problem, Not a Complexity Problem
An executive requested a simple revenue dashboard. Three months later, it was live. It should've taken four weeks. Here's what went wrong at …
Lezen →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.
Lezen →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.
Lezen →The Hybrid Governance Rollout: From Bottleneck to Balance in 12 Weeks
Every governance rebuild I've seen starts the same way: a team that over-corrected once, then over-corrected the other way, and is now tired …
Lezen →Status Quo Is Never Free: Why Your 'Do Nothing' Option Has the Biggest Hidden Price
"Do nothing" is never free. One client's "zero cost" status quo was burning 200K a year in workarounds nobody tracked.
Lezen →CAP Per Workload: Why One Consistency Model Doesn't Fit Your Whole Platform
Treating finance and customer analytics like the same workload is how you end up with a platform that serves neither well.
Lezen →The Rise of Data SRE: Reliability Engineering for Data Platforms
Your data pipelines run in production. But nobody treats them like production systems. That's about to change.
Lezen →Observability Turned Our Senior Engineers Back Into Builders
Six months ago our senior engineers were firefighters. Now they're builders again. The change wasn't a reorg. It was observability.
Lezen →The Data Maturity Assessment You Can Do in 30 Minutes
Most maturity assessments take six weeks and a consulting firm. This one takes 30 minutes and a whiteboard.
Lezen →The Data Quality Crisis: 67% of Executives Don't Trust Their Analytics
Executives stopped using the dashboards. They didn't trust the data. Here's how we rebuilt trust in 10 weeks.
Lezen →Wardley Mapping Your Data Stack (Build, Buy, or Outsource?)
Your custom Airflow setup is not a competitive advantage. Your customer analytics model might be.
Lezen →The Incremental Migration Strategy (Strangler Fig Pattern)
You don't migrate a data platform in one go. You grow the new one around the old one.
Lezen →Data Observability + Data Catalog: The Convergence
Your data team switches between four tools during an incident. That's about to change.
Lezen →The Data Contract That Saved a Product Launch
The data contract didn't save the launch. It saved the three days of firefighting that would have followed.
Lezen →The RACI Nobody Wants to Fill In (And Why That's the Problem)
Everyone agrees on "data ownership." Nobody agrees on who actually owns what.
Lezen →The Metadata Moment: When 'Where Is This Data?' Costs You Two Engineers
Two full-time equivalents on your data team do nothing but answer questions all day.
Lezen →The Cloud Cost Optimization Sprint: 45% Reduction in 8 Weeks
This company was burning six figures a year on cloud data - we cut it by 45% in 8 weeks.
Lezen →Data Lineage: From 'Nice to Have' to 'Must Have
Without data lineage, every schema change is a game of "what did we just break."
Lezen →The Data Product Roadmap Template (3 Horizons)
Your data roadmap is a wishlist - here's the 3-horizon framework that turns it into strategy.
Lezen →2026 Data Hiring: From 'Find Unicorns' to 'Build Balanced Teams
The unicorn data engineer doesn't exist - but the balanced data team does.
Lezen →The "Just Use Excel" Moment (And Why It Happened)
When the CFO opens Excel instead of your dashboard, your data team has already lost.
Lezen →Build, Buy, or Partner? The Question Most Data Teams Answer Wrong
Your engineers want to build it, your CFO wants to buy it - here's the framework that settles it in 30 minutes.
Lezen →The 2x2 That Kills 80% of Data Initiative Debates
The 2x2 matrix isn't new - but most data teams still score "value" completely wrong.
Lezen →The Fractional Engagement - 2 Days Per Week, EUR120K Impact
A client budgeted for a full-time data architect they couldn't find, so we tried something different.
Lezen →Data Governance - The Spectrum from Anarchy to Bureaucracy
Your data governance is either too loose to trust or too tight to ship.
Lezen →The Alerting Hierarchy (Critical, Warning, Info)
If every alert is critical, none of them are.
Lezen →The Real-Time Data Paradox - Everyone Wants It, Few Need It
90% of "we need real-time" conversations end with a batch job running at midnight.
Lezen →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.
Lezen →The Data Strategy One-Pager (What Execs Actually Need)
The best data strategy I've seen fit on a single page.
Lezen →What the Books Got Wrong About Data
The DevOps playbook assumes you can roll back - data doesn't work that way.
Lezen →The Data Contracts Rollout - From Chaos to 60% Coverage in 90 Days
Data contracts sound great in theory. Here's what it actually looks like to implement them - week by week, with the parts that almost …
Lezen →The Medallion Architecture Backlash
Bronze, Silver, Gold. Three layers that make sense on a slide and fall apart the moment someone asks "where does this transformation …
Lezen →The Tiered Storage Strategy (Hot, Warm, Cold)
Hot, warm, cold. Three tiers, one policy, and suddenly your storage bill makes sense.
Lezen →The Feedback Loop - Why Data Incidents Keep Recurring
Your data team hides problems because they'll get blamed for them. The Unicorn Project calls this the downward spiral. Here's how to break …
Lezen →The Migration That Didn't Solve Anything
The most expensive way to avoid fixing your organizational problems: migrate to a new data platform.
Lezen →The Data Incident Response Playbook (MTTR Edition)
When your data breaks, how long until someone notices? If the answer is "when the CFO calls," you don't have an incident response process.
Lezen →60% of Your Cloud Spend Is Waste (Here's Where)
Your data platform is burning money in three places right now. You're probably only looking at one.
Lezen →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.
Lezen →Brent Is Your Senior Data Engineer
Every data team has a Brent. The one person who knows everything. The one person the org can't afford to lose. The one person who's about to …
Lezen →The Self-Service Analytics Maturity Ladder
"Self-service analytics" at most companies means "we gave everyone PowerBI access and hoped for the best."
Lezen →The Death of the Full-Stack Data Engineer
Stop hiring full-stack data engineers. They don't exist, and pretending they do is burning your team out.
Lezen →The Dashboard Nobody Uses (EUR60K Lesson)
Three months of development. EUR60K in cost. Zero daily users. The most expensive screensaver I've ever seen.
Lezen →The Data Lineage Maturity Model (4 Stages)
You can't fix what you can't trace. Here's the 4-stage lineage maturity model.
Lezen →The Deployment Pipeline Concept Applied to Data Products
Your data team deploys to production the same way software teams did in 2008. Manually, nervously, with a 1000-step runbook nobody trusts.
Lezen →The Series B Rescue - Making Data Investor-Ready in 10 Weeks
Due diligence will find your data problems before you do. One company found out the hard way.
Lezen →CALMS for Data Organizations
The DevOps Handbook has a framework called CALMS. Most data teams only do the A. Here's what they're missing.
Lezen →Horizontal vs Vertical Scaling
Vertical scaling is adding RAM. Horizontal scaling is adding servers. One has a ceiling. One doesn't.
Lezen →Data Platform Teams Are Becoming Product Teams
Nobody adopts a pipeline. They adopt a product. That's what most data teams still don't get.
Lezen →The Compliance Incident That Cost a Giant Fine (And One Email)
They had microservices, a data lake, and Grafana dashboards for everything. They didn't have an answer to "where does this customer's data …
Lezen →The Data Platform Scaling Checklist (When to Evolve)
Scaling too late costs you 6 months. Scaling too early costs you 18.
Lezen →Parts Unlimited" Is Your Data Platform
The Phoenix Project described a company drowning in unplanned work. Gene Kim called it Parts Unlimited. You might recognize the patterns.
Lezen →Communication Overhead Kills Data Team Velocity
You doubled your data team. Delivery got worse. Fred Brooks explained why in 1975.
Lezen →From EUR80K/Month Cloud Bill to EUR45K - The Optimization Sprint
This company cut their cloud data bill from EUR80K to EUR45K in 6 weeks. No functionality lost.
Lezen →Analytics Lead Time - The Time to Insight Metric
Your data team takes 2 weeks to answer a business question. That decision's already been made.
Lezen →The Five Ideals Applied to Data Teams
Gene Kim wrote The Unicorn Project about a developer trapped in bureaucracy. Data engineers live that story every day.
Lezen →The Shadow IT Problem - When Fast Beats Right
Shadow IT doesn't start with rogue employees. It starts when the gap between 'I need this' and 'we can deliver this' gets too wide.
Lezen →The 6 Dimensions of Data Quality
Data quality has 6 dimensions. Most teams only measure 2. Here's what you're missing.
Lezen →The Three Ways Applied to Data Pipelines
Your data team ships pipelines fast. That's the First Way. They're ignoring the other two.
Lezen →Platform Scaling Without Hiring
Five times the data. Same number of people. No new hires. The only way through? Rethink the architecture.
Lezen →Data Observability Practical Start
Data observability sounds expensive and complex. Here's how to start in one afternoon.
Lezen →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 …
Lezen →Incremental Processing Pattern
Your nightly job reprocesses 10TB. Only 50GB changed. You're burning money and adding risk.
Lezen →Why Companies Hire a Data Architect Consultant (And When You Shouldn't)
You don't always need a data architect consultant. Here's how to know if you do, what to expect, and how to avoid hiring the wrong person.
Lezen →Waiting for LLMs vs Waiting for Compilation
We spent a decade optimizing compilation times. Now we're staring at an LLM spinner doing the exact same thing.
Lezen →Cost of Tribal Knowledge
Nobody sets out to hoard knowledge.
Lezen →Data Product Operating Model
You wouldn't ship a software product without an owner, a roadmap, or a release process. Why do you treat your data differently?
Lezen →Technical Debt Cost Calculation
Slow pipelines are a symptom. The disease is poor architectural decisions nobody revisited.
Lezen →The Second-System Effect in Data Platforms
Your second data platform will be overengineered. Fred Brooks predicted this in 1975.
Lezen →When to Actually Implement a Modern Data Stack (SME Edition)
You're paying EUR3K/month for a cloud warehouse. Your Postgres could've handled it.
Lezen →Cost-Aware Data Engineering - FinOps for Data
Your data team doesn't know what their pipelines cost. That's the first problem.
Lezen →AI Worry Gap - Engineers vs Executives
Executives see AI as opportunity. Engineers see it as threat. Neither is talking to the other about it.
Lezen →The Alex Problem - Hero Dependency
Alex knows everything about your data platform. When Alex leaves, you're in trouble.
Lezen →T-Shaped Monitoring Model
Monitoring all your data equally is why you're drowning in alerts. Here's the smarter approach.
Lezen →Managers Overseeing 3X More People Than 2017
The average data team manager is overseeing nearly 3X more people than in 2017. Something has to give.
Lezen →Platform Rescue Engagement
Three months ago, this data platform had 15 incidents per week. Today: 3.
Lezen →Firefighters vs Pyromaniacs
Your best firefighter might be your worst pyromaniac.
Lezen →Hybrid Governance Implementation
The 3-part governance model that actually gets adopted.
Lezen →Hybrid Data Governance
Your governance is either a bottleneck or ignored. The data says 80% of companies can't find the middle ground.
Lezen →Metadata Management ROI
Engineers losing 10-20% of their time to repetitive questions. Most teams don't even measure it.
Lezen →Data Quality Testing Layers
Testing data quality after transformation is like tasting the dish after it's plated. Too late.
Lezen →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.
Lezen →The €250K Migration That Didn't Need to Happen
The €250K migration wasn't a technology project. It was an expensive way to avoid hard conversations.
Lezen →Building data platforms for technology instead of teams
The data platform nobody asked for is the data platform nobody uses.
Lezen →Event-driven architecture coordination tradeoffs
You adopted EDA to reduce dependencies. You just traded runtime coupling for design-time coupling.
Lezen →Data Architecture vs Data Engineering: What's the Difference?
Architects design the blueprint. Engineers build the system. Hire the wrong one first and you'll hire both twice.
Lezen →mise en place for data teams
Skip your prep and service falls apart. Every chef knows this. Most data teams learn it the hard way.
Lezen →The Alignment Tax: What Misalignment Costs Per Sprint
Your team's velocity isn't slow because they're bad. It's slow because they're building the wrong thing right.
Lezen →The AI Readiness Checklist Nobody Uses
Every company has an AI roadmap. Almost none have passed their own readiness checklist.
Lezen →When You Actually Need a Modern Data Stack
Your spreadsheet chaos isn't a sign you need Snowflake. It's a sign you need clarity on what you're trying to measure.
Lezen →Platform Review: What I Find in Week One
In week one of every platform review, I find the same five problems. Your company probably has at least three.
Lezen →The Reorg That Made Everything Worse
They reorganized the data team three times in two years. Each time, things got worse.
Lezen →What Is Data Strategy for a 50-Person Company?
Your 50-person company doesn't need an enterprise data strategy. You need to answer five questions.
Lezen →How to Prioritize Data Requests in 3 Steps
When everything is "high priority," nothing gets done. Here's how to fix your data request backlog in three steps.
Lezen →AI-Ready Means Data-Ready
Your AI strategy won't save you if your data is a mess. Gartner says 80% of digital organizations risk failure without modern data …
Lezen →Platform Review: 3-Month ROI for a Series B Startup
Every growing startup hits the same three data problems. Not similar. Identical.
Lezen →The Destabilizing Effect of Constant Org Chart Shuffle
Only 23% of reorganizations achieve their objectives. The other 77% just reset the clock.
Lezen →Data Mesh vs Reality - Why Silos Return
You decentralized your data team. Now you have 10 data silos instead of 1.
Lezen →We Shipped Fast. We Paid Slowly
The problem isn't shipping fast. It's not being able to fix fast.
Lezen →The Data Trust Paradox - Why 67% Don't Believe
Data trust is asymmetric. You lose it fast. You earn it slowly.
Lezen →Technical Debt Is Like Credit Card Interest - It Compounds
Think of technical debt like a credit card. Your data platform maxed it out years ago. Your engineers? They're stuck paying the minimum …
Lezen →Data Consultancy vs Data Products - The Expensive Confusion
A data team that only consults will never scale. A data team that only builds will never be used.
Lezen →What Is a Data Architect?
Data engineers solve problems. Data architects help decide which problems are worth solving.
Lezen →Architecture Advisory: The 3 Questions I Ask First
In week one of any architecture review, I ask the same 3 questions.
Lezen →Why Your AI Project Failed at the Data Layer
Rule of thumb: AI success is 20% model and 80% data infrastructure.
Lezen →Legacy Modernization: Break or Transform
Some legacy systems should be replaced. Most should just be wrapped.
Lezen →Hero Dependency: Why Your Best Work Makes You Replaceable
The best proof of your value is a team that doesn't need you anymore.
Lezen →Shadow Data Costs Your Team 8-9 Hours/Week
Your team can lose 8-9 hours/week to shadow data. And they actually don't call it that.
Lezen →GenAI Risks: The Billion-Euro Wake-Up Call
GenAI failures are poised to cost enterprises billions in wasted budget. Many won't be tech failures.
Lezen →Team Alignment Sprint: 3 Outputs Teams Actually Use
A 4-week sprint. 3 outputs. Zero slide decks nobody reads.
Lezen →You're Hiring Data Engineers Wrong
You're hiring data engineers wrong. And your best candidates know it.
Lezen →FinOps Reality Check: 60% Wasted Spend
Up to 60% of your cloud spend can go to waste. And nobody owns the problem.
Lezen →The Genius Developer Anti-Pattern (Reprise)
Your best developer isn't your biggest asset. They're your biggest risk.
Lezen →3 Ways to Escape the 40% Maintenance Trap
Your engineers spend 40% on maintenance. Here's how to get half of that back.
Lezen →The Migration That Took Three Years
We planned a six-month migration. We finished in three years.
Lezen →The Dashboard Nobody Trusted
We built the perfect dashboard. Nobody used it.
Lezen →Why Your Data Team Is Burned Out
The "urgent" request took two hours. The context switch cost four.
Lezen →Mapping Architecture to Outcomes
The CEO doesn't care about your system design. They care about what it enables.
Lezen →Citizen Development Creates Enterprise Debt
The app your business team built in a week will cost IT six months to fix.
Lezen →The Data Platform ROI Nobody Calculates
The CFO asked for the ROI of data. Nobody could answer.
Lezen →The Architecture Conversation CEOs Avoid
The architecture conversation CEOs avoid is the one they need most.
Lezen →When Your Customer Data Lives in 47 Places
Your customer data lives in 47 places. None of them agree.
Lezen →AI Governance - Why 82% Are Scrambling
Your board wants AI. Your teams are building AI. Your governance? Still stuck in 2019.
Lezen →Cloud Cost Shock - $100B in Waste
Global enterprises waste $100 billion annually on cloud. Your share is probably 20-40%.
Lezen →Data Quality Crisis - 77% Admit Failure
Everyone is in data. But only one team gets the blame when it breaks.
Lezen →Data Quality as Organizational Signal
Bad data doesn't come from bad systems. It comes from broken ownership.
Lezen →We Hired a 10x Developer. Then We Lost the Team
We hired a 10x developer. Then we lost the team.
Lezen →Process Debt Is Worse Than Technical Debt
You can refactor code. Try refactoring a six-person approval chain.
Lezen →The Tech Lead's Real Job Isn't Technical
You got promoted for coding. Now your job isn't to code.
Lezen →Refactoring Without Stopping Delivery
Refactoring projects fail. Refactoring routines succeed.
Lezen →Data Contract Pattern
Every Monday, someone's dashboard breaks. Nobody knows why.
Lezen →The Expert Beginner Trap
The expert beginner knows enough to be confident and not enough to know what they're missing.
Lezen →Strategy Debt: When Your Roadmap Has No North Star
A roadmap without a north star is just a to-do list with dates.
Lezen →The Shadow IT Problem Nobody Admits
Shadow IT isn't a governance failure. It's a service failure.
Lezen →AI Won't Fix Your Architecture - It Will Amplify It
Every AI initiative is an architecture stress test.
Lezen →Why Your Lakehouse Became a Swamp
Your lakehouse became a swamp. And it wasn't a technology problem.
Lezen →40% Maintaining, 20% Innovating - The Technical Debt Math Nobody Talks About
Your engineers spend 40% of their time maintaining yesterday's shortcuts. And you're wondering why your AI initiative isn't moving faster.
Lezen →Dear Alex - You're Not the Problem, the System Is
Dear Alex, you're not the problem.
Lezen →The 100k Cloud Migration Mistake
We spent €100k migrating to the cloud. Then we spent €100k migrating back.
Lezen →Red Flags - Symptoms of Poor Architecture
These five symptoms mean your architecture is working against you. And most leaders miss them.
Lezen →From Technical Debt to Technical Drag
Stop calling it technical debt. Debt has a balance you can clear. This is permanent friction.
Lezen →Why More Developers Won't Fix Delivery Problems
You hired ten more developers. Delivery got slower. That's not a paradox, it's physics.
Lezen →The False Economy of Skipping Architecture Reviews
Skipping architecture reviews saves weeks. Fixing the consequences costs months.
Lezen →The Genius Developer Anti-Pattern
Your best developer might be your biggest risk.
Lezen →Hidden Cost Multiplier: Technical Debt Compounds Faster Than Financial Debt
Technical debt compounds faster than financial debt. And nobody tracks the interest rate.
Lezen →Dependencies - Hidden Drags on Progress
Your roadmap isn't delayed by complexity. It's delayed because of coupling.
Lezen →The Velocity Paradox
Every shortcut you take to move faster becomes a wall you hit at speed.
Lezen →Why Your Best Engineers Leave - It's the Architecture
Retention isn't an HR problem when your technical debt compounds faster than careers grow.
Lezen →Platform as Product - Enabling Team Autonomy
Your platform team believes they're building infrastructure, but they're actually running a product company with just one customer segment: …
Lezen →The Expensive Lie - We'll Refactor Later
"We'll refactor later" isn't a plan. It's a bet that future you will have more time, budget, and political capital than present you.
Lezen →Event-Driven Architecture - Eliminating Integration Pain
Every point-to-point integration you create is a gamble that the future will resemble today. Event-driven architecture recognizes that it …
Lezen →Connecting Architecture to Business Goals
Architecture without business context is just expensive documentation.
Lezen →Why MVP Thinking Creates Permanent Debt
You shipped the MVP. The business loved it. Three years later, you're still paying interest.
Lezen →How Poor Architecture Turns Seniors Into Firefighters
If your top talent spends more time debugging than designing, it's not a talent problem; it's a debt problem.
Lezen →Speed-only cultures build hidden debt, not velocity
Speed-only cultures build hidden debt, not velocity.
Lezen →The architecture decisions you can't reverse
The architecture decisions you can't reverse
Lezen →Why hiring more developers won't fix your delivery proble...
Why hiring more developers won't fix your delivery problems A lack of hands doesn't cause slow delivery. It's a lack of coherence that …
Lezen →Most integration pain is self-inflicted
Most integration pain is self-inflicted.
Lezen →Most teams view architecture as code
Most teams view architecture as code. Boxes. Lines. Repos. Services.
Lezen →Dependencies are the hidden drag for your delivery speed
Dependencies are the hidden drag for your delivery speed.
Lezen →Communication debt becomes technical debt
Communication debt becomes technical debt.
Lezen →Tech solutions don't fix human problems - they magnify them
Tech solutions don't fix human problems - they magnify them.
Lezen →Team structure shapes your delivery speed more than tools
Team structure shapes your delivery speed more than tools.
Lezen →Is your architecture ready for AI-driven threats
Is your architecture ready for AI-driven threats?
Lezen →You cannot outrun poor architecture by accelerating delivery
You cannot outrun poor architecture by accelerating delivery.
Lezen →If you organise by technology rather than by outcome, you...
If you organise by technology rather than by outcome, you'll deliver patchwork.
Lezen →Effective governance is built in, not bolted on
Effective governance is built in, not bolted on.
Lezen →You don't scale by sprinting harder
You don't scale by sprinting harder. You scale by eliminating friction. Everyone desires velocity. Few invest in what truly sustains it. …
Lezen →Most people think constraints limit creativity
Most people think constraints limit creativity.
Lezen →Clarity doesn't remove complexity;
Clarity doesn't remove complexity; It organizes it into direction.
Lezen →You can't design great systems without designing how deci...
You can't design great systems without designing how decisions are made
Lezen →"Faster" alone won't save anyone
"Faster" alone won't save anyone
Lezen →Data pipeline reliability is a good proxy for how much ev...
Data pipeline reliability is a good proxy for how much everybody cares.
Lezen →Silver bullets sell because uncertainty is uncomfortable
Silver bullets sell because uncertainty is uncomfortable.
Lezen →If you can't describe the problem, AI can't solve it
If you can't describe the problem, AI can't solve it.
Lezen →Decision debt keeps you running in circles
Decision debt keeps you running in circles
Lezen →Specialists make things work
Specialists make things work. Generalists make things connect.
Lezen →Every data flow tells a story.
Every data flow tells a story. Not about systems. About people.
Lezen →Your architecture mirrors your communication patterns.
Your architecture mirrors your communication patterns.
Lezen →If your data product doesn't start with 'why,' it will en...
If your data product doesn't start with 'why,' it will end with 'disaster.'
Lezen →If everyone agrees instantly, nobody's being honest.
If everyone agrees instantly, nobody's being honest.
Lezen →AI cannot innovate if all you provide it with is precedent.
AI cannot innovate if all you provide it with is precedent.
Lezen →Your real integration layer isn't code
Your real integration layer isn't code. It's people.
Lezen →Clarity is cheap. Confusion costs millions.
Clarity is cheap. Confusion costs millions.
Lezen →Do you actually know what a "data product" is?
Do you actually know what a "data product" is?
Lezen →Buy vs Build isn't an IT decision.
Buy vs Build isn't an IT decision. It's a strategic tradeoff.
Lezen →If all you have is a hammer, everything looks like a nail.
If all you have is a hammer, everything looks like a nail. In data, the hammer could be the vendor you've already to committed to.
Lezen →Your most challenging problems aren't technical; they're ...
Your most challenging problems aren't technical; they're social. Stop calling them soft skills.
Lezen →Most teams can't even list the AI tools they've deployed.
Most teams can't even list the AI tools they've deployed. That's the problem.
Lezen →Hype doesn't deliver ROI. Solid architecture does.
Hype doesn't deliver ROI. Solid architecture does. The AI hype cycle is eating budgets - most won't see returns.
Lezen →Big bang modernization creates new debt faster than it clear
Big bang modernization creates new debt faster than it clears the old. Tech is only the visible part of legacy. The real weight is …
Lezen →Friction between DataOps and SysOps isn't about tools.
Friction between DataOps and SysOps isn't about tools. It's about ownership.
Lezen →Slideware isn't strategy.
Slideware isn't strategy. If it can't survive constraints, it's theatre.
Lezen →Your architecture is how you deliver.
Your architecture is how you deliver. Slow isn't about the team. It's about the design.
Lezen →AI doesn't kill architecture. Bad architecture kills AI
AI doesn't kill architecture. Bad architecture kills AI Most teams are deploying AI on loose ground.
Lezen →Most Data Strategies die in a slide deck.
Most Data Strategies die in a slide deck. If yours needs a PDF, it's already too slow.
Lezen →Legacy doesn't explode. It decays.
Legacy doesn't explode. It decays. By the time it's urgent, you're already behind.
Lezen →Deskundige blik op jouw data-architectuur?
Geen verkooppraatje. Een eerlijk gesprek over of ik kan helpen, en hoe dat er dan zou uitzien.