<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>mlops on Alex Savin</title>
    <link>https://alexsavin.me/tags/mlops/</link>
    <description>Recent content in mlops on Alex Savin</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en</language>
    <lastBuildDate>Wed, 19 Aug 2026 01:37:10 +0000</lastBuildDate><atom:link href="https://alexsavin.me/tags/mlops/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>MLOps for software engineers - Part 1: What is an ML model?</title>
      <link>https://alexsavin.me/posts/2026-08-19-mlops-for-software-engineers/</link>
      <pubDate>Wed, 19 Aug 2026 01:37:10 +0000</pubDate>
      
      <guid>https://alexsavin.me/posts/2026-08-19-mlops-for-software-engineers/</guid>
      <description>I&amp;rsquo;m not an MLOps engineer. However for the past couple of years I&amp;rsquo;ve been working side-by-side with data scientists to create, deploy and monitor bespoke ML models. This blog is for software engineers, who might find themselves in a similar scenario.
This is especially likely if your title contains anything &amp;ldquo;full-stack&amp;rdquo; - these days this would definitely include some degree of MLOps, if your product is employing any level of modelling or prediction.</description>
    </item>
    
  </channel>
</rss>
