asynchronous workflow
A working pattern where a human delegates a task to an agent and works on other things while the agent completes it, reviewing output later.
As defined in Scott Wu - Building Cognition - [Invest Like the Best, EP.402]
Where it comes up · 1
Most important claims · 5 of 5Search all claims for “asynchronous workflow” →
- Devin turns each engineer into an engineering manager with a team of Devins, delegating many small tasks and working on them asynchronously while the Devins run in parallel and ask questions or submit code for review.Scott Wu - Building Cognition - [Invest Like the Best, EP.402]
- The biggest step-function difference between IDE code assistants and Devin is asynchronous versus synchronous work: assistants give roughly 10 to 20 percent speedups by autocompleting while the human confirms each suggestion, whereas Devin takes a whole task off the engineer's hands, making it closer to 10x for delegable tasks.Scott Wu - Building Cognition - [Invest Like the Best, EP.402]
- Roughly half the time, Devin's output on a reported bug, crash, or feature request is a pull request ready to merge; the other half requires coaching Devin, touching it up, or starting over, but tagging Devin still gives a free first pass.Scott Wu - Building Cognition - [Invest Like the Best, EP.402]
- Because bug reports must be filed anyway, tagging Devin at the end of the report adds almost no cost and yields a free first-pass attempt, which is why asynchronous workflows are easy to adopt.Scott Wu - Building Cognition - [Invest Like the Best, EP.402]
- Engineers at Cognition kick off small refactors and type-safety fixes to Devin from the IDE while continuing their own project, so small distractions get handled asynchronously rather than breaking focus.Scott Wu - Building Cognition - [Invest Like the Best, EP.402]