Topic
Architecture & Modeling
Technical patterns, tradeoffs, and scars from real data systems.
If Security Depends on Who Built the Dashboard, You Do Not Have a Security Model
Analytics security often starts with a reasonable shortcut. Restrict a folder, add a filter, configure a workbook, and ship. The problem appears later, when the same rules have to survive new dashboards, new users, new teams, and people who were not there when the original decisions were made.
A Metric Is Not Defined Until the Exceptions Are
Teams can agree on a metric in five minutes and spend months discovering what they actually agreed to. The formula is usually the easy part. Timing, incomplete work, corrections, customer configuration, missing data, and competing definitions are where a metric becomes real.
The Fastest Way to Ship Technical Debt Is to Call It a Shortcut
Most technical debt is not created by poor engineering. It is created by reasonable decisions made under delivery pressure that are never revisited. The shortcut is rarely the problem. Treating it as the new architecture is.
The Most Expensive Words in Analytics Are 'Just Add a Field'
Adding one field to a report sounds harmless. In reality it can change grain, security, ownership, testing, performance, documentation, and long-term maintenance. The request is rarely the expensive part. Everything underneath it is.
The Hidden Cost of Over-Modeled Analytics
When every question requires a perfect model, the business waits on architecture instead of getting answers.