Eventual Consistency | Your Reality Check on What's Actually Happening in Data

The data leader's fortnightly reality check. No hype. No hot takes for engagement. Just honest conversation about what's actually happening in data and what it means for the work you're doing. Every two weeks, we pick the stories dominating your feed, the acquisitions, product launches, frameworks, and controversies and discuss them the way you would with your team: critically, honestly, and with one question in mind: "What does this actually mean for my world?" We're not here to sell you courses, predict the future, or tell you the sky is falling. We're here to cut through vendor claims that everything is "revolutionising" something, LinkedIn posts oscillating between doom and humble-brags, and tech journalism that treats every product launch like it's world-changing. This is for VPs of Data, Analytics Directors, Data Engineering Managers, and senior practitioners who need to stay informed but don't have time to wade through whitepapers and noise. People making

Eventual Consistency | Your Reality Check on What's Actually Happening in Data is a news podcast hosted by CorrDyn, with 30 episodes on record and a Required Pod Score of 80.

CorrDyn hosts Eventual Consistency | Your Reality Check on What's Actually Happening in Data, a news show with 30 episodes published.

Our AI reads these to draft pitches. Use them as grounding for a pitch that cites a real guest and a specific topic.

• 

  Episode #17

  Why Nvidia's $13B Deal for Hugging Face Was Never About Revenue

  Sep 23, 202641 minS2

  Nvidia just paid almost $13 billion for a company with $150 million in revenue. That math only makes sense once you stop thinking about revenue. Every big AI acquisition headline feels urgent, but figuring out whether it changes anything about your data stack or your vendor risk is another matter entirely. Ross Katz, principal and data science lead at CorrDyn, works with data teams day to day on exactly the kind of infrastructure decisions this deal touches. He walks through the acquisition using the same framework he'd use with a client evaluating any major shift in the data industry. You'll walk away with a clear read on why Nvidia bought Hugging Face, what "aggregating demand" means in practice, and whether enterprises leaning on Hugging Face need to change anything right now. Ross also flags the one thing worth putting on your 3 to 5 year roadmap regardless of how this deal plays out. This episode covers Nvidia's smile curve strategy, the difference between supply aggregation and demand aggregation, Hugging Face's security breach and what Nvidia's involvement means for trust in the platform, and the regulatory review timeline ahead. It's built for data and analytics leaders who need a clear-eyed read on AI industry M&A, not hot takes. Key Takeaways - The $13 billion price tag is a rounding error for Nvidia, and that's the point: this was never a revenue play, it's about owning one of AI's key demand aggregation points. - Nvidia's real nightmare isn't losing this deal, it's a future where the model layer captures all the value and hardware becomes a commodity. Ross explains why that reshapes every move Jensen Huang makes. - If your team treats Hugging Face as load-bearing infrastructure, Ross has a specific take on what should change now versus what belongs on a 3 to 5 year roadmap instead. - Nvidia has a track record of vertical integration ambitions, and Ross lays out the exact scenario that would push them to acquire a frontier model company outright. Chapter Markers 00:00 Nvidia's $13 billion Hugging Face acquisition 00:58 What is Nvidia actually buying here 04:36 Aggregating supply versus aggregating demand 07:09 Hugging Face as AI's demand aggregation hub 11:44 Nvidia's nightmare scenario: hardware commoditization 14:10 Was Nvidia the only strategic buyer 20:27 Should enterprises rethink Hugging Face dependency 23:46 Regulatory review timeline and what to watch 24:58 Could Nvidia acquire a frontier model company 30:38 Nvidia's lead over AMD, Qualcomm, and Broadcom 33:23 Hugging Face's security breach and trust concerns 35:24 What We're Watching: data warehouse benchmarking findings Connect With the Show Follow Ross Katz on LinkedIn: https://www.linkedin.com/in/b-ross-katz/ CorrDyn on LinkedIn: https://www.linkedin.com/company/corrdyn/ Website: corrdyn.com Do you think Nvidia's Hugging Face acquisition changes anything about how you evaluate vendor risk in your AI stack? Tell us in the comments, we read every one. If you want to talk about your data challenges, or you think we got something wrong, find us at corrdyn.com. #EventualConsistency #DataIndustry #Nvidia #AIInfrastructure #DataStrategy

  ListenShow Notes
