Daily data contracts tips

When it comes to defining SLOs, I’m aiming for good enough.

A great analogy for a data contract is an API.

In 2012 the authors of the Go programming language published a document that made clear their intention for backwards compatibility:

How many times do you find something that is not working as it should be, and after digging around you find it has no clear owner?

It’s a misconception that data contracts are just for tabular data.

What’s the right organisational structure for a successful data contracts implementation?

A question I received on a LinkedIn post about change management with data contracts asked (lightly edited for clarity):

Data governance initiatives often deliver a set of rules for people to follow when they create and manage data.

When it comes to data contracts I’m always talking about well structured data.

I was asked on LinkedIn how I might approach data contracts with dbt.