<?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: tworrell</title>
    <description>The latest articles on DEV Community by tworrell (@tworrell).</description>
    <link>https://dev.to/tworrell</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.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F108669%2F99be4dbe-4281-42bb-b893-a753302e9866.jpg</url>
      <title>DEV Community: tworrell</title>
      <link>https://dev.to/tworrell</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/tworrell"/>
    <language>en</language>
    <item>
      <title>How I'm using ASTs and Gemini to solve the "Codebase Onboarding" problem 🧠</title>
      <dc:creator>tworrell</dc:creator>
      <pubDate>Wed, 15 Apr 2026 14:41:03 +0000</pubDate>
      <link>https://dev.to/tworrell/how-im-using-asts-and-gemini-to-solve-the-codebase-onboarding-problem-1la9</link>
      <guid>https://dev.to/tworrell/how-im-using-asts-and-gemini-to-solve-the-codebase-onboarding-problem-1la9</guid>
      <description>&lt;p&gt;Hi everyone! 👋&lt;/p&gt;

&lt;p&gt;I’m Tara, a Senior Software Engineer and Consultant. Over the years, I've jumped between a lot of different codebases.&lt;/p&gt;

&lt;p&gt;Every time I join a new project, I notice the exact same problem: it takes new engineers 3 to 6 months to truly understand how a complex system is glued together. AI tools like Copilot and Cursor are amazing at making us write code faster, but developers still spend almost 50% of their time just reading and navigating code.&lt;/p&gt;

&lt;p&gt;Nobody was solving the comprehension layer. So, I decided to build a tool for it.&lt;/p&gt;

&lt;p&gt;I’m super excited to share what I've been working on: &lt;a href="https://www.auracode.space/" rel="noopener noreferrer"&gt;AuraCode&lt;/a&gt;(Feel free to poke around the live interactive demo there!)&lt;/p&gt;

&lt;p&gt;🤔 What does it do?&lt;br&gt;
AuraCode is a neural code agent that transforms messy, undocumented repositories into interactive visual maps and context-aware chat.&lt;/p&gt;

&lt;p&gt;Here are the main features I’ve built so far:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;&lt;p&gt;Interactive Architecture Canvas 🗺️: Paste a GitHub URL, and it generates a beautiful, interactive D3.js radial tree mapping out component relationships and the system structure.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Contextual Chat + Text-to-Speech 🗣️: You can ask questions like "What breaks if I change this auth utility?" and get answers grounded in your actual code structure. I also hooked the output up to an ElevenLabs TTS engine, so you can have it read the flow to you hands-free while you look at the code.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Smart Onboarding ✅: Say goodbye to outdated setup.md files. AuraCode auto-generates structured onboarding checklists tailored specifically to the architecture of the scanned codebase.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Code Review Summaries 🚀: Point it at a PR, and it will run a trend analysis and spit out a review summary based on the delta.&lt;/p&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fpop72xr5gpdwmm2zkbov.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fpop72xr5gpdwmm2zkbov.png" alt="Generated Architecture mind map made with D3.Js" width="800" height="653"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;🛠️ How it works under the hood&lt;br&gt;
Building this required balancing context windows with accurate retrieval. Here is how I approached it:&lt;/p&gt;

&lt;p&gt;The AI Architecture: Treating code as "flat text" loses all the important structural relationships (call graphs, dependency chains, etc.). To solve this, AuraCode uses two different approaches depending on the size of the repository:&lt;/p&gt;

&lt;p&gt;For small/medium repos: I inject Abstract Syntax Trees (ASTs) directly into the model's context window. This preserves the architectural patterns so the AI actually understands how the code connects.&lt;br&gt;
For massive monorepos: I use what I call Lean RAG. It's a lightweight retrieval layer that selectively surfaces the most structurally relevant nodes before context injection. This keeps accuracy high without blowing out the token limit.&lt;/p&gt;

&lt;p&gt;What's next? 🚀&lt;br&gt;
Right now, AuraCode is in pre-launch. Because I am entirely bootstrapped and LLM token costs scale rapidly with usage, I am currently opening up full private-repo access to the first 50 developers on the waitlist.&lt;/p&gt;

&lt;p&gt;However, the demo is fully live and open to the public on the site!&lt;/p&gt;