• 

  Episode #16

  How to Know When Open-Weight AI Models Actually Save You Money

  Sep 9, 202640 minS2

  AT&T runs 45 billion AI tokens a day, and open-weight models already handle a quarter of that load. If your business is burning through a frontier-model bill without knowing which tasks actually need frontier intelligence, you're leaving cash on the table every single day. Ross Katz, Principal and Data Science Lead at CorrDyn, works with data teams on exactly this problem: deciding what to build, what to buy, and what to route. He breaks down a Wall Street Journal piece on AT&T's shift to open-weight models and open-weight AI, and tells you where that logic does and doesn't apply to a normal-sized company. Listen and you'll walk away with a practical way to decide when open-weight models are worth the engineering cost, when routing beats self-hosting, and when Chinese-origin models are a risk versus just a headline. Ross puts a number on it: if the use case isn't worth more than a million dollars a year, don't bother self-hosting. Ross and Jason get into the real difference between open-source and open-weight models, when a routing layer beats hosting your own infrastructure, and why data exfiltration (not hidden backdoors) is the actual risk with Chinese models. They also cover build-cost estimates for self-hosting, and close with a candid take on the AI bubble debate. This one's for data leaders weighing their AI spend, not for anyone just using ChatGPT subscriptions day to day. ## Key Takeaways - AT&T's chief data and AI officer expects open models to handle up to 80% of their AI workload within a few years, but Ross explains why that math doesn't automatically transfer to a smaller company. - Self-hosting an open-weight model isn't just a GPU cost. Ross puts a real number on the engineering talent required, and where the break-even point actually sits. - The Chinese-model security story isn't what most headlines suggest. Ross separates the genuine risk (data exfiltration via APIs) from the one that hasn't been proven (hidden backdoors in the weights). - There's a specific volume threshold, tied to a proprietary dataset, where a small fine-tuned open-weight model can beat a frontier model outright. Ross names the number of examples it took. ## Chapter Markers 00:00 AT&T's token numbers and the episode setup 01:05 Are open models ready for large companies 02:38 Why routing captures value other companies leave behind 07:00 Open-source versus open-weight, explained 09:54 How AT&T's smart router actually works 12:11 Shared inference versus dedicated deployment 14:43 The real cost of self-hosting a model 17:19 Where open weights clearly win today 21:35 AT&T's use of Chinese models 22:33 Is the security risk real or overblown 27:32 What smaller businesses should actually worry about 30:57 Questions every data leader should be asking now 41:51 What We're Watching: is AI a bubble ## Useful Links & Resources - Wall Street Journal: AT&T's open-model strategy (the article that prompted this episode) - CorrDyn: corrdyn.com ## Connect With the Show - Ross Katz on LinkedIn: https://www.linkedin.com/in/b-ross-katz/ - Ross Katz on X: https://x.com/brosskatz - CorrDyn on LinkedIn: https://www.linkedin.com/company/corrdyn/ Are you already routing workloads between open and closed models, or is your AI stack still one provider, one bill? Tell us how you're thinking about it. If you want to talk about your data challenges, or you think we got something wrong, find us at corrdyn.com. #EventualConsistency #DataIndustry #AIInfrastructure #OpenWeightAI #BuildVsBuy

  ListenShow Notes
