<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Seyed Jafar Mousavi</title>
    <description>The latest articles on DEV Community by Seyed Jafar Mousavi (@seyedjafar).</description>
    <link>https://dev.to/seyedjafar</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4029317%2Ff2568f04-3484-4d03-b41a-606ebbcd37af.png</url>
      <title>DEV Community: Seyed Jafar Mousavi</title>
      <link>https://dev.to/seyedjafar</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/seyedjafar"/>
    <language>en</language>
    <item>
      <title>Why I’m building Zbloue: Making complex codebases easy to understand</title>
      <dc:creator>Seyed Jafar Mousavi</dc:creator>
      <pubDate>Tue, 14 Jul 2026 23:12:13 +0000</pubDate>
      <link>https://dev.to/seyedjafar/why-im-building-zbloue-making-complex-codebases-easy-to-understand-3l7p</link>
      <guid>https://dev.to/seyedjafar/why-im-building-zbloue-making-complex-codebases-easy-to-understand-3l7p</guid>
      <description>&lt;p&gt;Have you ever opened a massive repository, stared at the file structure for 10 minutes, and felt like you needed a map just to understand where to start?&lt;/p&gt;

&lt;p&gt;We've all been there. Whether it's a legacy codebase or a new open-source library, navigating code takes a massive toll on our cognitive load. That feeling of "information overload" is exactly why I started building &lt;strong&gt;Zbloue&lt;/strong&gt;.&lt;/p&gt;

&lt;h3&gt;
  
  
  The Problem: Context Switching
&lt;/h3&gt;

&lt;p&gt;As developers, we spend way more time &lt;em&gt;reading&lt;/em&gt; code than &lt;em&gt;writing&lt;/em&gt; it. When you jump into a new codebase, you're constantly trying to figure out:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;What does this module actually do?&lt;/li&gt;
&lt;li&gt;How do these components interact?&lt;/li&gt;
&lt;li&gt;Where is the business logic hidden?&lt;/li&gt;
&lt;/ul&gt;

&lt;h3&gt;
  
  
  The Solution: Zbloue
&lt;/h3&gt;

&lt;p&gt;I wanted to build a bridge between complex code and actionable insights. &lt;strong&gt;Zbloue&lt;/strong&gt; is an AI-powered code analysis tool designed to help developers "get" a codebase in seconds, not hours.&lt;/p&gt;

&lt;h3&gt;
  
  
  The Tech Stack
&lt;/h3&gt;

&lt;p&gt;Building this has been a great journey in Developer Experience (DX):&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Next.js (App Router):&lt;/strong&gt; For a fast frontend.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;OpenAI API:&lt;/strong&gt; The engine behind the analysis.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Supabase:&lt;/strong&gt; Handling the data layer.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The biggest challenge? Handling the AI context window effectively to ensure it understands the &lt;em&gt;intent&lt;/em&gt; behind the code, not just the syntax.&lt;/p&gt;

&lt;h3&gt;
  
  
  Building in Public
&lt;/h3&gt;

&lt;p&gt;I’m building Zbloue in public because I believe the best tools are built with community feedback. &lt;/p&gt;

&lt;p&gt;&lt;strong&gt;I’d love to hear from you:&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;What’s your biggest pain point when diving into a new codebase?&lt;/li&gt;
&lt;li&gt;Have you tried AI tools for code analysis before?&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Check out the project: &lt;a href="https://zbloue.vercel.app" rel="noopener noreferrer"&gt;zbloue.vercel.app&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Let's discuss in the comments!&lt;/p&gt;

</description>
      <category>ai</category>
      <category>webdev</category>
      <category>productivity</category>
      <category>opensource</category>
    </item>
  </channel>
</rss>
