<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Architecture on El PoshoX</title><link>http://elposhox.dev/en/tags/architecture/</link><description>Recent content in Architecture on El PoshoX</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>© 2026 Az García Zúñiga</copyright><lastBuildDate>Wed, 15 Jul 2026 13:26:00 -0600</lastBuildDate><atom:link href="http://elposhox.dev/en/tags/architecture/index.xml" rel="self" type="application/rss+xml"/><item><title>The code comprehension hierarchy: why LSP is just the beginning for AI coding tools</title><link>http://elposhox.dev/en/posts/jerarquia-comprension-codigo-ai/</link><pubDate>Wed, 15 Jul 2026 13:26:00 -0600</pubDate><guid>http://elposhox.dev/en/posts/jerarquia-comprension-codigo-ai/</guid><description>&lt;div class="lead text-neutral-500 dark:text-neutral-400 !mb-9 text-xl"&gt;
 Most AI coding tools understand your code at the level of a junior with grep, when the best ones operate four layers above. I organized these layers into seven levels to understand what separates one tool from another.
&lt;/div&gt;

&lt;p&gt;When an AI coding tool needs to know where a function is used, most do exactly what you would do with &lt;code&gt;grep&lt;/code&gt;. Scan text, find matches, and hope the result makes sense. Some make the &lt;strong&gt;jump to LSP&lt;/strong&gt; and get real semantic answers, types, definitions, exact references, but almost none operate at the level where they truly understand your system&amp;rsquo;s architecture, the dependencies between services, the transitive impact of a change.&lt;/p&gt;</description></item></channel></rss>