<?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 Carol Hsu's Blog</title><link>https://carol-hsu.github.io/tags/infrastructure-as-code/</link><description>Recent content in Infrastructure-as-Code on Carol Hsu's Blog</description><generator>Hugo</generator><language>en</language><managingEditor>asymplone@gmail.com (Carol Hsu)</managingEditor><webMaster>asymplone@gmail.com (Carol Hsu)</webMaster><lastBuildDate>Sun, 19 Apr 2026 14:57:35 +0200</lastBuildDate><atom:link href="https://carol-hsu.github.io/tags/infrastructure-as-code/index.xml" rel="self" type="application/rss+xml"/><item><title>The Tangled Love-Hate Story of Infrastructure as Code</title><link>https://carol-hsu.github.io/post/study/iac_intro/</link><pubDate>Sun, 19 Apr 2026 00:00:00 +0000</pubDate><author>asymplone@gmail.com (Carol Hsu)</author><guid>https://carol-hsu.github.io/post/study/iac_intro/</guid><description>&lt;p>What motivated me to write this post is not a particularly pleasant story.
It&amp;rsquo;s true that I haven&amp;rsquo;t worked in industry for a while, as I&amp;rsquo;ve spent the past few years focusing on becoming an independent researcher.
This post serves as a small piece of evidence
for those who might question whether I still have the background knowledge or the ability to pick up practical engineering skills.
Another reason comes from my experience working as a DevOps engineer.
The work itself never gave me a headache:
learning new frameworks and tools, building delivery pipelines,
and configuring end-to-end integrations were all manageable.
However, the job could sometimes feel frustrating.
The quality of such work is difficult to measure and often receives little attention,
so it is taken less seriously than the service or product it supports.&lt;/p></description></item></channel></rss>