
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
166166 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.

1,857 Listeners

1,083 Listeners

171 Listeners

301 Listeners

146 Listeners

3,984 Listeners

231 Listeners

268 Listeners

211 Listeners

131 Listeners

97 Listeners

209 Listeners

557 Listeners

59 Listeners

95 Listeners