<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Posts on Mauro Nunes</title><link>https://mauronunes.dev/posts/</link><description>Recent content in Posts on Mauro Nunes</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Fri, 03 Jul 2026 19:01:57 -0300</lastBuildDate><atom:link href="https://mauronunes.dev/posts/index.xml" rel="self" type="application/rss+xml"/><item><title>Performance Optimization: Throttling vs. Debouncing</title><link>https://mauronunes.dev/posts/throttling-vs-debouncing/</link><pubDate>Fri, 03 Jul 2026 19:01:57 -0300</pubDate><guid>https://mauronunes.dev/posts/throttling-vs-debouncing/</guid><description>&lt;p&gt;Updated 03/07/2026&lt;/p&gt;
&lt;h2 id="performance-optimization-throttling-vs-debouncing"&gt;Performance Optimization: Throttling vs. Debouncing&lt;/h2&gt;
&lt;p&gt;Sometimes the absolute best optimization trick you can pull to improve a system&amp;rsquo;s performance is simply making it not run.&lt;/p&gt;
&lt;p&gt;Throttling and debouncing are two essential techniques that boil down to intentionally ignoring function calls. While they both stop your app from doing too much work, they operate in completely different ways. Here is a simple breakdown of how they work and when to reach for each.&lt;/p&gt;</description></item></channel></rss>