Stop chatting with your code. Start assigning tickets to it. The mistake most devs make with AI is treating it like a chat partner.
The real UI for AI coding is not a chatbot. Its a Pull Requests.
Chats disappear. They rely on your memory.
PRs persist. They capture intent, context, and verification.
My current workflow looks like this -
1. I spot a grunt work like "update all API endpoints to v2."
2. I send a message in slack with the details or open a ticket with the intent in our ticketing tool.
3. I get a plan, approve it, and let an async agent handle the execution by queuing and scheduling it.
4. I focus on the complex problems.
A few moments later - a PR lands. I review the diff, review the tests and if i am satisfied get it merged.
I don't stare at the screen and wait or open multiple terminals and juggle. I just orchestrated it.
This is the **async coding model**.
It frees you up to solve the problems that actually require a human brain, while the "digital labor" handles the execution.
Excited for whatโs cooking!
Vibe coding tools are getting powerful but the ecosystem is messy. IDE agents. CLI agents. App builders. All great but not fully autonomous.
The missing piece is orchestration.
That is why we are building Sia. It routes tasks, handles policy, manages multi repo work, and turns tickets into PRs across your stack.
Shared a full breakdown of the vibe coding landscape and why an orchestrator matters.
https://t.co/6t4Zu0OImE
2. Asynchronous (The Goal): You assign a task, close your laptop, and come back to a finished Pull Request.
We need to stop optimizing for #1 and start building for #2.
The future belongs to the Orchestrators.
I want to focus on the System Architecture while an agent handles the dependency upgrades and UI padding fixes in the background.
We need to move from "Human-in-the-loop" to "Human-on-the-loop."
This destroys deep work. You can't architect a complex system if you're interrupting your thought process every 30 seconds to verify an AI's syntax.
True parallelism in software engineering is missing.
Weโre extending our Thanksgiving offer ๐
If youโre new to Dialo, you now get:
๐ Your first call free
๐ณ 10% extra credits on your first recharge
Dialo is fully pay-as-you-go. No subscriptions.
Just simple international calling that works anywhere.
Try - https://t.co/CwHJWHdi1S
@svpino This is the problem which existed, existing and will exist in future irrespective of the tech.
The problem is not automation, its about finding the inefficiency and how much the leadership is caring about that and how much they are willing to pay for it.
@konstipaulus@SteveMoraco Working on https://t.co/kdxHUFl6s0 at the moment. Will drop our first version on Dec 1st and its also going to be open source from day-1.
Excited!
@audiencon I am 200% with you on this. At an early stage, VCs don't add much. Most of it is new for them too, so they end up wasting your time more than helping.
@garrytan I don't get why 50/50 is considered bad. If things are stuck, the title decides anyway. The CEO makes the final call. So why bother with 51/49 and it only gets messier once dilution starts kicking in.
@pmitu I became a complete reply man after your suggestion. Just two curious questions -
1. How many replies do you do in a day?
2. Are your replies mostly to comments on your own posts or do you jump into others posts too? Which one is more for you?