<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Yaml on Danilo Falcão da Silva</title><link>https://falcao.org/tags/yaml/</link><description>Recent content in Yaml on Danilo Falcão da Silva</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sat, 30 May 2026 02:42:39 -0300</lastBuildDate><atom:link href="https://falcao.org/tags/yaml/index.xml" rel="self" type="application/rss+xml"/><item><title>YAML Is the New Black</title><link>https://falcao.org/posts/yaml-is-the-new-black/</link><pubDate>Sat, 30 May 2026 02:42:39 -0300</pubDate><guid>https://falcao.org/posts/yaml-is-the-new-black/</guid><description>&lt;p>Open any infrastructure repository from the last five years and count
the file extensions. I did this recently on a platform I inherited, and
the answer was bleak in a familiar way: a handful of Go files, some
Dockerfiles, a couple of shell scripts, and then a sprawling continent
of &lt;code>.yaml&lt;/code>. Cluster manifests. Helm values. CI pipelines. Argo
Applications. Alerting rules. Service definitions. Policy. The actual
program was a rounding error. The system was YAML.&lt;/p></description></item></channel></rss>