#88 Data Engineering and Data Engineers' Future in Data Mesh - Interview w/ Joe Reis

https://www.patreon.com/datameshradio (Data Mesh Radio Patreon) - get access to interviews well before they are released Episode list and links to all available episode transcripts (most interviews from #32 on) https://docs.google.com/spreadsheets/d/1ZmCIinVgIm0xjIVFpL9jMtCiOlBQ7LbvLmtmb0FKcQc/edit?usp=sharing (here) Provided as a free resource by DataStax https://www.datastax.com/products/datastax-astra?utm_source=DataMeshRadio (AstraDB) Transcript for this episode (https://docs.google.com/document/d/1CrNt8qo72qGtU1dOdz4PMDVMfqeIZOAP9v5dFzpSKcI/edit?usp=sharing (link)) provided by Starburst. See their Data Mesh Summit recordings https://www.starburst.io/learn/events-webinars/datanova-on-demand/?datameshradio (here) and their great data mesh resource center https://www.starburst.io/info/distributed-data-mesh-resource-center/?datameshradio (here) In this episode, Scott interviewed Joe Reis, CEO/Co-Founder of data consultancy Ternary Data, Co-Host of the Monday Morning Data Chat, and author of the upcoming book Fundamentals of Data Engineering. Some key points or takeaways specifically from Joe's point of view (not necessarily those of the podcast): Find quick, high-value wins. Too often people focus on the big wins and those become overly complicated and end up in failure. Most software engineers don't understand data well enough to be data product developers in data mesh, at least yet. Data mesh is a polarizing topic. And that makes sense as it is pushing boundaries. Many hope it can come to fruition but it is a bit of a utopian view. The future of data engineering is to move past managing pipelines to much higher-value work. Speed to achieving wins with data - with a clear return on investment and trust - is the first thing you should focus on. Get this right and you can have the "luxury" of building great data products. Joe started by discussing the kind of nebulous area within software engineering and data that data engineering has always played - sit between the source systems and the data o