Data Producer Enablement and Developer Experience for Data Teams
•
Andrew Jones
Andrew Jones on data contracts, producer tooling and why access alone never solved self-service.
Access to company data is still one of the hardest problems a data team faces, and it does not go away once a company opens up raw data to every team. On this episode of the Data Playbook podcast, Kris Peeters, CEO of Dataminded, talks with Andrew Jones, staff data engineer at LocalStack, about what a data platform needs on top of access: data contracts, tooling that meets producer teams where they already work, and guardrails built into the platform rather than enforced by review.
Jones walks through a platform that failed, built around a serialization format his producer teams did not know or like, and the one that replaced it, built around a format they already used every day. He and Kris also get into where self-service ends for data consumers, why data teams cling to being the bottleneck, and why the assumptions behind medallion architecture are worth revisiting now that copying raw data out of a source system is no longer the only option. The conversation closes on data semantics for AI agents: what happens when an agent asks a data question with the wrong context, and where that context belongs so it stops happening.
Latest
Data Producer Enablement and Developer Experience for Data Teams
Andrew Jones on data contracts, producer tooling and why access alone never solved self-service.
Data Contracts and Data Products: What AI Agents Need to Access Enterprise Data
AI agents need their own access rules. Simon Harrer, Entropy Data, on data contracts, data products and purpose-based access control.
Data Mesh After the Hype: Why Data Products Matter More Than Ever
Why Data Products outlasted Data Mesh, where Data Contracts fit, and how AI is changing modern data architecture.
