<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Explanation on Software Factory</title><link>/tags/explanation/</link><description>Recent content in Explanation on Software Factory</description><generator>Hugo</generator><language>en</language><atom:link href="/tags/explanation/index.xml" rel="self" type="application/rss+xml"/><item><title>Assist code understanding</title><link>/use/practices/genai/explain/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>/use/practices/genai/explain/</guid><description>&lt;h2 id="introduction"&gt;Introduction&lt;a class="td-heading-self-link" href="#introduction" aria-label="Heading self-link"&gt;&lt;/a&gt;&lt;/h2&gt;
&lt;p&gt;This practice helps developers understand unfamiliar or legacy code faster by
using coding assistants to explain intent, data flow, dependencies, assumptions,
and likely failure modes. It is especially valuable for &lt;strong&gt;onboarding
engineers&lt;/strong&gt;, &lt;strong&gt;maintainers of legacy systems&lt;/strong&gt;, and &lt;strong&gt;reviewers&lt;/strong&gt; who need to
assess impact quickly. The assistant should be used as a guided reading
companion: it accelerates analysis and reduces cognitive load, but &lt;strong&gt;human
validation remains essential&lt;/strong&gt; for correctness, security, and final
interpretation.&lt;/p&gt;</description></item></channel></rss>