https://mauronunes.dev/Recent content on Mauro NunesHugoen-usSat, 25 Jul 2026 17:31:19 -0300https://mauronunes.dev/posts/using-tailwind-in-blazor/Sat, 25 Jul 2026 17:31:19 -0300https://mauronunes.dev/posts/using-tailwind-in-blazor/<p>Updated 25/07/2026</p> <h1 id="how-to-use-tailwind-in-a-blazor-application">How to use Tailwind in a Blazor Application</h1> <p>Tailwind makes frontend development more bearable by avoiding different <code>.css</code> files for each page or component you create and by having neat utility classes that boost your productivity. Installing it on a Blazor application is very straightforward. Below is the step-by-step process on how to install it on a Blazor web app.</p> <h2 id="installing-node">Installing Node</h2> <p>Node is the JavaScript runtime and is required for this — follow the installation guide on the <a href="https://nodejs.org/en/download">Official Node Website</a> and install the latest LTS version supported for your OS. It will bundle npm (Node Package Manager) that will allow us to install Tailwind.</p>https://mauronunes.dev/posts/throttling-vs-debouncing/Fri, 03 Jul 2026 19:01:57 -0300https://mauronunes.dev/posts/throttling-vs-debouncing/<p>Updated 03/07/2026</p> <h2 id="performance-optimization-throttling-vs-debouncing">Performance Optimization: Throttling vs. Debouncing</h2> <p>Sometimes the absolute best optimization trick you can pull to improve a system&rsquo;s performance is simply making it not run.</p> <p>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.</p>