<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Week 4 - Platform Engineering on AI Platform Engineering Handbook</title><link>/docs/week-04/</link><description>Recent content in Week 4 - Platform Engineering on AI Platform Engineering Handbook</description><generator>Hugo</generator><language>en</language><copyright>Copyright (c) 2026 Harshhaa</copyright><atom:link href="/docs/week-04/index.xml" rel="self" type="application/rss+xml"/><item><title>Infrastructure as Code (Terraform Advanced)</title><link>/docs/week-04/infrastructure-as-code-terraform-advanced/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>/docs/week-04/infrastructure-as-code-terraform-advanced/</guid><description>&lt;hr&gt;
&lt;h2 id="1-infrastructure-as-code-principles"&gt;1. Infrastructure as Code Principles&lt;/h2&gt;
&lt;p&gt;Let&amp;rsquo;s start from the very beginning and understand why Infrastructure as Code exists, because once you understand the problem it solves, every other concept in this section makes intuitive sense.&lt;/p&gt;</description></item><item><title>GitOps &amp; Continuous Delivery</title><link>/docs/week-04/gitops-continuous-delivery/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>/docs/week-04/gitops-continuous-delivery/</guid><description>&lt;hr&gt;
&lt;h2 id="1-gitops-principles"&gt;1. GitOps Principles&lt;/h2&gt;
&lt;p&gt;To understand GitOps, you first need to understand the problem it solves, because the solution only makes sense in the context of the problem.&lt;/p&gt;</description></item><item><title>Internal Developer Platform (IDP)</title><link>/docs/week-04/internal-developer-platform-idp/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>/docs/week-04/internal-developer-platform-idp/</guid><description>&lt;hr&gt;
&lt;h2 id="1-platform-engineering-fundamentals"&gt;1. Platform Engineering Fundamentals&lt;/h2&gt;
&lt;p&gt;To understand platform engineering, you first need to understand the problem that created the need for it, because the discipline emerged directly from a specific pain point that organizations hit as they scaled their engineering teams.&lt;/p&gt;</description></item></channel></rss>