&lt;p&gt;I built this because it's exactly the tool I wish I had existed every time I was hired to consult on a massive, legacy codebase.&lt;/p&gt;

&lt;p&gt;I would love to hear your thoughts! How do you usually handle ramping up on massive, undocumented codebases?&lt;/p&gt;

&lt;p&gt;Let me know if you have any questions about the tech stack, the Lean RAG approach, or the D3 visualizations. I'd love to chat in the comments! 👇&lt;/p&gt;

</description>
      <category>ai</category>
      <category>productivity</category>
      <category>webdev</category>
      <category>showdev</category>
    </item>
    <item>
      <title>How I'm using ASTs and Gemini to solve the "Codebase Onboarding" problem 🧠</title>
      <dc:creator>tworrell</dc:creator>
      <pubDate>Wed, 15 Apr 2026 14:41:03 +0000</pubDate>
      <link>https://dev.to/tworrell/how-im-using-asts-and-gemini-to-solve-the-codebase-onboarding-problem-bca</link>
      <guid>https://dev.to/tworrell/how-im-using-asts-and-gemini-to-solve-the-codebase-onboarding-problem-bca</guid>
      <description>&lt;p&gt;Hi everyone! 👋&lt;/p&gt;

&lt;p&gt;I’m Tara, a Senior Software Engineer and Consultant. Over the years, I've jumped between a lot of different codebases.&lt;/p&gt;

&lt;p&gt;Every time I join a new project, I notice the exact same problem: it takes new engineers 3 to 6 months to truly understand how a complex system is glued together. AI tools like Copilot and Cursor are amazing at making us write code faster, but developers still spend almost 50% of their time just reading and navigating code.&lt;/p&gt;

&lt;p&gt;Nobody was solving the comprehension layer. So, I decided to build a tool for it.&lt;/p&gt;

&lt;p&gt;I’m super excited to share what I've been working on: &lt;a href="https://www.auracode.space/" rel="noopener noreferrer"&gt;AuraCode&lt;/a&gt;(Feel free to poke around the live interactive demo there!)&lt;/p&gt;

&lt;p&gt;🤔 What does it do?&lt;br&gt;
AuraCode is a neural code agent that transforms messy, undocumented repositories into interactive visual maps and context-aware chat.&lt;/p&gt;

&lt;p&gt;Here are the main features I’ve built so far:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;&lt;p&gt;Interactive Architecture Canvas 🗺️: Paste a GitHub URL, and it generates a beautiful, interactive D3.js radial tree mapping out component relationships and the system structure.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Contextual Chat + Text-to-Speech 🗣️: You can ask questions like "What breaks if I change this auth utility?" and get answers grounded in your actual code structure. I also hooked the output up to an ElevenLabs TTS engine, so you can have it read the flow to you hands-free while you look at the code.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Smart Onboarding ✅: Say goodbye to outdated setup.md files. AuraCode auto-generates structured onboarding checklists tailored specifically to the architecture of the scanned codebase.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Code Review Summaries 🚀: Point it at a PR, and it will run a trend analysis and spit out a review summary based on the delta.&lt;/p&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fpop72xr5gpdwmm2zkbov.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fpop72xr5gpdwmm2zkbov.png" alt="Generated Architecture mind map made with D3.Js" width="800" height="653"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;🛠️ How it works under the hood&lt;br&gt;
Building this required balancing context windows with accurate retrieval. Here is how I approached it:&lt;/p&gt;

&lt;p&gt;The AI Architecture: Treating code as "flat text" loses all the important structural relationships (call graphs, dependency chains, etc.). To solve this, AuraCode uses two different approaches depending on the size of the repository:&lt;/p&gt;

&lt;p&gt;For small/medium repos: I inject Abstract Syntax Trees (ASTs) directly into the model's context window. This preserves the architectural patterns so the AI actually understands how the code connects.&lt;br&gt;
For massive monorepos: I use what I call Lean RAG. It's a lightweight retrieval layer that selectively surfaces the most structurally relevant nodes before context injection. This keeps accuracy high without blowing out the token limit.&lt;/p&gt;

&lt;p&gt;What's next? 🚀&lt;br&gt;
Right now, AuraCode is in pre-launch. Because I am entirely bootstrapped and LLM token costs scale rapidly with usage, I am currently opening up full private-repo access to the first 50 developers on the waitlist.&lt;/p&gt;

