<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Best-Practices on Samuel Matildes - Knowledge Base</title><link>https://docs.matildes.dev/tags/best-practices/</link><description>Recent content in Best-Practices on Samuel Matildes - Knowledge Base</description><generator>Hugo</generator><language>en</language><lastBuildDate>Tue, 26 May 2026 14:15:13 +0100</lastBuildDate><atom:link href="https://docs.matildes.dev/tags/best-practices/index.xml" rel="self" type="application/rss+xml"/><item><title>Before You Scale: Why Software Optimization Beats Hardware Every Time</title><link>https://docs.matildes.dev/software-engineering/memory-optimization/</link><pubDate>Mon, 02 Feb 2026 00:00:00 +0000</pubDate><guid>https://docs.matildes.dev/software-engineering/memory-optimization/</guid><description>&lt;p&gt;&lt;i class="fas fa-microchip" aria-hidden="true"&gt;&lt;/i&gt; Before You Scale: Why Software Optimization Beats Hardware Every Time&lt;/p&gt;
&lt;h2 id="summary"&gt;Summary&lt;a class="td-heading-self-link" href="#summary" aria-label="Heading self-link"&gt;&lt;/a&gt;&lt;/h2&gt;
&lt;p&gt;When your application crashes with an Out-of-Memory (OOM) error, the instinctive response is often: &amp;ldquo;Let&amp;rsquo;s add more RAM.&amp;rdquo; In the age of cloud computing where resources are just a slider away, this approach has become the default. But what if I told you that a 30-minute code investigation could reduce your memory usage by &lt;strong&gt;95%&lt;/strong&gt;—turning a 3GB memory spike into 150MB?&lt;/p&gt;</description></item></channel></rss>