texlytics

Loading

Publications

Publications

29/07/ 2026
Article IV — Our Beliefs

The texlytics Charter Series Every organization operates according to a set of beliefs. Some are written down. Most are not. At texlytics, we believe those beliefs should be intentional, because they influence every recommendation we make and every solution we design. Our beliefs are simple. Organizations usually possess more knowledge than they realize. Understanding creates better decisions. Complexity is a cost. Technology exists to serve people. Curiosity is a competitive advantage. Learning is a professional responsibility. Trust is earned. Knowledge should compound. These beliefs influence every engagement, every…

Read more
24/07/ 2026
The Dedupe Key That Doesn’t Drift

This article was originally published on LinkedIn and is archived here on texlytics.com. There is a reflex every data engineer has when they need to deduplicate rows: hash the row, compare the hashes, keep one of each. It is fast, it is simple, and on a well-behaved source it is correct. I reached for it without thinking when I built the ingestion for one of our CMiC AP voucher endpoints. It was the wrong call, and the way it failed is worth writing down, because the lesson holds…

Read more
22/07/ 2026
Article III – Vision

The texlytics Charter Series Every company has goals. Those things matter. But they’re not a vision. A vision should answer a much bigger question: What are we trying to build that will outlast us? For texlytics, our vision has never been to become known for a particular technology. Technology changes. Platforms evolve. Today’s innovations become tomorrow’s legacy systems. If we define ourselves by the tools we use, we’ll spend our future chasing the next trend. Instead, we’re building something that we hope will endure. To build an enduring…

Read more
17/07/ 2026
The 95-Minute Notebook

This article was originally published on LinkedIn and is archived here on texlytics.com. The symptom Our Bronze ingestion notebook on Microsoft Fabric had a runtime problem. The notebook pulls incremental changes from CMiC’s REST APIs into a lakehouse on a 15-minute cadence — dozens of endpoints, all driven from a single control table. The kind of thing that should finish in a few minutes. It was taking 95. Here’s what made it interesting: the Python wasn’t slow. The API calls came back quickly. The filtering and dedupe logic…

Read more
Charter Article 2 - Mission Charter Article 2 - Mission
15/07/ 2026
Article II – Mission

The texlytics Charter Series Technology isn’t our mission. Understanding is. At texlytics, we don’t start with software. We start by understanding the business. Every organization has its own goals, processes, challenges, and people. Technology should reflect those differences, not force businesses into someone else’s way of working. That’s why we ask questions before we recommend solutions. The technology is never the destination. It’s simply the vehicle. That philosophy is what led to the creation of Origo. Not because the world needed another platform, but because we saw too…

Read more
10/07/ 2026
The Most Important Table in My Microsoft Fabric Environment

This article was originally published on LinkedIn and is archived here on texlytics.com. Most data engineers love talking about pipelines. Others love talking about notebooks, Spark, semantic models, or dashboards. But after building a near-real-time Microsoft Fabric integration framework that ingests dozens of CMiC endpoints every fifteen minutes, I’ve come to a different conclusion: The most important object in my entire environment isn’t a pipeline. It’s a table. Not a fact table.Not a dimension table.A control table. What started as a simple metadata repository evolved into the operational…

Read more
cherter series - article 1 cherter series - article 1
09/07/ 2026
Article I – Purpose

The texlytics Charter Series The purpose of texlytics is to help organizations better understand themselves. We transform complexity into clarity by connecting information, people, systems, and intelligence so better decisions become possible. Those two sentences define everything we build. Businesses rarely struggle because they lack information. They struggle because information exists in too many places, disconnected from the context needed to make confident decisions. Information is often scattered across: Our job isn’t simply to connect systems. Our job is to connect understanding. When understanding improves: This philosophy shapes…

Read more