[ericmaciver]

I used to watch a window code - each line - but that was too much. I ended up just making sure adversarial reviews are performed for every task, a completion report generated to my personal preferences and then I feed multiple tasks through an an orchestrator that keeps the high-level context in play, which aligns work with my objectives before merging it. It knows my preferences, and runs audits itself, along with automated tests. It took a long time to tweak it to a point where I can stay involved in the choices and code while maximizing throughput - but the work put into the ecosystem has (so far) paid off.

[cmar00]

Wow this feels next level! So you only talk to the orchestrator, then it calls sub agents to do the actual work, review and realign. Got a few questions for you:

- Which tools did you use to create this ecosystem?

- Do you write the tests yourself? Do you tell it which tests to write? Or does it guess them on its own based on his understanding of your preferences? How do you make sure the generated code is secure?

- As you give orders to the orchestrator and as the orchestrator gives orders to sub agents your original message might get distorted (similar to when you print a copy of a copy of a copy with your printer). Do you ever find subagents going off topic in an endless code/review/code/review loop?