Charles Mulwa

 By Charles Mulwa Every few years, someone declares the data warehouse dead. I heard it when Hadoop showed up and everyone insisted schema-on-read would make schema-on-write obsolete. I heard it again when the data lake became the buzzword of the decade. Now it's the lakehouse, real-time streaming architectures, and a wave of AI-native platforms all taking their turn at the same obituary. And yet, twenty-plus years into a career built largely around data warehousing, database administration, and data strategy, I keep walking into organizations - across distribution, healthcare, manufacturing, financial services, you name it - where the traditional data warehouse isn't just alive. It's still the thing doing the actual work. I want to be careful here, because I'm not writing this as a defense of stagnation. The tools around the warehouse have changed enormously, and for the better. But the core idea — a governed, modeled, trustworthy home for your organization's n...

By Charles Mulwa For more than twenty years, I've had the privilege of helping organizations solve one of their most valuable - and often most challenging- business assets: data. When I started my career, success was measured by keeping SQL Server databases online, optimizing queries, building data warehouses, and delivering reliable reports. Today, those skills remain essential, but the data landscape has evolved dramatically. Organizations are no longer asking, "Can we build a report?" They're asking: How do we prepare for Artificial Intelligence? Should we choose Databricks or Microsoft Fabric? Is Snowflake the right cloud data platform? How do we govern data across Azure, AWS, and Google Cloud? Can Microsoft Purview help us understand our data estate? How do we build trusted data products that business users can consume confidently? The conversation has shifted from managing databases to managing data ecosystems. After more than two decades in enterprise data arch...

  I n modern software engineering, "technical debt" is a term thrown around in almost every sprint planning meeting, architecture review, and product roadmap alignment. Teams frequently pause to discuss refactoring messy application code, upgrading outdated JavaScript frameworks, or rewriting monolithic microservices to keep the codebase clean. Yet, there is a massive, gaping blind spot in most corporate technical debt strategies. While application developers command the lion's share of attention and funding to clean up their code, the underlying data layer is routinely ignored. It is treated like a mysterious black box—a utility that is expected to work flawlessly, endlessly, and without maintenance, until it suddenly breaks. This is the reality of Database Technical Debt . It is the silent killer of enterprise systems. Unlike application debt, which usually manifests as clunky user interfaces or slow feature deployment, database technical debt directly compromises the c...

Artificial Intelligence is no longer a futuristic concept whispered about in research labs. It is actively embedded in modern analytics platforms, driving automated business applications, and shaping high-stakes executive decision-making. From predictive forecasting to generative workflows, enterprise leadership is feeling the immense pressure to deploy AI initiatives rapidly. Yet, many organizations rush headfirst into the AI race only to stumble over a painful, costly truth: AI is only ever as good as the data feeding it. Across enterprise environments, a recurring pattern plays out. Executive leaders demand immediate, AI-driven insights, predictive models, and automated efficiency. However, the underlying data foundations are fractured, unorganized, and entirely unready to support the weight of these advanced cognitive workloads. If you feed an advanced algorithm fragmented information, it will simply produce flawed conclusions at a much faster rate. Why Data Management Matters Mo...