# MLOps Week 17: Why Data Scientists Need MLOps with Mikiko Bazeley Page: https://stenobird.com/podcast/mlops-weekly/mlops-week-17-why-data-scientists-need-mlops-with-mikiko-bazeley Text version: https://stenobird.com/podcast/mlops-weekly/mlops-week-17-why-data-scientists-need-mlops-with-mikiko-bazeley.md Podcast: [MLOps Weekly Podcast](https://stenobird.com/podcast/mlops-weekly) Published: 2023-04-12T17:30:11+00:00 Episode link: https://rss.com/podcasts/mlops-weekly/905492 Audio file: https://content.rss.com/episodes/132586/905492/mlops-weekly/2023_04_12_17_27_47_84c89e1f-0e79-4023-8502-03d48ba22dea.mp3 Processing state: processed JSON: https://stenobird.com/v1/public/podcasts/mlops-weekly/episodes/mlops-week-17-why-data-scientists-need-mlops-with-mikiko-bazeley Duration seconds: 2242 ## Resource This episode covers We're, MLOps Weekly Podcast, Head, Mikiko Bazeley. Mikiko, and MLOps. It also touches on Weekly, Podcast, and Mikiko. ## Highlights - The episode discusses We're - The episode discusses MLOps Weekly Podcast - The episode discusses Head - The episode discusses Mikiko Bazeley. Mikiko - The episode discusses MLOps - The episode discusses Weekly ## Topics We're, MLOps Weekly Podcast, Head, Mikiko Bazeley. Mikiko, MLOps, Weekly, Podcast, Mikiko, Hey, Simba Kadi ## Chapters - 0:00 — Hey: Discussion of Hey, Simba Kadi, and Lops. - 10:00 — And: Discussion of And, MailChamp, and ML. And. - 20:00 — Should: Discussion of Should, Change, and And. - 30:00 — Nemo: Discussion of Nemo, For, and Like. ## Actions - request_transcript: `POST https://stenobird.com/v1/public/podcasts/mlops-weekly/episodes/mlops-week-17-why-data-scientists-need-mlops-with-mikiko-bazeley/transcription-requests` — Idempotently request low-priority transcript generation for this episode. - read_markdown: `GET https://stenobird.com/podcast/mlops-weekly/mlops-week-17-why-data-scientists-need-mlops-with-mikiko-bazeley.md` — Read the agent-friendly Markdown representation of this episode resource. A page view does not enqueue transcription. Agents should invoke `request_transcript` explicitly when they need this episode processed. ## Transcript Full transcripts are not published on public pages unless there is a clear rights basis.