06-reference

indy dev dan tiny software factories

2026-11-02·reference·source: IndyDevDan (YouTube)·by IndyDevDan
agentic-engineeringsoftware-factoriesagent-uxnear-the-loopcron-agents

"Tiny Software Factories: Agentic Engineering DONE WRONG" — IndyDevDan

Full transcript: [[2026-11-02-indy-dev-dan-tiny-software-factories-transcript]].

Why this is in the vault

IndyDevDan is a tier-1 tracked channel for agentic-engineering practice, and this lesson is a direct, named stab at the "software factory" pattern RDCO has built against repeatedly (Scribble Works, Squarely tooling, skill-brigade stations). The provocative framing ("done wrong," "anti-patterns") is marketing for his Phase 3 course, but the underlying taxonomy — empty factory vs. working factory, in-the-loop vs. near-the-loop, agent access parity, cron prompts as the bridge to autonomy — is a genuinely useful vocabulary for auditing RDCO's own factory-shaped builds.

Episode summary

This is lesson one of Dan's "Tiny Software Factories" mini-course (a free preview ahead of his paid "Phase 3: Infinite Agentic Engineering" presale). He defines a tiny software factory as a single-purpose, 24/7 proactive agent system where the human sits "near the loop" (reviewing/approving) rather than "in the loop" (prompting back and forth), then walks through a live demo UI — pages, a persistent agent sidebar, full agent/human tool parity, the "core four" (context, model, prompt, tools), customizable DX, and cron-triggered prompts — to show how fast one can be stood up.

Key arguments / segments

Notable claims

Mapping against Ray Data Co

Strong mapping. RDCO's own practice already lives inside Dan's "near-the-loop" zone almost everywhere that matters: check-board, morning-prep, open-threads-check, and the brigade stations (spec-author → test-author → code-author → critic) are all proactive, cron/trigger-driven agents that surface decisions rather than wait for prompts — exactly his "empty factory → specialized factory" shape. The "core four" (context/model/prompt/tools) maps cleanly onto how RDCO already treats agent configuration as a first-class lever (model+effort pairing per feedback_delegation_model_effort_pairing, context budget discipline in AGENTS.md rule 4). His "agent access parity" point — every human UI control should have an agent-callable equivalent — is a sharper articulation of why RDCO keeps building CLI/script wrappers (cloudflare-api.sh, wrangler.sh) rather than leaving actions GUI-only. The one gap: Dan's demo factory lets the agent reconfigure its own tools/thinking level live, which is further than RDCO currently goes — the founder's existing settings-drift and classifier-gate rules (feedback_no_claudemd_state_drift, feedback_automode_classifier_hard_gate) are effectively a guardrail against exactly that kind of self-modification happening ungated. Worth flagging, not necessarily worth adopting.

Related