Build a Software Factory That Actually Works
A practical software-factory blueprint for parallel coding agents: isolate work, build to explicit architecture, prove behavior with evidence, and ship through review loops.
Every case study, system breakdown, and field note, newest first and filterable by topic. No theory, no demos. Only systems that run in production and what it took to get them there.
This is the complete archive: all 478 posts across 52 topics, newest first, filterable by category. It holds the case studies, the model and tool comparisons, and the field notes from systems I built and run. For the curated view, where the writing sits alongside the free Claude Code skills, start at the Library instead.
The archive leans in four directions: AI Search Visibility (95), AI Agent Architecture (58), AI Tools (38), and AI Coding Agents (26). Those four account for most of what I publish, because they are where most of the client questions land.
Three places to start. The AI search visibility guide is the hub for the largest cluster and links out to every spoke in it. Grok Imagine vs Midjourney is the image model comparison, rebuilt against live leaderboard data rather than left to go stale. OutreachIQ is the longest running system breakdown here, from first prototype through to a public repo.
A practical software-factory blueprint for parallel coding agents: isolate work, build to explicit architecture, prove behavior with evidence, and ship through review loops.
Test service-package changes with approved offer facts, fixed buyer questions, evidence capture, and regression checks for prices, currencies, scope, and exclusions.
A practical guide to Herdr workspaces, tabs, panes, persistent sessions, VPS access, agent tracking, CLI automation, and the official Herdr skill.
Allie K. Miller's 34-agent system rebuilt as a practical guide to goals, context, fixed risk tiers, watchdogs, model routing, and reusable factories.
Garry Tan frames personal AGI as owned context, reusable skills, and agent infrastructure. Here is the architecture, security model, and 30-day build plan.
The official Agent Plugins standard explained: root plugin.json, portable Agent Skills, MCP configuration, client support, migration, and security boundaries.
Andrew Warner and Alex McDonnell demonstrate a Hyperagent sales team inside Slack. Here is the architecture, approval model, shared-memory risk, security history, cost boundary, and safer rollout.
Andrew Warner and Mike Bradley install ODS on Windows. Here is what the local AI stack includes, what stays private, the real hardware tiers, and a safer setup path.
Bijan Bowen pairs Fable 5 with local Qwen3.6 27B in Traycer. Here is what improved, failed, and the solo baseline revealed about multi-agent orchestration.
Greg Isenberg's framework rebuilt as a practical guide to jobs, arrows, shared state, parallel research, checks, loops, and human approvals.
Josh Pocock stress-tests Buzz and exposes the gap between a shared agent workspace and dependable orchestration. Here is what Buzz really solves, what the demo broke, and the controls a production agent team still needs.
Kacper Rutkiewicz tests Scrapling across targeted web extraction, prospect research, and design synthesis. Here is the source-checked setup, the real token math, the fetcher decision tree, and the legal and security boundaries his workflows need.
Vaibhav Sisinty builds a reusable specialist, a delegated startup team, and a scheduled analyst in Hyperagent. Here is the practical no-code setup with prompts, permissions, costs, rubrics, and approval gates.
Riley Brown and Vince Canger show how to build a practical Buzz agent team with Codex as the lead, Claude Code and other runtimes as specialists, scoped channels, review loops, mobile access, and safer recurring workflows.
Andrew Warner and Vince Canger test Buzz across agent runtimes, Wasp and Railway deployment, mobile access, Git projects, workflow triggers, shared compute, and multi-agent routing. Here is the practical operator guide.
Vaibhav Sisinty tests ChatGPT Work and Claude Cowork across projects, scheduled tasks, connectors, recorded skills, Slack, Sites, Artifacts, and local work. Here is the current, source-checked comparison.
Greg Isenberg and Vinny tour Buzz, Block's open agent workspace. The real opportunity is portable team context across Claude Code, Codex, Goose, Git worktrees, workflows, and local compute, with important early-preview limits.
Cody Schneider and Greg Isenberg map a real Meta Ads agent: unified business data, research and creative pipelines, bounded API actions, and a feedback loop tied to revenue.
Ryan Carson explains how he runs parallel cloud agents, recurring production checks, self-improvement loops, and model routing. This guide turns the interview into a controlled agent-operations system.
Block's Buzz puts people, Claude Code, Codex, and other agents in one Nostr workspace. Here is the architecture, privacy reality, chief-of-staff pattern, shared-compute risk, and honest Slack comparison.
Ari Meisel shows how Tasklet agents coordinate website optimization, knowledge, content, support, and personal tasks. Here is the architecture, full toolkit, shadow-mode rollout, and the controls the demo still needs.
Run GPT-5.6 Sol inside Hermes Agent: the verified Codex OAuth setup, how to pick reasoning effort, three bounded workflows, and the safety controls to keep.
Vaibhav Sisinty explains why token consumption is becoming a business cost problem. Here is the source-checked playbook: measure cost per successful task, route models, cache correctly, trim context, set limits, and decide when local inference pays.
Greg Isenberg and Elie Steinbock explain how loop engineering can improve SEO, ads, and product feedback. Here is the practical architecture: objective metrics, memory, budgets, verification, schedules, and stop conditions.
Every post here is about a system that actually shipped. Book a free call and let's talk about what could ship for you.
Book Free 30-min CallAdd your name and email to unlock recording.
Thanks for your voice message. I listen to every one myself and I will get back to you within one business day.