<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Build Systems on AI VOID</title><link>https://ai-blog.noorshomelab.dev/tags/build-systems/</link><description>Recent content in Build Systems on AI VOID</description><generator>Hugo</generator><language>en</language><lastBuildDate>Sat, 14 Mar 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://ai-blog.noorshomelab.dev/tags/build-systems/index.xml" rel="self" type="application/rss+xml"/><item><title>Setting Up Your OpenZL Development Environment</title><link>https://ai-blog.noorshomelab.dev/openzl-mastery-2026/setup-openzl-development-environment/</link><pubDate>Mon, 26 Jan 2026 00:00:00 +0000</pubDate><guid>https://ai-blog.noorshomelab.dev/openzl-mastery-2026/setup-openzl-development-environment/</guid><description>&lt;h2 id="setting-up-your-openzl-development-environment"&gt;Setting Up Your OpenZL Development Environment&lt;/h2&gt;
&lt;p&gt;Welcome back, future compression wizard! In our previous chapter, we took a high-level flight over OpenZL, understanding its revolutionary approach to format-aware data compression. Now, it&amp;rsquo;s time to roll up our sleeves and get practical. Before we can dive into the fascinating world of codecs and compression graphs, we need a solid foundation: a properly configured development environment.&lt;/p&gt;
&lt;p&gt;This chapter is all about getting OpenZL ready for action on your machine. We&amp;rsquo;ll walk through installing the necessary tools, grabbing the OpenZL source code, and building it from scratch. By the end, you&amp;rsquo;ll have a working OpenZL setup, ready for experimentation and coding. No worries if you&amp;rsquo;re new to building software from source; we&amp;rsquo;ll take every single step together, explaining &lt;em&gt;why&lt;/em&gt; we&amp;rsquo;re doing what we&amp;rsquo;re doing!&lt;/p&gt;</description></item><item><title>Chapter 5: Compiler Behavior &amp;amp; TSConfig Deep Dive</title><link>https://ai-blog.noorshomelab.dev/typescript-architect-prep-2026/compiler-behavior-tsconfig-deep-dive/</link><pubDate>Wed, 14 Jan 2026 00:00:00 +0000</pubDate><guid>https://ai-blog.noorshomelab.dev/typescript-architect-prep-2026/compiler-behavior-tsconfig-deep-dive/</guid><description>&lt;h2 id="introduction"&gt;Introduction&lt;/h2&gt;
&lt;p&gt;Understanding the TypeScript compiler&amp;rsquo;s behavior and effectively configuring &lt;code&gt;tsconfig.json&lt;/code&gt; is paramount for any TypeScript developer, especially those aspiring to mid-level or architect roles. This chapter delves into the intricacies of how TypeScript transforms your code, manages types, and the profound impact your &lt;code&gt;tsconfig.json&lt;/code&gt; choices have on project structure, performance, and maintainability.&lt;/p&gt;
&lt;p&gt;For architects, &lt;code&gt;tsconfig.json&lt;/code&gt; is not just a configuration file; it&amp;rsquo;s a strategic tool that dictates module resolution, strictness levels, build performance in large codebases, and seamless integration within monorepos. This section provides a comprehensive look at the compiler&amp;rsquo;s inner workings, common configuration challenges, and advanced techniques, preparing you to answer questions that go beyond basic syntax and touch upon real-world architectural trade-offs.&lt;/p&gt;</description></item><item><title>7. Build Processes, Scaling, and Resource Management</title><link>https://ai-blog.noorshomelab.dev/void-cloud-mastery-2026/build-processes-scaling-resource-management/</link><pubDate>Sat, 14 Mar 2026 00:00:00 +0000</pubDate><guid>https://ai-blog.noorshomelab.dev/void-cloud-mastery-2026/build-processes-scaling-resource-management/</guid><description>&lt;h2 id="introduction"&gt;Introduction&lt;/h2&gt;
&lt;p&gt;Welcome back, future Void Cloud masters! In previous chapters, we learned how to get our projects up and running on Void Cloud, creating a seamless journey from local development to cloud deployment. But what happens &lt;em&gt;behind the scenes&lt;/em&gt; when you hit that &lt;code&gt;void deploy&lt;/code&gt; command? How does Void Cloud transform your source code into a live, responsive application? And how does it handle sudden spikes in user traffic without breaking a sweat?&lt;/p&gt;</description></item></channel></rss>