06-reference

indy dev dan zero to running software factory 16 minutes

2026-11-09·reference·source: IndyDevDan (YouTube)·by IndyDevDan
agentic-engineeringsoftware-factoriesliquid-softwarenear-the-loopsubagents

"ZERO to RUNNING Software Factory In 16 Minutes (LIQUID Software)" — IndyDevDan

Why this is in the vault

Lesson two of IndyDevDan's Tiny Software Factories series, following the lesson-one note already filed. It shows a concrete init/configure/specialize workflow for mounting an agent-driven app shell into an existing codebase, plus a set of agent-UX features (tool summaries, budgeted subagents, agent access parity) that map directly onto how RDCO runs and observes its own agents.

Episode summary

Dan takes an empty "tiny software factory" template and, with one skill and one command, installs it into a mock prompt-to-image app (Hues), then feeds a 150-line plan to a configure skill to turn it into a product-analytics agent. While that runs he walks through the 14 features added in tier two, framed as "liquid software" that reshapes itself to the problem. The through-line is the move from in the loop to near the loop.

Key arguments / segments

Notable claims

Guests

None. Solo demo by IndyDevDan.

Sponsorship

House promo: the description and framing push the agenticengineer.com "Infinite Agentic Engineering" course, of which this series is the preview. No third-party paid sponsor is named in the transcript. Bias: the factory template is the product being sold, so "great defaults" and the 14-feature value claims are marketing-adjacent; the demos run on his own mock app rather than a real production workload.

Mapping against Ray Data Co

Strength: medium. Three portable ideas. (1) Tool summaries by a cheap model are a pattern for RDCO's own observability of cron and subagent runs, where raw tool output is currently unreadable at a glance. (2) Budgeted subagents (model tier plus time and dollar caps per launch) resemble RDCO's delegation model/effort pairing and could be made explicit as per-run caps. (3) Agent access parity matches the advisor-mode, agent-does-reversible-work stance: every HQ control should be agent-callable. The "near the loop" framing is the same argument as the founder's decision-vs-action split. The product itself (a sellable template) is not an RDCO dependency; RDCO is a personal-license, phData-first setup, so this is idea mining, not adoption.

Related