<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Software-Factory on MyVar.dev</title><link>https://gibbok.github.io/myvar/tags/software-factory/</link><description>Recent content in Software-Factory on MyVar.dev</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Mon, 27 Jul 2026 05:45:55 +0000</lastBuildDate><atom:link href="https://gibbok.github.io/myvar/tags/software-factory/index.xml" rel="self" type="application/rss+xml"/><item><title>Software Factory Evolution AI and Automation in Production</title><link>https://gibbok.github.io/myvar/software-factory/software-factory-evolution-ai-and-automation-in-production/</link><pubDate>Mon, 27 Jul 2026 05:45:55 +0000</pubDate><guid>https://gibbok.github.io/myvar/software-factory/software-factory-evolution-ai-and-automation-in-production/</guid><description>&lt;h2 id="overview"&gt;Overview&lt;/h2&gt;
&lt;p&gt;A software factory represents the vision of a repeatable, instrumentable software production process, moving beyond individual craft to scaled, automated generation. This paradigm currently explores two primary models: the &lt;strong&gt;dark factory&lt;/strong&gt;, where code ships without human review, and the &lt;strong&gt;lit factory&lt;/strong&gt;, which integrates human judgment upstream and at critical verification points. The central challenge lies in determining the appropriate balance of automation and human oversight.&lt;/p&gt;
&lt;h2 id="key-insights"&gt;Key Insights&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;The &lt;strong&gt;software factory&lt;/strong&gt; concept, first introduced in 1968, is undergoing a significant re-evaluation due to recent advancements in AI and agentic systems.&lt;/li&gt;
&lt;li&gt;The foundational components of an agentic software factory are the &lt;strong&gt;loop&lt;/strong&gt;, the &lt;strong&gt;harness&lt;/strong&gt;, and the &lt;strong&gt;factory&lt;/strong&gt; itself.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Comprehension debt&lt;/strong&gt;—the widening gap between existing code and human understanding—is a critical risk for fully automated (dark) factories.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Verification&lt;/strong&gt;, not code generation, is the primary bottleneck in a software factory, necessitating the principle of &lt;strong&gt;back pressure&lt;/strong&gt;.&lt;/li&gt;
&lt;li&gt;Humans shift from &amp;ldquo;inner loop&amp;rdquo; code creation to &amp;ldquo;outer loop&amp;rdquo; responsibilities, focusing on design, architecture, judgment, and oversight.&lt;/li&gt;
&lt;li&gt;Structured workflows, or &lt;strong&gt;graphs&lt;/strong&gt; (finite state machines), offer a more reliable approach than pure, unbounded agentic loops for complex systems.&lt;/li&gt;
&lt;li&gt;Established architectural practices serve as a crucial, hard-to-fake safety net against agent-introduced errors.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="technical-details"&gt;Technical Details&lt;/h2&gt;
&lt;h3 id="the-software-factory-paradigm"&gt;The Software Factory Paradigm&lt;/h3&gt;
&lt;p&gt;The concept of a software factory, first articulated by Bob Bemer in 1968, envisions software development as a repeatable, instrumentable production process. While historically challenging to implement due to the inherent difficulty of &amp;ldquo;stamping out ideas,&amp;rdquo; recent advancements in AI and agentic systems have made this vision more tangible. The modern software factory is built upon three layered concepts: the loop, the harness, and the factory.&lt;/p&gt;</description></item></channel></rss>