#37 Building a Self-Serve Platform Developers Will Actually Use - Interview w/ Audun Fauchald Strand and Gøran Berntsen

Data Mesh Radio - A podcast by Data as a Product Podcast Network

Categories:

Sign up for Data Mesh Understanding's free roundtable and introduction programs here: https://landing.datameshunderstanding.com/Please Rate and Review us on your podcast app of choice!If you want to be a guest or give feedback (suggestions for topics, comments, etc.), please see hereEpisode list and links to all available episode transcripts here.Provided as a free resource by Data Mesh Understanding / Scott Hirleman. Get in touch with Scott on LinkedIn if you want to chat data mesh.Transcript for this episode (link) provided by Starburst. See their Data Mesh Summit recordings here (info gated)Gøran's Twitter: @gorzan / https://twitter.com/gorzanAudun's Twitter: @audunstrand / https://twitter.com/audunstrandGøran's LinkedIn: https://www.linkedin.com/in/g%C3%B8ran-berntsen-66066517/Audun's LinkedIn: https://www.linkedin.com/in/audunstrand/NAIS Platform Website: https://nais.io/In this episode, Scott interviews Audun Fauchald Strand and Gøran Berntsen of NAV. Audun is the Principal Engineer and Gøran is the Product Manager for NAV's NAIS application platform as well as their emerging self-serve data platform for data mesh called NADA.They covered a lot of different topics including: 1) building out the platform; 2) working with consumers to set expectations for common data products; 3) definition of a data product - and how it will evolve; 4) setting the frameworks for producer teams and allowing them to own the production; 5) communicating across teams; and 6) Cake! No really, a secret to success is cake.While NAV is early days in building out their data platform for data mesh, they are taking an interesting approach: work with the developers to set data product expectations and then see how the developers would go about creating those data products. Then, the data platform team will build the platform out to make developer workflows much easier. While Gøran, with a background as a data person, feels the pull to make the self-serve platform as data-centric as possible, he understands the need to make it developer friendly from his time building the application platform with those from a developer background like Audun.They both talked about reducing friction, including via sensible defaults, as a big part of their path forward. Stop trying to make developers come up with everything themselves. While they are still early days on developing those defaults, they are comfortable in their process to get there. And working with developers along the way is key.To start, NAV's definition of a data product is a single table or view. It...