Great callout! I think it's similar, but our approach is a bit different from Devin's because we're currently focusing less on autonomy.
It looks like Devin chooses a plan and then writes and runs the code or uses the internet to get feedback on how to change the plan/code accordingly.
We focus on having the engineer work with the AI on the plan before writing the code, and the engineer is responsible for the final implementation.
We found that doing everything autonomously was awesome when it worked but frustrating when it didn't; so we wanted to make the UX interactive enough to be useful even if the AI gives some unexpected results. Does that help?
It looks like Devin chooses a plan and then writes and runs the code or uses the internet to get feedback on how to change the plan/code accordingly.
We focus on having the engineer work with the AI on the plan before writing the code, and the engineer is responsible for the final implementation.
We found that doing everything autonomously was awesome when it worked but frustrating when it didn't; so we wanted to make the UX interactive enough to be useful even if the AI gives some unexpected results. Does that help?