<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Testing on Gniewomir Świechowski</title>
    <link>https://gniewomir.com/tags/testing/</link>
    <description>Recent content in Testing on Gniewomir Świechowski</description>
    <image>
      <title>Gniewomir Świechowski</title>
      <url>https://gniewomir.com/images/papermod-cover.png</url>
      <link>https://gniewomir.com/images/papermod-cover.png</link>
    </image>
    <generator>Hugo -- 0.147.8</generator>
    <language>en</language>
    <lastBuildDate>Sat, 25 Jul 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://gniewomir.com/tags/testing/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Infrastructure-As-Code is still code</title>
      <link>https://gniewomir.com/posts/infrastructure-as-code-is-still-code/</link>
      <pubDate>Sat, 25 Jul 2026 00:00:00 +0000</pubDate>
      <guid>https://gniewomir.com/posts/infrastructure-as-code-is-still-code/</guid>
      <description>&lt;p&gt;I was – and I still am – a cynic when it comes to how AI will affect software development (whole &amp;ldquo;it&amp;rsquo;s an amplifier&amp;rdquo; argument + unchanged incentives). Still, after finding a flow which fits my brain, I cannot imagine working without it.&lt;/p&gt;
&lt;p&gt;Doing TDD when &amp;ldquo;devopsing&amp;rdquo; is hard, so the default observed in the wild was &amp;ldquo;get it right and pray we do not need to touch it&amp;rdquo; most of the time. Which often meant that Infrastructure-As-Code made things simpler, but reproducibility was not something you really wanted to depend on.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
