Skip to main content

Data Engineering

2025


2024


Talking to software engineers

·3 mins

Yesterday I talked to software engineers about data quality.

It went well!

Specifically, it was about the responsibilities they have, as data producers, when they migrate a data contract to a new version.

Moving to interfaces requires a culture change

·2 mins

Responding to yesterdays post on LinkedIn, Anna Bergevin wrote:

I agree and interface makes things less tightly coupled. But in order to change this we’d need a big cultural change at the company to seeing publishing data for secondary use cases as a core function of the job. Part of why data teams go in and get the data vs the other team publishing an API is because it’s the data team’s whole job to make data available and takes minimal effort from the software/system team. If the team is expected to make and maintain an API (including change management) that is a LOT of extra work. […]

Data teams start with accessibility

·2 mins

A new data team, perhaps being created in a business that is evolving from a startup to a scaleup, often focus on accessibility.

When you remove data engineering as a bottleneck

·1 min

When you remove data engineering as a bottleneck:

  • You have more data available
  • You have more data being used
  • You have more value being realised through data

It also benefits those generating and consuming data, who can now:

Writing code is the easy part

·1 min

Writing code. Modelling data. Building transformations.

That’s the easy part.

The hard part is using all of that to deliver meaningful value to your organisation.


Want great, practical advice on implementing data mesh, data products and data contracts?

In my weekly newsletter I share with you an original post and links to what's new and cool in the world of data mesh, data products, and data contracts.

I also include a little pun, because why not? 😅

    Newsletter

    (Don’t worry—I hate spam, too, and I’ll NEVER share your email address with anyone!)