Linda Xie
@linda
1/ My first attempt trying Devin ("collaborative AI teammate" for eng work) was a success My experience: We needed to make styling changes on Bountycaster based on user feedback. I talked to Devin over Slack using natural language and it shared the plan with me in an understandable way. Once I reviewed and confirmed it, Devin submitted a PR (~5 min). I asked Devin to make more changes once I saw how it looked locally. Devin wasn't able to figure out one of them but that was minor, then I merged the changes
2 replies
6 recasts
44 reactions
Linda Xie
@linda
2/ Context: I'm not a dev but have basic coding experience. I usually can handle basic styling changes on my own + Claude. Anything more complicated goes to my cofounder but he's solo dev so unless it's high priority, we have to backlog it Conclusion: Devin saved me significant time *as a non-dev* having to figure out how to implement the change using Claude or wait for my cofounder to implement it if I couldn't figure it out. I love that Devin has context over the entire codebase and it's easy to communicate through Slack using natural language. The price point of $500/month is high for our bootstrapped team. We'll continue to test and see devin.ai
3 replies
1 recast
24 reactions
Zach
@zd
I’m curious if you stick around or churn I found the novelty factor wore off after the first week or two, and Devin kept choosing more complicated solutions than were necessary / making new bugs I like that it can be used across repositories, and the input method being Slack, but I wish the accuracy was improved (Cursor has a higher likelihood of one shot prompts being correct in my experience)
1 reply
0 recast
3 reactions