Bijan Bowen compares two attempts to build a 3D flight simulator with a local Qwen 27B coding model. The direct single-agent attempt struggled to maintain the project and did not produce a usable result, while the orchestrated run decomposed the work into milestones and assigned focused tasks to separate agents.
The orchestration layer maintained a shared plan, reviewed intermediate changes and surfaced dependencies between tasks. It caught implementation problems that a simple one-pass workflow missed, including issues that were not obvious from a quick visual check.
The run also recovered after a context and server interruption by using the durable project plan and completed artifacts. The practical lesson is that coordination, review and recoverable state can matter as much as the underlying model when small models tackle larger software projects.
Watch the original on YouTube