AI Services Market › Use cases › Software & DevOps
Software & DevOpsDone with Devin Jan 1, 2025
Try Devin for pull requests on a company codebase
A commenter's team tried Devin but found PRs slow and still needing review, so it felt like a junior developer.
- What They Did
- One commenter said their team at a decently sized tech company tried Devin on its codebase to get pull requests submitted. In practice, Devin produced PRs slowly, and the team still had to review the code themselves, so the human work stayed in the loop and the tool mainly acted like a very junior developer.
- How It Went
- They stopped using it because the turnaround was too slow and the value did not beat ordinary review overhead. The commenter said it felt comparable to hiring a junior developer, and the pricing also was not competitive.
- Worth Knowing
- The key catch was cost versus speed: the commenter said Devin was slow to submit PRs and still required full code review, so the economics did not work for them.
Try it yourself with Devin
In [repo name], take this ticket: [ticket description or link]. Make the change, run the existing tests, and open a pull request with a clear description of what you changed and why. Show me the plan and the diff before you push, and list anything you were unsure about so I can review it quickly.
Do this with a skill.
These AI Services Market playbooks do this exact job.