DevOps with Matthias Thierbach

July 21, 2025 By Mike Carlo

DevOps is a Process

The explicit measures podcast unpacks what does DevOps mean. It’s not a software it is a way of thinking. Matthias is the creator and inventor of our now beloved TMDL format. This conversation will blow your mind as you learn about DevOps with Microsoft Fabric.

📺 Playlist Overview

Total Videos: 4
Theme: DevOps strategies and practices in Power BI
Guest: Mathias Thierbach
Audience: Power BI professionals and teams interested in CI/CD, DataOps, and DevOps methodologies

🔗 Videos in the Playlist

Deep Dive on CI/CD Branching Strategy – Ep.436

Provides a detailed look at branching strategies for continuous integration and deployment in Power BI projects.

DataOps is the Future of Power BI Teams – Ep.435

Discusses how DataOps principles can streamline Power BI team workflows and improve collaboration.

Top Down and Bottom Up DevOps – Ep.434

Explores different approaches to implementing DevOps in Power BI environments, from leadership-driven to grassroots efforts.

DevOps and You, Your Team, and Your Data – Ep.433

Introduces the foundational concepts of DevOps in Power BI and how they impact individuals, teams, and data governance.

Listen on Your Favorite Platform

Oct 27, 2026

How to Play This or That: The Daily Power BI Game

Three Power BI hot takes a day. Pick a side, give your reason, and see how the community voted. Here's how to play This or That.

Oct 24, 2026

How Deplavity Was Born (and Everything We Made Because of It)

On Explicit Measures episode 573, Mike Carlo tried to say "deployment savvy" and invented Deplavity instead. Here is where the slip happened, how it turned into a fake prescription drug, and every video, ad, and jingle made because of it.

Oct 20, 2026

Fabric Deployment Plan - Ep.573

Fabric deployment plans let you order deployments and run notebooks or pipelines before and after each item lands, which finally gives data a place in the release. Mike Carlo and Tommy Puglia work out which teams should reach for a plan, which should stay in Git and GitHub Actions, and why both would wait for GA.