2024
Data engineers typically favour moving quickly over reliability.
If you’re creating data, you’re modelling data.
Computation is the most expensive part of your data stack.
I talk a lot about data quality and how it could be improved, because I strongly believe that with a little bit more discipline we can do a lot better.
An article that has stayed with me since it was published back in 2015 is Dan McKinley’s Choose Boring Technology.
You can’t do self-serve just by providing datasets that you understand, but your users don’t.
What do you want from your data?
I enjoyed this post from Nicole Radziwill, PhD on LinkedIn:
Following on from yesterdays post about measuring for reporting and measuring for action, one data-driven initiative I’m working on is our FinOps program.
Recently I’m finding it useful to split some of the data-driven initiatives I’m working on into two parts: measure for reporting, and measure for action.
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!)