• 

  Episode #15

  How to Build a Data Team Ready for AI Agents, Not Just People

  Aug 26, 202647 minS2

  Your data platform used to serve people. Now it has to serve agents too, and that changes what you build and who you hire. Two people ask an AI agent the same question and get two different numbers back, and neither can explain how their agent got there. That's the moment a data leader realises the platform wasn't built for this world. Ross Katz, principal and data science lead at CorrDyn, works with data teams every day as they rebuild their platforms for a world where agents, not dashboards, are the main consumer of data. You'll get a clear framework for what actually changes on a data team when agents become primary consumers, the warning signs that tell you it's time to invest in your data foundation, and a practical way to think through build versus buy versus hire. Ross also makes the case for why judgment, not production, is now the scarce resource on any data team. Ross covers the new org chart split between platform and distribution work for humans and for agents, why judgment has become the bottleneck, and how tacit knowledge gets written into semantic layers and tools like MotherDuck Guides. This is for data and analytics leaders deciding how to structure their teams around agentic AI, not for anyone after a hype pitch on AI replacing analysts. Key Takeaways - The data team's job hasn't changed: curating knowledge and adding context, but who's consuming it has, and that reshapes the platform you need to build. - One specific failure mode is coming for every data team running agents at scale, and it involves two conflicting numbers that nobody can explain. - There are three real reasons to bring in an external team instead of building in-house, and only one of them is about missing skills. - AI should raise your standard for "done", not lower it, but only if you're using it the way Ross argues you should. Chapter Markers 00:00 - Introduction: agents as the new data consumer 00:49 - How the data team's role has evolved with AI 05:11 - Why context now flows to agents, not dashboards 09:43 - Warning signs it's time to invest in your data foundation 16:11 - Build vs buy vs hire: the real decision drivers 21:38 - Designing the org chart for platform and distribution 29:22 - Why judgment is the bottleneck, not production 34:01 - Which data roles disappear, and which get created 36:29 - Turning tacit knowledge into documented context 43:22 - What We're Watching: who AI actually helps 48:09 - Recap and key takeaways Useful Links & Resources - CorrDyn: corrdyn.com - Katie Bauer's platform vs distribution framework, referenced from her work at Hex: https://hex.tech/blog/data-teams-in-ai-era/ - Otis et al. research on AI and Kenyan business owners, discussed in the What We're Watching segment: https://papers.ssrn.com/sol3/papers.cfm?abstract_id=4671369 - MotherDuck Guides, for organisation-level data documentation: https://motherduck.com/docs/category/guides/ - Previous Eventual Consistency episode with Dave Yaffe on AI governance: https://www.corrdyn.com/podcasts/eventual-consistency/ep-27-prefect-dagster-orchestration/ Connect With the Show - Ross Katz on LinkedIn: https://www.linkedin.com/in/b-ross-katz/ - Ross Katz on X: https://x.com/brosskatz - CorrDyn on LinkedIn: https://www.linkedin.com/company/corrdyn/ - Website: corrdyn.com Where does your team stand right now: are you still building platforms purely for human consumers, or have agents already started showing up in your query logs? Tell us what you're seeing. If you want to talk about your data challenges, or you think we got something wrong, find us at corrdyn.com.

  ListenShow Notes
