<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Week 3 - MLOps Engineering on AI Platform Engineering Handbook</title><link>/docs/week-03/</link><description>Recent content in Week 3 - MLOps Engineering on AI Platform Engineering Handbook</description><generator>Hugo</generator><language>en</language><copyright>Copyright (c) 2026 Harshhaa</copyright><atom:link href="/docs/week-03/index.xml" rel="self" type="application/rss+xml"/><item><title>ML Lifecycle &amp; Experiment Tracking</title><link>/docs/week-03/ml-lifecycle-experiment-tracking/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>/docs/week-03/ml-lifecycle-experiment-tracking/</guid><description>&lt;hr&gt;
&lt;h2 id="1-machine-learning-lifecycle-overview"&gt;1. Machine Learning Lifecycle Overview&lt;/h2&gt;
&lt;p&gt;Before diving into individual concepts, you need a mental model of the complete journey a machine learning project takes from idea to production. Most engineers new to ML think the lifecycle is: get data, train model, done. In reality, that&amp;rsquo;s about 10% of the work. The full lifecycle is a continuous loop involving many disciplines, many failure modes, and many handoffs between people and systems.&lt;/p&gt;</description></item><item><title>Model Packaging &amp; Serving</title><link>/docs/week-03/model-packaging-serving/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>/docs/week-03/model-packaging-serving/</guid><description>&lt;hr&gt;
&lt;h2 id="1-model-serialization-techniques"&gt;1. Model Serialization Techniques&lt;/h2&gt;
&lt;p&gt;You&amp;rsquo;ve trained a model. The training process ran for hours, consumed gigabytes of GPU memory, and produced a set of learned parameters — numbers representing the patterns the model discovered in your data. When training finishes, those parameters exist only in your process&amp;rsquo;s memory. The moment that process ends, they&amp;rsquo;re gone forever unless you save them to disk. Serialization is the process of converting those in-memory parameters and model structure into a format that can be stored persistently and loaded back later.&lt;/p&gt;</description></item><item><title>CI/CD for Machine Learning</title><link>/docs/week-03/cicd-for-machine-learning/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>/docs/week-03/cicd-for-machine-learning/</guid><description>&lt;hr&gt;
&lt;h2 id="1-ml-pipeline-architecture"&gt;1. ML Pipeline Architecture&lt;/h2&gt;
&lt;p&gt;Before getting into individual concepts, you need a mental model of what an ML pipeline actually is and why it needs to be a pipeline at all rather than a collection of scripts someone runs manually.&lt;/p&gt;</description></item><item><title>Data Validation, LLM Ops &amp; Monitoring</title><link>/docs/week-03/data-validation-llm-ops-monitoring/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>/docs/week-03/data-validation-llm-ops-monitoring/</guid><description>&lt;hr&gt;
&lt;h2 id="1-data-quality-validation-concepts"&gt;1. Data Quality Validation Concepts&lt;/h2&gt;
&lt;p&gt;Let&amp;rsquo;s start with the most important insight about data quality in machine learning: bad data is the silent killer of ML systems. Unlike application bugs that crash loudly and obviously, bad data produces models that fail quietly. The model keeps running, keeps returning predictions, and nobody realizes anything is wrong until the damage is done — wrong loan approvals, missed fraud, bad recommendations, or incorrect medical predictions that affected real patients.&lt;/p&gt;</description></item></channel></rss>