<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Linting on AI VOID</title><link>https://ai-blog.noorshomelab.dev/tags/linting/</link><description>Recent content in Linting on AI VOID</description><generator>Hugo</generator><language>en</language><lastBuildDate>Wed, 11 Feb 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://ai-blog.noorshomelab.dev/tags/linting/index.xml" rel="self" type="application/rss+xml"/><item><title>Chapter 17: Quality Assurance: Linting, Formatting, and Testing</title><link>https://ai-blog.noorshomelab.dev/ts-mastery-2025/quality-assurance-linting-formatting-testing/</link><pubDate>Fri, 05 Dec 2025 00:00:00 +0000</pubDate><guid>https://ai-blog.noorshomelab.dev/ts-mastery-2025/quality-assurance-linting-formatting-testing/</guid><description>&lt;h2 id="chapter-17-quality-assurance-linting-formatting-and-testing"&gt;Chapter 17: Quality Assurance: Linting, Formatting, and Testing&lt;/h2&gt;
&lt;p&gt;Welcome back, intrepid TypeScript adventurer! You&amp;rsquo;ve come a long way, mastering types, interfaces, classes, and even advanced design patterns. But what good is beautifully architected code if it&amp;rsquo;s riddled with inconsistencies, potential bugs, or simply hard for others to read?&lt;/p&gt;
&lt;p&gt;In this crucial chapter, we&amp;rsquo;re going to dive into the world of &lt;strong&gt;Quality Assurance&lt;/strong&gt;. We&amp;rsquo;ll equip our TypeScript projects with powerful tools for &lt;strong&gt;linting&lt;/strong&gt; (catching errors and style issues), &lt;strong&gt;formatting&lt;/strong&gt; (ensuring consistent code style), and &lt;strong&gt;testing&lt;/strong&gt; (verifying our code works as expected). These aren&amp;rsquo;t just &amp;ldquo;nice-to-haves&amp;rdquo;; they are absolute necessities for any production-ready application, helping you build robust, maintainable, and collaborative codebases. Get ready to elevate your code quality game!&lt;/p&gt;</description></item><item><title>Chapter 21: Developer Experience (DX) and Project Maintainability</title><link>https://ai-blog.noorshomelab.dev/angular-production-guide-2026/developer-experience-maintainability/</link><pubDate>Wed, 11 Feb 2026 00:00:00 +0000</pubDate><guid>https://ai-blog.noorshomelab.dev/angular-production-guide-2026/developer-experience-maintainability/</guid><description>&lt;h2 id="chapter-21-developer-experience-dx-and-project-maintainability"&gt;Chapter 21: Developer Experience (DX) and Project Maintainability&lt;/h2&gt;
&lt;p&gt;Welcome to Chapter 21! In this part of our journey, we&amp;rsquo;re shifting our focus from building features to building a &lt;em&gt;better development experience&lt;/em&gt; and ensuring our Angular applications remain robust and maintainable over time. While shiny new features are exciting, a project&amp;rsquo;s long-term success often hinges on how easy it is for developers to understand, modify, and extend the codebase. This is where Developer Experience (DX) and thoughtful project maintainability practices come into play.&lt;/p&gt;</description></item></channel></rss>