• 

  Episode #12

  The Consulting-Lab Land Grab: What Sits Between a Model and an Outcome

  Jul 9, 202634 minS2

  Every major AI lab has just bought itself a consulting arm. Ross Katz explains why that is not a flex, it is an admission that the model alone does not create value. You have been told to "do something with AI" by year end, and now every systems integrator in the market wants the work. How do you tell a partner doing real engineering from one reselling a model licence with a nice deck on top? Ross Katz is principal and data science lead at CorrDyn, where he works daily with enterprise data teams trying to get real value from AI deployments. He reads these lab-consultancy tie-ups as a practitioner who actually does the integration work, not as someone selling the deal. Ross walks through why OpenAI, Anthropic and the big four consultancies are suddenly partnering, and what each side actually gets from the arrangement. You will come away with a clear framework for the layers of work that sit between signing an AI deal and getting anything useful out of it, plus a simple filter for evaluating any implementation partner pitching you. This episode covers the OpenAI and Anthropic consulting and private equity deals, the six layers between a model and real business value, and where money actually accrues in the AI stack. It is built for data and analytics leaders under pressure to show AI results, not for anyone looking for lab hype or a quick fix. Key Takeaways The labs, consultancies and PE firms should not be natural partners, but each is trading something specific: reach, integration knowledge, or portfolio intelligence. Ross breaks down exactly what each side walks away with. Getting a model into production means working through six layers beyond the model itself, and the one nobody wants to talk about is the hardest. Anthropic's own numbers suggest six dollars of services spend for every dollar of software, which tells you where the real work (and the real value) is sitting right now. Ross gives you three questions to ask any AI consultant before you sign, built around exactly how they claim to deliver value. Chapter Markers 00:00 AI labs buying into consultancies and PE 01:25 Why labs need consultancies at all 09:19 Strategic alliance or forced marriage 11:12 The six layers between deal and deployment 17:11 Where the AI money actually lands 20:13 Are consultancies funding their own disruption 22:48 The 1970s mainframe rollout parallel 26:43 Spotting real engineering vs a reseller 29:09 What We're Watching: AI labs and IPO pricing 31:56 Recap and takeaways Useful Links & Resources Ross Katz on LinkedIn: https://www.linkedin.com/in/b-ross-katz/ Ross Katz on X: https://x.com/brosskatz Previous episode referenced on Snowflake and Databricks context layers CorrDyn: corrdyn.com Connect With the Show CorrDyn on LinkedIn: https://www.linkedin.com/company/corrdyn/ Ross Katz on LinkedIn: https://www.linkedin.com/in/b-ross-katz/ Ross Katz on X: https://x.com/brosskatz Which layer is eating your AI budget right now: the data substrate, the governance, or the process and change nobody budgeted for? Tell us where your own AI rollout is stuck, and whether your consultant could actually answer Ross's three questions. If you want to talk about your data challenges, or you think we got something wrong, find us at corrdyn.com. #EventualConsistency #DataIndustry #AIDisruption #BuildVsBuy #DataInfrastructure

  ListenShow Notes
• 

  Episode #11

  Similar Keynote, Different Platforms: What Snowflake and Databricks Are Really Competing For

  Jun 26, 202643 minS2

  Snowflake and Databricks held their flagship conferences within a fortnight of each other and both independently built their entire keynotes around the same claim: the bottleneck for enterprise AI is not the model, it is the context. When two direct competitors land on identical messaging at the same moment, the right response is to check the working. That's exactly what this episode of Eventual Consistency does. Ross Katz joins Jason Bradwell to separate signal from positioning across both conferences, from Databricks' LDAP and the one copy of data promise, to the ontology race, to what Genie One actually tells us about how mature these agentic platforms really are. The through line is bigger than any single announcement: data gravity is no longer the moat it once was, and both platforms know it. The race now is to become the structured intelligence layer of your business and that changes how platform decisions should be made. The real risk for data leaders right now is not backing the wrong preview feature. It is not experimenting at all. Key topics covered >> Why the "context not model" consensus is real and manufactured at the same time >> What LDAP means for your data architecture >> Why the ontology race matters more than the feature announcements >> How to make a Snowflake vs. Databricks platform decision in 2026 >> What a mature agentic AI system actually looks like in practice About the hosts Ross Katz brings a background in analytics and data strategy, working with companies to cut through the noise and focus on what actually drives business value. With experience spanning industries such as e-commerce, education, biotech, and finance, as well as the evolving landscape of AI-enabled work, he focuses on the intersection of data capabilities and business outcomes. He's particularly interested in how shifts in technology change not just what's possible but also how people think about and use data in their daily work. Jason Bradwell is a seasoned B2B marketing leader, founder of B2B Better and hosts Pipe Dream, where he explores how modern B2B companies can build media and marketing strategies that drive real revenue and audience growth. Connect with us: Sponsor: CorrDyn, a data consultancy Connect with Ross Katz on LinkedIn Connect with Jason Bradwell LinkedIn

  ListenShow Notes

Recent guests on Eventual Consistency | Your Reality Check on What's Actually Happening in Data. Study who booked and why before you pitch.

Based on semantic analysis of episode topics and host coverage, this show is a strong guest fit for executives in:

Industry fit is computed by PitchCentric using vector embeddings of the show's episode catalog.