↓Skip to main content

Why are you expected to accept unrefined data?

·1 min
Data Engineering Data

Following on from yesterdays mail, when I talked about the language of data engineering, it’s worth asking why you’re asked to accept “unrefined”, poor quality data.

Is it because your organisation is happy with the costs that incurs on you and your team? If so, do they know that cost?

Is it because they don’t value what you’re working on? If so, is it valuable enough?

Is it just the way it’s always been? If so, what’s stopping you from challenging that?

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? 😅

Enter your best email here:

    (Don’t worry—I hate spam, too, and I’ll NEVER share your email address with anyone!)
    Andrew Jones
    Author
    Andrew Jones
    I build data platforms that reduce risk and drive revenue.
    ← → The language of data engineering The circuit breaker pattern → ←