<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Articles on human - The Dark Software Factory for Claude Code</title>
    <link>https://gethuman.sh/articles/</link>
    <description>Recent content in Articles on human - The Dark Software Factory for Claude Code</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Mon, 25 May 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://gethuman.sh/articles/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Getting to the Dark Software Factory</title>
      <link>https://gethuman.sh/getting-to-the-dark-software-factory/</link>
      <pubDate>Mon, 25 May 2026 00:00:00 +0000</pubDate>
      <guid>https://gethuman.sh/getting-to-the-dark-software-factory/</guid>
      <description>&lt;aside class=&#34;tldr&#34;&gt;&#xA;  &lt;span class=&#34;tldr-label&#34;&gt;TL;DR&lt;/span&gt;&#xA;  &lt;p&gt;A dark software factory ships work from intent to production with no developer touching it on the way. Darkness is per-unit — about which stages run unattended, not how much AI you use overall — and it needs three things from the infrastructure, not the agent: machine-derivable intent, machine-observable outcomes, and a machine-bounded blast radius. A qualifier routes each unit into a dark lane or leaves it to humans; lanes are defined by intent source and capability (maintenance, bug autofix, telemetry-driven, transformation, gardening), while concerns like passing tests and stable APIs are the floor every lane must clear. Run continuously, the qualifier becomes a forager that cherry-picks work, and that scoring function — not the agents — is the real product. As shipping costs collapse, the bottleneck moves from what you can build to positioning and attention, so the factory&#39;s real value is throughput plus restraint.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Yes, You Can Run a Dark Factory on Your Codebase</title>
      <link>https://gethuman.sh/run-a-dark-factory-on-your-codebase/</link>
      <pubDate>Sat, 23 May 2026 00:00:00 +0000</pubDate>
      <guid>https://gethuman.sh/run-a-dark-factory-on-your-codebase/</guid>
      <description>&lt;aside class=&#34;tldr&#34;&gt;&#xA;  &lt;span class=&#34;tldr-label&#34;&gt;TL;DR&lt;/span&gt;&#xA;  &lt;p&gt;Yes, you can run a dark software factory on your own codebase today, and the recipe is lighter than the writeups make it look. Six categories already ship good results against the test infrastructure most teams already have — integrations and SDKs, migrations and refactors, CRUD on well-typed schemas, codegen from formal specs, infrastructure-as-code, and bug fixes with a reproducing test — together roughly 40–60% of what a typical SaaS team ships. The near edge (feature-flagged work, benchmark-driven performance) arrives within a year; the rings beyond it need Level 6 self-optimisation and more mature telemetry. Start by running one ticket end to end and shipping it, because the harness tuning and intent-writing compound with every ticket. human is the harness for that today-list.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Beyond the Dark Factory</title>
      <link>https://gethuman.sh/beyond-dark-factory/</link>
      <pubDate>Sat, 11 Apr 2026 00:00:00 +0000</pubDate>
      <guid>https://gethuman.sh/beyond-dark-factory/</guid>
      <description>&lt;aside class=&#34;tldr&#34;&gt;&#xA;  &lt;span class=&#34;tldr-label&#34;&gt;TL;DR&lt;/span&gt;&#xA;  &lt;p&gt;The first piece stopped at Level 5, the dark software factory. Two more levels are already visible from here. Level 6 is the self-optimizing factory: the harness measures itself, tunes itself, and compounds. Level 7 is the autonomous ideation factory: the factory reads customer signals and generates its own tickets. Each level pulls a loop that used to be human inside the machine. The meta-work is the new frontier, not code-writing. The scarce resource at Level 7 is taste, and taste does not move inside the factory. human is a Level 5 harness today; the next step for it is Level 6.&lt;/p&gt;</description>
    </item>
    <item>
      <title>What is a Dark Software Factory?</title>
      <link>https://gethuman.sh/dark-software-factory/</link>
      <pubDate>Wed, 08 Apr 2026 00:00:00 +0000</pubDate>
      <guid>https://gethuman.sh/dark-software-factory/</guid>
      <description>&lt;aside class=&#34;tldr&#34;&gt;&#xA;  &lt;span class=&#34;tldr-label&#34;&gt;TL;DR&lt;/span&gt;&#xA;  &lt;p&gt;A dark software factory is an autonomous software delivery pipeline where AI agents write, test, and ship code from specifications, and no human reviews the diffs. The name comes from lights-out manufacturing, where robots make things in factories with the lights off because no one is on the floor. The term was applied to software in early 2026 by Dan Shapiro. BCG Platinion and i-SCOOP picked it up as the category label for Level 5 AI-assisted coding, and StrongDM is the most-cited proof-of-concept. Humans are not removed from this model. They move upstream and downstream: intent, policy, outcome review. The middle, the actual writing and reviewing of code, is machine-driven.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
