<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Infrastructure-as-Code on Left 4 More</title><link>https://left4more.com/tags/infrastructure-as-code/</link><description>Recent content in Infrastructure-as-Code on Left 4 More</description><generator>Hugo</generator><language>en-au</language><lastBuildDate>Sat, 20 Jun 2026 11:30:16 +1000</lastBuildDate><atom:link href="https://left4more.com/tags/infrastructure-as-code/index.xml" rel="self" type="application/rss+xml"/><item><title>Diagrams That Lie to You, and the Beautiful Madness of Fixing That</title><link>https://left4more.com/posts/diagrams-that-lie-to-you-and-the-beautiful-madness/</link><pubDate>Sat, 20 Jun 2026 11:30:16 +1000</pubDate><guid>https://left4more.com/posts/diagrams-that-lie-to-you-and-the-beautiful-madness/</guid><description>&lt;p>Someone posted their homelab setup online recently and the project itself is genuinely clever: they took their network diagram out of a drawing tool and made it a build artefact instead. A text file in a repo, a GitHub Actions workflow that renders it on every push, icons pulled from public sources at render time so nothing drifts. The diagram can&amp;rsquo;t lie to you because it rebuilds itself from the thing that is actually true.&lt;/p></description></item></channel></rss>