
Sign up to save your podcasts
Or


When it comes to data, there are data consumers (analysts, builders and users of data products, and various other business stakeholders) and data producers (software engineers and various adjacent roles and systems). It's all too common for data producers to "break" the data as they add new features and functionality to systems as they focus on the operational processes the system supports and not the data that those processes spawn. How can this be avoided? One approach is to implement "data contracts." What that actually means… is the subject of this episode, which Shane Murray from Monte Carlo joined us to discuss! For complete show notes, including links to items mentioned in this episode and a transcript of the show, visit the show page.
By Michael Helbling, Moe Kiss, Tim Wilson, Val Kroll, and Julie Hoyer4.8
168168 ratings
When it comes to data, there are data consumers (analysts, builders and users of data products, and various other business stakeholders) and data producers (software engineers and various adjacent roles and systems). It's all too common for data producers to "break" the data as they add new features and functionality to systems as they focus on the operational processes the system supports and not the data that those processes spawn. How can this be avoided? One approach is to implement "data contracts." What that actually means… is the subject of this episode, which Shane Murray from Monte Carlo joined us to discuss! For complete show notes, including links to items mentioned in this episode and a transcript of the show, visit the show page.

4,137 Listeners

406 Listeners

583 Listeners

145 Listeners

301 Listeners

608 Listeners

345 Listeners

3,976 Listeners

1,425 Listeners

208 Listeners

314 Listeners

99 Listeners

226 Listeners

682 Listeners

170 Listeners