<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Open-Source on Sohil Ladhani Blog</title><link>https://sohilladhani.com/blog/tags/open-source/</link><description>Recent content in Open-Source on Sohil Ladhani Blog</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Mon, 22 Jun 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://sohilladhani.com/blog/tags/open-source/index.xml" rel="self" type="application/rss+xml"/><item><title>Why I Built CodeSynapse</title><link>https://sohilladhani.com/blog/post/2026-06-22-codesynapse-code-graph-for-ai-assistants/</link><pubDate>Mon, 22 Jun 2026 00:00:00 +0000</pubDate><guid>https://sohilladhani.com/blog/post/2026-06-22-codesynapse-code-graph-for-ai-assistants/</guid><description>My AI assistant kept giving me confident wrong answers about my own codebase.
Not wrong in an obvious way. Wrong in the way where the answer sounds right, covers the surface, misses three critical connections, and you only realize it was wrong when you&amp;rsquo;re two hours into a change that shouldn&amp;rsquo;t have taken twenty minutes.
The specific failure: ask &amp;ldquo;what handles auth token expiry?&amp;rdquo; and it would grep for &amp;ldquo;token&amp;rdquo; and &amp;ldquo;expiry&amp;rdquo;, find some files, miss the actual handler buried behind two layers of delegation, and present the whole thing like it knew exactly what was going on.</description></item></channel></rss>