# Orchestras, Not Factories: How the Fastest Builders Work — Charlie Holtz, Conductor

## Executive summary

Charlie Holtz, co-founder of Conductor, outlines principles for achieving peak building efficiency, arguing that the future of development lies in 'orchestras' of human and AI effort, rather than 'factories' of pure automation. Key strategies include staying near technological frontiers, avoiding over-optimization for non-default workflows, establishing 'slop-free zones' for critical code, centralizing all organizational data ('feeding the beast'), and giving agents free-range, cloud-based sandboxes for exploration and collaboration.

## Key takeaways

- Stay Near the Frontier: Always experiment with the latest tools (e.g., ultra code, slash go) to generate new ideas. Staying current is crucial because workflows move too fast for traditional information trickle-down methods. (2:00)
- Don't Try to Beat the Market: When deciding on workflow optimization, ask if the workflow is the default. If it is, wait for major platforms (Anthropic, OpenAI, etc.) to integrate it, rather than spending time on niche optimizations. (3:25)
- Create Slop-Free Zones: Identify critical parts of the codebase (e.g., migrations files, documentation, skills) that require strict human review and care, preventing the codebase from becoming unstable. (5:25)
- Feed the Beast: Centralize all organizational information—including Slack messages, bug reports (Discord), and meeting recordings—into a single database so agents have maximum context for effectiveness. (7:25)
- Free-Range Agents: Provide agents with cloud sandboxes where they can run and explore without being confined to a local laptop, enabling sustained work and collaboration. (8:40)
- Orchestras, Not Factories: The future of development should feel human and crafted, like conducting an orchestra, where humans and agents collaborate, rather than managing an assembly line or 'feature factory.' (14:40)

## Technical details

- Conductor: A desktop application designed to manage and orchestrate multiple coding agents (Cloud Codes, Code Accesses) from a single interface. (1:05)
- Agent Architecture: Agents benefit from cloud sandboxes, allowing them to continue running and working even when the user closes their laptop. (8:40)
- Data Integration: The 'Conductor Internal Agent' (CIA) acts as a centralized database, ingesting data from sources like Slack and Discord to provide comprehensive context for agents. (7:25)
- Code Safety: Designating 'slop-free zones' is critical; for example, CI requires human review for any changes to the migrations file. (5:25)

## Practical implications

- Build workflows that are highly contextual by centralizing all organizational data (Slack, bug reports, meetings).
- Prioritize human-reviewed zones (migrations, docs) in the codebase to maintain stability.
- Shift the development mindset from pure automation ('factories') to human-centered collaboration ('orchestras').
- Utilize cloud sandboxes to ensure agents maintain continuity and capability regardless of the user's physical location.

## Topics

AI Engineering, Agent Orchestration, Software Architecture, Build Tools, DevOps, Conductor

Source: https://www.youtube.com/watch?v=TRfzFJCJ7ZE