#87 Choosing Tech for the Now and Future and Potential Woes of Decentralizing Data Teams - Interview w/ Jesse Anderson

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/1J5LuzBWwHZIp1cXPKctyb88iXCQDPAhVDlwiMGJ3wfM/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 Jesse Anderson, Managing Director at consulting company Big Data Institute, host of the Data Dream Team podcast, and author of 3 books, most recently Data Teams. To start, a few takeaways from Jesse's perspective on the choosing technology side: You should make sure you have the right team in place to make good technology decisions - the team needs to be in place first Before selecting any technology, it's crucial to understand what you are trying to accomplish. And to understand that the technology will provide help in addressing the challenge but won't solve anything itself Focus on: is this the right tool or solution for us now and in the future? What is the roadmap and vibrancy of the solution? "Technology must earn its keep", meaning you should understand the total cost of ownership and what is your expected return on investment Data tooling cycles are probably going to be 10 years at the most - prepare for obsolescence so you aren't overly reliant on any one technology And some takeaways from Jesse's point of view on decentralizing data teams: Currently, software engineers aren't ready to be data product developers so