&lt;p&gt;However, the demo is fully live and open to the public on the site!&lt;/p&gt;

&lt;p&gt;I built this because it's exactly the tool I wish I had existed every time I was hired to consult on a massive, legacy codebase.&lt;/p&gt;

&lt;p&gt;I would love to hear your thoughts! How do you usually handle ramping up on massive, undocumented codebases?&lt;/p&gt;

&lt;p&gt;Let me know if you have any questions about the tech stack, the Lean RAG approach, or the D3 visualizations. I'd love to chat in the comments! 👇&lt;/p&gt;

</description>
      <category>ai</category>
      <category>gemini</category>
      <category>productivity</category>
      <category>showdev</category>
    </item>
    <item>
      <title>Re-Codenize - Codebase Navigation Assistant</title>
      <dc:creator>tworrell</dc:creator>
      <pubDate>Mon, 27 Jan 2025 04:15:30 +0000</pubDate>
      <link>https://dev.to/tworrell/re-codenize-codebase-4lbp</link>
      <guid>https://dev.to/tworrell/re-codenize-codebase-4lbp</guid>
      <description>&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fha6eeqcpaz06ak65e4kw.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fha6eeqcpaz06ak65e4kw.png" alt="Black and Green Polygons that has a cheeky play on code with Re-Codenize wrapped inside codebase" width="800" height="294"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;em&gt;This is a submission for the &lt;a href="https://srv.buysellads.com/ads/long/x/T6EK3TDFTTTTTT6WWB6C5TTTTTTGBRAPKATTTTTTWTFVT7YTTTTTTKPPKJFH4LJNPYYNNSZL2QLCE2DPPQVCEI45GHBT" rel="noopener noreferrer"&gt;Agent.ai&lt;/a&gt; Challenge: Productivity-Pro Agent (&lt;a href="https://dev.to/challenges/agentai"&gt;See Details&lt;/a&gt;)&lt;/em&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  What I Built
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;Your AI-Powered Guide to Codebase Mastery — Onboard Faster, Contribute Smarter.&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;This AI agent is a &lt;strong&gt;codebase navigation assistant&lt;/strong&gt; designed to streamline onboarding for software engineers whether it is for joining a new client or an open source project. &lt;/p&gt;

&lt;p&gt;It works by helping software engineers understand and explore a new codebase quickly and efficiently. This AI Agent acts as a guide, providing codebase insights, Smart Search, and File and Function Summaries.&lt;/p&gt;

&lt;p&gt;I created this AI Agent because I’ve often faced challenges getting timely meetings with fellow software engineers to provide high-level overviews and explanations of codebases I was assigned to enhance or build upon. I wanted to find a solution to alleviate this bottleneck, and that’s how this idea was born. This concept has been on my mind for over a year, and I had already started developing it independently. However, when I discovered the opportunity to accelerate its development with Agent.ai, I couldn’t pass it up. While there are still many features I’d like to add, this is an incredible starting point.&lt;/p&gt;

&lt;h2&gt;
  
  
  Demo
&lt;/h2&gt;

&lt;p&gt;&lt;a href="https://vimeo.com/1050615163/c7992f81eb?ts=0&amp;amp;share=copy" rel="noopener noreferrer"&gt;Demo&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;a href="https://agent.ai/agent/re-codenize" rel="noopener noreferrer"&gt;Try it Out&lt;/a&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  Agent.ai Experience
&lt;/h2&gt;

&lt;p&gt;I thoroughly enjoyed bringing my idea to life. While there is a bit of a learning curve when using the Agent.ai interface to build your agent, it’s quite manageable. I’m incredibly excited to see how people use this agent and to hear their feedback on how it’s working for them.&lt;/p&gt;

&lt;h2&gt;
  
  
  What's Next
&lt;/h2&gt;

&lt;p&gt;I have several additional features I’m excited to add, such as visualization tools and more. I’ll also continue building on this project through the website I’ve been developing, where users will soon be able to access and explore all the features I have planned for this AI agent.&lt;/p&gt;

&lt;p&gt;✨Thanks for reading.✨ Happy Coding! 👩🏾‍💻&lt;/p&gt;

</description>
      <category>devchallenge</category>
      <category>agentaichallenge</category>
      <category>ai</category>
      <category>machinelearning</category>
    </item>
  </channel>
</rss>
