<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>CDK on I am Lino</title><link>https://iamlino.net/en/tags/cdk/</link><description>Recent content in CDK on I am Lino</description><generator>Hugo</generator><language>en</language><lastBuildDate>Mon, 30 Mar 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://iamlino.net/en/tags/cdk/index.xml" rel="self" type="application/rss+xml"/><item><title>Infrastructure as Code: Why Your Infrastructure Deserves Version Control Just Like Your Code</title><link>https://iamlino.net/en/blog/infrastructure-as-code-why-your-infrastructure-deserves-version-control-just-like-your-code/</link><pubDate>Mon, 30 Mar 2026 00:00:00 +0000</pubDate><guid>https://iamlino.net/en/blog/infrastructure-as-code-why-your-infrastructure-deserves-version-control-just-like-your-code/</guid><description>&lt;p&gt;For years we&amp;rsquo;ve treated &lt;strong&gt;infrastructure&lt;/strong&gt; and &lt;strong&gt;software&lt;/strong&gt; as two separate religions, each with their own gods, their own rituals, and most importantly, their own people to blame. The code lived in Git; the infrastructure lived &amp;ldquo;in AWS,&amp;rdquo; some ethereal thing that &amp;ldquo;we manage with scripts and the console.&amp;rdquo;&lt;/p&gt;
&lt;p&gt;But the truth is your infrastructure already behaves like software: it has state, dependencies, bugs, versions, and side effects when you change it.&lt;/p&gt;</description></item></channel></rss>