Insights & ideas.
Practical writing on websites, software, data, and AI from the Lumex team. Aimed at business owners, not developers.
Practical writing on websites, software, data, and AI from the Lumex team. Aimed at business owners, not developers.
5 posts
The UI had a dimension-fact data problem. Multiple dimension collections, one dense fact table, filters that needed to cross all of them reactively. The naive approach was O(n) inside O(n). So we built indexes. Then we had to justify them.
Most businesses think of a report as a deliverable. Something you request when you need a specific answer. That model only lets you ask questions you already know to ask. Analytics isn't a report. It's a capability.
The hard part of data analytics was solved long ago. What hasn't been solved is the translation layer between those tools and your specific business. That gap isn't a technology problem - it's a plumbing problem.
The developers who actually move fast aren't better typists - they're better translators. Between messy business reality and clean system logic. The code is just what it looks like when you're done.
Tell us what you're working on. We respond within one business day.