<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>SDLC on AI VOID</title><link>https://ai-blog.noorshomelab.dev/tags/sdlc/</link><description>Recent content in SDLC on AI VOID</description><generator>Hugo</generator><language>en</language><lastBuildDate>Sat, 18 Apr 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://ai-blog.noorshomelab.dev/tags/sdlc/index.xml" rel="self" type="application/rss+xml"/><item><title>Chapter 15: Threat Modeling for Large-Scale Applications</title><link>https://ai-blog.noorshomelab.dev/web-security-ethical-hacking-2026/threat-modeling-large-apps/</link><pubDate>Sun, 04 Jan 2026 00:00:00 +0000</pubDate><guid>https://ai-blog.noorshomelab.dev/web-security-ethical-hacking-2026/threat-modeling-large-apps/</guid><description>&lt;h2 id="introduction-to-proactive-security-with-threat-modeling"&gt;Introduction to Proactive Security with Threat Modeling&lt;/h2&gt;
&lt;p&gt;Welcome to Chapter 15! So far, we&amp;rsquo;ve explored many fascinating (and sometimes scary!) attack techniques and learned how to defend against them. But what if we could catch potential vulnerabilities &lt;em&gt;before&lt;/em&gt; any code is even written, or at least very early in the development cycle? That&amp;rsquo;s where &lt;strong&gt;Threat Modeling&lt;/strong&gt; comes in.&lt;/p&gt;
&lt;p&gt;In this chapter, we&amp;rsquo;re going to dive deep into threat modeling, a structured approach to identifying potential threats, vulnerabilities, and countermeasures within an application or system. For large-scale applications, with their intricate microservices, APIs, and distributed components, proactive security is not just a best practice—it&amp;rsquo;s a necessity. We&amp;rsquo;ll learn how to systematically break down complex systems, identify potential attack vectors, and design security controls right from the start.&lt;/p&gt;</description></item><item><title>DevSecOps Tools: Complete Comparison 2026</title><link>https://ai-blog.noorshomelab.dev/comparisons/devsecops-tools-comparison-2026/</link><pubDate>Sat, 18 Apr 2026 00:00:00 +0000</pubDate><guid>https://ai-blog.noorshomelab.dev/comparisons/devsecops-tools-comparison-2026/</guid><description>&lt;p&gt;Integrating security seamlessly into the development pipeline is no longer optional; it&amp;rsquo;s a fundamental requirement for modern software delivery. This guide dives deep into 11 essential DevSecOps tools, dissecting their capabilities to help you fortify your Secure Software Development Lifecycle (SSDLC).&lt;/p&gt;
&lt;h2 id="why-this-comparison-matters"&gt;Why This Comparison Matters&lt;/h2&gt;
&lt;p&gt;In 2026, the complexity of software supply chains, the rapid adoption of cloud-native architectures, and the increasing sophistication of cyber threats demand a proactive approach to security. DevSecOps tools are the backbone of this shift-left strategy, enabling teams to identify and remediate vulnerabilities early, reduce technical debt, and accelerate secure deployments. Choosing the right tools can mean the difference between robust, resilient applications and costly, reputation-damaging breaches.&lt;/p&gt;</description></item><item><title>The AI Paradox: Why Coding Assistants Haven&amp;#39;t Turbocharged Software Delivery (Yet)</title><link>https://ai-blog.noorshomelab.dev/blog/ai-coding-assistants-software-delivery-bottleneck-2026/</link><pubDate>Mon, 06 Apr 2026 00:00:00 +0000</pubDate><guid>https://ai-blog.noorshomelab.dev/blog/ai-coding-assistants-software-delivery-bottleneck-2026/</guid><description>&lt;h2 id="the-ai-paradox-why-coding-assistants-havent-turbocharged-software-delivery-yet"&gt;The AI Paradox: Why Coding Assistants Haven&amp;rsquo;t Turbocharged Software Delivery (Yet)&lt;/h2&gt;
&lt;p&gt;In 2026, AI coding assistants like GitHub Copilot, Amazon CodeWhisperer, and Google Gemini Code are ubiquitous. They promise to revolutionize developer productivity, churning out lines of code at unprecedented speeds. Yet, many organizations are finding that while individual developers might feel more productive, the overall software delivery pipeline hasn&amp;rsquo;t accelerated commensurately. Why the disconnect?&lt;/p&gt;
&lt;p&gt;The answer lies in a fundamental misunderstanding of where the true bottlenecks in the Software Development Lifecycle (SDLC) actually reside. Coding, it turns out, was never the primary slowdown. Instead, the downstream stages—review, testing, quality assurance (QA), and deployment—are now struggling to keep pace with the sheer volume of AI-generated code. This post will dissect this &amp;ldquo;AI paradox,&amp;rdquo; identify the real bottlenecks, and offer actionable strategies for truly leveraging AI to improve overall software delivery speed.&lt;/p&gt;</description></item></channel></rss>