Building engineering teams where humans orchestrate and agents execute. 🤖 Calling it AI-Orchestrated Engineering (AoE). 📧 CTO @ sending .ac · 🇻🇳 Da Nang
We ship an email deliverability suite. Built by engineers and product designers, not a solo dev.
Humans orchestrate, agents execute. I call this AI-Orchestrated Engineering (AoE).
Most takes on AI engineering come from people who don't ship features to paying customers, or who work solo. We ship. In a team.
This is my unfiltered playbook re: how it actually works.
What you get here:
- how AoE works in production
- the processes and checklists we use, copy them
- what we got wrong, and how we fixed it
Follow if you are serious about building with agents.
Check my GitHub if this sounds like we should work together.
The Core and Vibe fork only works because our products live on separate domains.
Different brand, different users, different trust surface.
Vibe ships fast. Core ships solid.
We forked our own codebase in half.
One side is the paid product. Reliability first. Seniors own it. We call it Core.
Other side is everything adjacent. Speed first. Juniors own it. We call it Vibe.
Same platform under both.
@alexcooldev Do you sometimes feel a desire for structure?
That’s what I hear so often: this freedom to do and work on whatever you want can actually feel daunting
How to fix that…
What a junior owns here on day one.
Build it. Write and run the tests. Deploy. Watch the rollout. On-call for what they built.
No code review gate. Design is signed off before they start. After that it's theirs.
@TheAhmadOsman I'd love to see a breakdown of technologies and how you integrated them. I believe this is a reusable pattern for many future projects. “3 Tier Architecture” days are gone.