<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Garbage Collection on AI VOID</title><link>https://ai-blog.noorshomelab.dev/tags/garbage-collection/</link><description>Recent content in Garbage Collection on AI VOID</description><generator>Hugo</generator><language>en</language><lastBuildDate>Wed, 14 Jan 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://ai-blog.noorshomelab.dev/tags/garbage-collection/index.xml" rel="self" type="application/rss+xml"/><item><title>Memory Management, Garbage Collection, and Preventing Leaks</title><link>https://ai-blog.noorshomelab.dev/js-architect-prep-2026/memory-management-garbage-collection-leaks/</link><pubDate>Wed, 14 Jan 2026 00:00:00 +0000</pubDate><guid>https://ai-blog.noorshomelab.dev/js-architect-prep-2026/memory-management-garbage-collection-leaks/</guid><description>&lt;h2 id="introduction"&gt;Introduction&lt;/h2&gt;
&lt;p&gt;While JavaScript is often lauded for its automatic memory management via garbage collection, a deep understanding of how memory is allocated, utilized, and deallocated is crucial for any serious JavaScript developer, especially those aiming for mid to architect-level roles. This chapter delves into the intricacies of JavaScript&amp;rsquo;s memory model, the mechanics of its garbage collector, and the common pitfalls that lead to memory leaks.&lt;/p&gt;
&lt;p&gt;Interviewers ask these questions to gauge a candidate&amp;rsquo;s ability to write performant, stable, and scalable applications. It&amp;rsquo;s not just about knowing syntax; it&amp;rsquo;s about understanding the underlying runtime, diagnosing subtle performance issues, and proactively preventing resource exhaustion. Mastering these concepts will equip you to build robust applications and troubleshoot complex, real-world bugs that often manifest as slow performance or unexpected crashes.&lt;/p&gt;</description></item><item><title>Chapter 14: Beyond the Code: JVM Internals &amp;amp; Performance Basics</title><link>https://ai-blog.noorshomelab.dev/java-mastery-2025/chapter-14-jvm-performance-basics/</link><pubDate>Thu, 04 Dec 2025 00:00:00 +0000</pubDate><guid>https://ai-blog.noorshomelab.dev/java-mastery-2025/chapter-14-jvm-performance-basics/</guid><description>&lt;h2 id="chapter-14-beyond-the-code-jvm-internals--performance-basics"&gt;Chapter 14: Beyond the Code: JVM Internals &amp;amp; Performance Basics&lt;/h2&gt;
&lt;p&gt;Welcome back, intrepid Java explorer! So far, we&amp;rsquo;ve focused heavily on writing Java code, understanding syntax, and building applications. You&amp;rsquo;ve learned how to create classes, objects, handle data, and even design your programs using patterns. That&amp;rsquo;s fantastic! But what happens &lt;em&gt;after&lt;/em&gt; you hit that &amp;ldquo;run&amp;rdquo; button? How does your beautiful Java code actually come to life and execute on your computer?&lt;/p&gt;</description></item><item><title>How Memory Works: Deep Dive into Internals</title><link>https://ai-blog.noorshomelab.dev/how-it-works/how-memory-works/</link><pubDate>Wed, 31 Dec 2025 00:00:00 +0000</pubDate><guid>https://ai-blog.noorshomelab.dev/how-it-works/how-memory-works/</guid><description>&lt;h2 id="introduction"&gt;Introduction&lt;/h2&gt;
&lt;p&gt;In the intricate world of computing, memory is the fundamental substrate upon which all operations are performed. From the simplest variable assignment to the most complex database query, every piece of data and every instruction lives, however fleetingly, within memory. However, &amp;ldquo;memory&amp;rdquo; is not a monolithic entity; it&amp;rsquo;s a complex, multi-layered hierarchy designed to balance speed, capacity, and cost.&lt;/p&gt;
&lt;p&gt;Understanding the internals of how memory works is paramount for any serious developer or system administrator. It demystifies performance bottlenecks, helps diagnose elusive bugs like memory leaks, and empowers the creation of more efficient and robust software. Without this foundational knowledge, one is merely guessing at the underlying behavior of their applications and the systems they run on.&lt;/p&gt;</description></item></channel></rss>