<?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 Blog</title><link>https://blog.rickwaterman.com/tags/infrastructure-as-code/</link><description>Recent content in Infrastructure-as-Code on Blog</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Tue, 11 Mar 2025 00:00:00 +0000</lastBuildDate><atom:link href="https://blog.rickwaterman.com/tags/infrastructure-as-code/index.xml" rel="self" type="application/rss+xml"/><item><title>It's All Just AWS Under the Hood</title><link>https://blog.rickwaterman.com/posts/its-all-just-aws-under-the-hood/</link><pubDate>Tue, 11 Mar 2025 00:00:00 +0000</pubDate><guid>https://blog.rickwaterman.com/posts/its-all-just-aws-under-the-hood/</guid><description>Vercel, Netlify, Supabase, Heroku, Render, PlanetScale: open their region docs and you find AWS region codes. The platforms are thin layers over primitives you can learn directly. Deep AWS specialization — with real fluency in CDK and Terraform — is not narrowing. It is the thing that lets you use any of them, and leave any of them.</description></item><item><title>If You Are Not Part of the Implementation, You Are Part of the Problem</title><link>https://blog.rickwaterman.com/posts/if-you-are-not-part-of-the-implementation/</link><pubDate>Tue, 14 May 2024 00:00:00 +0000</pubDate><guid>https://blog.rickwaterman.com/posts/if-you-are-not-part-of-the-implementation/</guid><description>An architect who does not ship code has no feedback loop, and an architecture with no feedback loop is a guess with a diagram. Own a real piece of the build — the hard module, the infrastructure as code, the review queue — or accept that the team will route around you.</description></item></channel></rss>