<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Operations on Danilo Falcão da Silva</title><link>https://falcao.org/tags/operations/</link><description>Recent content in Operations on Danilo Falcão da Silva</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sat, 30 May 2026 01:22:55 -0300</lastBuildDate><atom:link href="https://falcao.org/tags/operations/index.xml" rel="self" type="application/rss+xml"/><item><title>The Problem With Changing Tools Too Often</title><link>https://falcao.org/posts/the-problem-with-changing-tools-too-often/</link><pubDate>Sat, 30 May 2026 01:22:55 -0300</pubDate><guid>https://falcao.org/posts/the-problem-with-changing-tools-too-often/</guid><description>&lt;p>There is a particular kind of meeting I have sat in too many times. A
team is frustrated with a tool. Something broke, or the config is ugly,
or a louder team down the hall is using something newer, and someone
says the words: &amp;ldquo;maybe we should just switch to X.&amp;rdquo; And everyone nods,
because switching feels like progress, and nobody in the room wants to
be the person defending the thing that&amp;rsquo;s annoying them today.&lt;/p></description></item></channel></rss>