<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Opentofu on F. Latini - IT Engineer</title><link>https://latini.dev/tags/opentofu/</link><description>Recent content in Opentofu on F. Latini - IT Engineer</description><generator>Hugo</generator><language>en</language><lastBuildDate>Wed, 10 Jun 2026 08:00:00 +0000</lastBuildDate><atom:link href="https://latini.dev/tags/opentofu/index.xml" rel="self" type="application/rss+xml"/><item><title>Learn Terraform Fluently</title><link>https://latini.dev/posts/learn-terraform-fluently/</link><pubDate>Wed, 10 Jun 2026 08:00:00 +0000</pubDate><guid>https://latini.dev/posts/learn-terraform-fluently/</guid><description>&lt;p&gt;&lt;strong&gt;TL;DR&lt;/strong&gt; - Most people who &amp;ldquo;know Terraform&amp;rdquo; have memorised &lt;code&gt;plan&lt;/code&gt; and &lt;code&gt;apply&lt;/code&gt; and treat the rest as weather. Fluency is a mental model, not a command list. Internalise five things - state as the source of truth, the plan as a diff you actually read, modules as functions, drift as a signal, and code organised by blast radius - and Terraform stops being a slot machine you pull and start being a tool you steer. This is the post I wish someone had handed me before my first &lt;code&gt;terraform destroy&lt;/code&gt; on the wrong workspace.&lt;/p&gt;</description></item></channel></rss>