<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Costs on Rough Edges</title><link>https://roughedges.dev/tags/costs/</link><description>Recent content in Costs on Rough Edges</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Thu, 09 Apr 2026 00:00:00 -0400</lastBuildDate><atom:link href="https://roughedges.dev/tags/costs/index.xml" rel="self" type="application/rss+xml"/><item><title>Your Infrastructure Costs Are Telling You Something – But Maybe Not What You Think</title><link>https://roughedges.dev/posts/infrastructure-costs-and-complexity/</link><pubDate>Thu, 09 Apr 2026 00:00:00 -0400</pubDate><guid>https://roughedges.dev/posts/infrastructure-costs-and-complexity/</guid><description>&lt;p&gt;High infrastructure costs are worth paying attention to. Teams that never look at their cloud bills tend to accumulate waste quietly – redundant logging pipelines, forgotten container registries, storage that nobody owns. Getting engineers to care about the cost of what they build is a legitimate goal, and one that&amp;rsquo;s harder than it sounds.&lt;/p&gt;
&lt;p&gt;But the diagnosis matters as much as the observation.&lt;/p&gt;
&lt;p&gt;The claim that elevated infrastructure costs primarily signal expertise gaps is too simple. Sometimes high costs reflect poor decisions. Sometimes they reflect genuine scale, regulatory requirements, or deliberate tradeoffs made during rapid growth. Sometimes they&amp;rsquo;re a combination. The work is figuring out which you&amp;rsquo;re dealing with before reaching for a solution.&lt;/p&gt;</description></item></channel></rss>